Documentation
Action triggers
Growth and above. Notify a channel when a rule fires.
An action trigger turns a firing rule into a message where your team already works. The notification carries the finding and a link back to the sourced Brief, so nobody has to reconstruct the number.
Destinations
| Destination | What is sent |
|---|---|
| Slack | Message to a channel or direct message, with the finding and a link to the Brief |
| Microsoft Teams | Message to a channel, same payload |
| Notification to named recipients | |
| Webhook | Signed JSON POST to your endpoint for custom routing |
Set one up
- 1
Open the rule
Go to the Decision Topic and select the rule you want to act on.
- 2
Add an action trigger
Choose Notify, then select Slack, Teams, email, or webhook.
- 3
Authorise the destination
Connect the workspace or channel, or supply the webhook URL. Notifications are outbound only.
- 4
Choose the payload detail
Send the headline finding only, or include the supporting figures and confidence.
- 5
Set quiet rules
Add a minimum interval so a flapping condition does not repeat in the channel.
- 6
Test the trigger
Fire a test notification, confirm the destination receives it, then enable it.
Note
Action triggers notify. They do not change data in a source system. Anything that creates work in another system is agent handoff.
Action trigger FAQ
Which plans include action triggers?
Growth and above. Free and Plus workspaces receive alerts in-app instead.
Is the webhook payload verifiable?
Yes. Webhook deliveries are signed so your endpoint can verify the request came from SIGNLD before acting on it.
Do notifications include the underlying data?
They include the finding and the supporting figures you choose, plus a link back to the Brief where full lineage lives. Access to the Brief still follows workspace permissions.
Further reading
Was this helpful?
Contact support