Notifications - How to Configure and When?

WOODY.IO Notifications let you trigger actions when an Import reaches specific states.

Create a Notification (common steps for all types)

1. Go to Management > Notifications and click Add Notification.
2. Fill the common fields:
   • Name
   • Description
   • Notification Type (select one type; the form for that type appears)
3. Configure the Condition section:
   • Select States: choose which Import state changes should trigger the Notification. WOODY.IO provides a fixed list of states such as Ready to persist, Persisting, Error Persisting, Archived, etc.
   • Filter (optional): restrict triggers to a subset of imports, using filters such as Metamodel, Import Template, Persist Type, Import Type, and counts like Error Count, Warning Count, Row Count.
4. Use tokens where supported (subject/body/payload/parameters) to include context like:
   • {import}, {import_identifier}
   • {metamodel}, {import_template}, {persist_type}
   • {row_count}, {warning_count}, {error_count}, {clearance_count}, {information_count}

Notification Types

Databricks

When to use?

Use this when the action you want to run is executed inside a Databricks workspace, such as running SQL, a notebook, or a job.

How to configure?

1. Create or verify a Databricks Connection for the workspace you want to target.
2. In Add Notification, set Notification Type to Databricks.
3. Configure the Databricks fields:
4. Connection: select the Databricks workspace connection
5. Method: choose one
   • SQL: provide Query
   • Notebook: provide Notebook Path and optional Parameters
   • Job: provide Job ID and optional Parameters
6. Choose trigger States and optional Filters as described in the common steps.
7. If you need runtime context in Databricks, pass WOODY tokens via notebook/job parameters (where your implementation expects them). Tokens available are listed in the Tokens panel.

HTTP Request

When to use?

Use this when you want WOODY.IO to call an external HTTP endpoint after an import finishes, such as an Azure Function, a Logic App, or an internal Webhook.

How to configure?

1. In Add Notification, set Notification Type to Http Request.
2. Configure the HTTP fields:
   • Url (supports Key Vault reference)
   • Method
   • Headers (supports Key Vault reference)
   • Body
3. Choose trigger States and optional Filters to avoid unintended calls.
4. Put tokens in the Body (and in headers if your receiver expects them) so the receiver knows which import triggered the call and with what counts.

Azure Event Grid

When to use?

Use this when you want to publish an event to an Azure Event Grid topic (or partner endpoint) so downstream subscribers can react in an event-driven way.

How to configure?

1. In Add Notification, set Notification Type to Azure Event Grid.
2. Configure the Event Grid fields:
   • Endpoint (supports Key Vault reference)
   • Event Schema
   • Event Type
   • Body
   • Authentication (supports Key Vault reference)
3. Choose an Authentication Type:
   • Application Service Principal: uses the Service Principal configured and managed within the WOODY.IO Application
   • Service Principal: uses the default Service Principal associated with the WOODY.IO application registration
   • Custom Service Principal: manually provide Tenant ID, Client ID, Client Secret
   • Access Key: authenticate using the Event Grid access key
4. If you use Custom Service Principal, the fields Tenant ID, Client ID, and Client Secret support Key Vault references.
5. Choose trigger States, optional Filters, and add tokens to the Body if you want consumers to receive import context.

Email

When to use?

Use this for human-facing notifications such as operational alerts, approval-related messages, and summaries delivered to an inbox. Tokens can be used to include details like import name and error counts.

How to configure?

1. In Add Notification, set Notification Type to Email.
2. Configure the email fields:
   • To (supports Key Vault reference)
   • Subject
   • Body (can contain HTML)
3. Choose trigger States and optional Filters.
4. Use tokens in Subject and Body so recipients get actionable context.

Microsoft SQL

When to use?

Use this when the downstream action is a SQL Server operation that should run after persisting has finished, such as executing a stored procedure or a DML statement.

How to configure?

1. In Add Notification, set Notification Type to Microsoft SQL.
2. Configure:
   • SQL: the statement to execute
   • Connection: the Connection ID
3. Choose trigger States and optional Filters.