Send Webhook Trigger

<< Click to Display Table of Contents >>

Raynet One Data Hub > 2026.2 > Administration and User Guide > Tasks > Creating or Editing Tasks > Configuration 

Send Webhook Trigger

The Send Webhook trigger type enables Data Hub to automatically send HTTP POST notifications to an external endpoint whenever a defined task event occurs. This allows integration with third-party platforms and automation workflows, such as Microsoft Teams, REST-based services, and custom notification pipelines.

 

To set up a Send Webhook trigger, navigate in Data Hub to Tasks > [Task Type] > Trigger, click the Add button, and select Send Webhook in the TYPE field. The webhook-specific input fields become available once Send Webhook is selected as the trigger type.

 

Configuration Fields

 

The following fields are required when configuring a Send Webhook trigger:

 

NAME: Sets a unique, descriptive name for the webhook trigger, used internally in Data Hub to distinguish it from other triggers configured for the same task.

 

CONDITION: Specifies the task event that activates the webhook. Select the appropriate condition from the dropdown menu. Available options are:

 

Success — The task completed without errors.

Failed — The task did not complete successfully.

Validation — The task data failed one or more validation checks.

Timeout — The task exceeded its permitted execution time.

 

TYPE: Set to Send Webhook to activate the webhook trigger fields.

 

URL: The target endpoint to which the HTTP POST request is sent. The URL must use the HTTPS scheme (for example, https://example.com/webhook). HTTP URLs are not accepted.

 

CONTENT TYPE: Determines the format of the request payload. Select one of the following options from the dropdown menu:

 

Content Type

Description

application/vnd.microsoft.card.adaptive

Sends a Microsoft Teams-compatible Adaptive Card. The PAYLOAD TEMPLATE field is not available for this content type. Data Hub automatically generates a card containing the task execution details: task name, status, start and end times, row counts per table (total, new or updated, deleted), and the tenant name.

application/json

Sends an HTTP POST request with the payload formatted as JSON. A non-empty payload is required.

application/xml

Sends an HTTP POST request with the payload formatted as XML. The payload must be valid XML. A non-empty payload is required.

text/plain

Sends an HTTP POST request with the payload as unformatted plain text. A non-empty payload is required.

 

PAYLOAD TEMPLATE: The data content included in the HTTP POST request body. The format must match the selected CONTENT TYPE. This field is not available when application/vnd.microsoft.card.adaptive is selected as the content type; for all other content types, a non-empty payload template is required.

 

Microsoft Teams Integration

 

When using the application/vnd.microsoft.card.adaptive content type, Data Hub automatically sends a structured Adaptive Card to the configured Teams incoming webhook URL. The card displays the following task execution details:

 

Task name and execution status

Start and end timestamps

Row counts per table: total rows, new or updated rows, and deleted rows

Tenant name

Error details (displayed if the task failed)

 

The Send Webhook trigger complements the existing Email Notifications Triggers and provides a flexible mechanism for integrating task lifecycle events into external systems and notification channels.