Matillion Webhook Setup Guide

Log in to Matillion and click Profile & Account at the bottom of the left navigation bar.

In the menu that opens, click Notifications under your user section.

On the Notifications page, click Add notification.

Select the Project and Environment you want StackOne to receive events for. To cover several projects, repeat this guide once per project/environment pair.

Under Pipeline completion alerts, click Add.

In the alert card, select the run outcomes to deliver, then under How do you want to receive this notification? tick Webhook.

• Select Success, Failure, Cancelled and Skipped to enable all completion events
• Tick Webhook as the delivery method

Three fields appear when Webhook is ticked.

• Webhook URL — paste the StackOne webhook URL for this connected account
• Webhook Name — any descriptive name, e.g. StackOne
• Payload Template — paste the template from the next step exactly as given

StackOne relies on this exact template to route events — paste it into Payload Template without modification (the View available variables link shows the supported placeholders):

{"source":"stackone","event":"pipeline.completion","status":"${status}","pipelineName":"${pipelineName}","pipelineExecutionId":"${pipelineExecutionId}","finishedAt":"${finishedAt}","projectId":"${projectId}","accountId":"${accountId}"}

Click Add notification. The new notification appears in the list with Webhook delivery.

To also receive duration-anomaly events, click Add under Anomaly alerts (or edit the saved notification), tick Enable anomaly alerts, choose Webhook, fill the same Webhook URL, and paste this anomaly template instead, then click Save:

{"source":"stackone","event":"pipeline.anomaly","status":"${status}","pipelineName":"${pipelineName}","environmentDisplayName":"${environmentDisplayName}","startedAt":"${startedAt}","elapsedDurationSeconds":"${elapsedDurationSeconds}","pipelineExecutionId":"${pipelineExecutionId}","triggerType":"${triggerType}","projectId":"${projectId}","accountId":"${accountId}"}

Events describing the outcome of scheduled or API-triggered pipeline runs.

• Pipeline Run Succeeded (pipeline_run.succeeded) — Fired when a pipeline run completes with status SUCCESS
• Pipeline Run Failed (pipeline_run.failed) — Fired when a pipeline run completes with status FAILED
• Pipeline Run Cancelled (pipeline_run.cancelled) — Fired when a pipeline run is cancelled
• Pipeline Run Skipped (pipeline_run.skipped) — Fired when a scheduled pipeline run is skipped
• Pipeline Run Duration Anomaly (pipeline_run.anomaly) — Fired when a run’s duration deviates significantly from its historical baseline (requires anomaly alerts enabled and a historical baseline)

Completion alerts support ${pipelineName}, ${status}, ${finishedAt}, ${pipelineExecutionId}, ${projectId} and ${accountId}. Anomaly alerts additionally support ${environmentDisplayName}, ${startedAt}, ${elapsedDurationSeconds}, ${expectedUpperBoundSeconds}, ${expectedLowerBoundSeconds} and ${triggerType}.