Trigger Alert
signl4.trigger_alert
ActionChat & messagingconnection required
Calls the SIGNL4 API with the connection's credentials.
Raise a Signl for a team directly, so everyone on duty receives an alert notification.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- SIGNL4
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- team_id, user_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
7 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
title Headline of the alert. | string | Yes | — | — | Payment gateway down |
text Body text describing what happened and what to do. | string | Yes | — | — | — |
team_id SIGNL4 team to act on; overrides the connection's default team. | string | No | — | — | a1b2c3d4e5f6 |
severity How serious the alert is. | string | No | — | one of "low", "major", "critical" | — |
category Service or system category to file the alert under. | string | No | — | — | — |
external_id Id of the record in your own system this alert corresponds to. | string | No | — | — | INC091210 |
parameters Extra name-and-value details to show on the alert. | object | No | — | — | {"Host":"db-01","Region":"eu-west-1"} |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"external_id": "INC091210",
"parameters": {
"Host": "db-01",
"Region": "eu-west-1"
},
"team_id": "a1b2c3d4e5f6",
"title": "Payment gateway down"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id SIGNL4's id for the alert. | string | — |
title The alert's title. | string | — |
text The alert's body text. | string | — |
externalId The id of the record in your system that raised it. | string | — |
categoryId Id of the service or system category it was filed under. | string | — |
categoryName Name of that category. | string | — |
eventId Id of the event that raised the alert. | string | — |
severity 0 low, 1 major, 2 critical. | number | — |
status.statusCode 1 open, 2 acknowledged, 4 closed. | number | — |
requiredAcknowledgements How many people still have to confirm it. | number | — |
lastModified ISO-8601 timestamp of the last change to the alert. | string | — |
{
"categoryId": "",
"categoryName": "",
"eventId": "",
"externalId": "",
"id": "",
"lastModified": "",
"requiredAcknowledgements": 0,
"severity": 0,
"status": {
"statusCode": 0
},
"text": "",
"title": ""
}See Trigger Alert run in a workflow.
In a technical demo we add the SIGNL4 connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.