Send Event
signl4.send_event
ActionChat & messagingconnection required
Calls the SIGNL4 API with the connection's credentials.
Send an event to a SIGNL4 team, which raises a new Signl or — with an external id — acknowledges or resolves the one that event raised before.
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
10 fields, 1 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 event, shown as the Signl's title. | string | Yes | — | — | Disk almost full on db-01 |
message Body text of the event, shown under the title. | string | No | — | — | — |
status What this event does: raise a new Signl, or acknowledge or resolve the one an earlier event with the same external id raised. | string | No | new | one of "new", "acknowledged", "resolved" | — |
external_id Id of the record in your own system. Required to acknowledge or resolve, because that is the only thing SIGNL4 matches on. | string | No | — | — | INC091210 |
target Team id to alert directly, or an inbound-webhook identifier to let the team's distribution rules choose. Defaults to the connection's team. | string | No | — | — | — |
service Service or system category to file the Signl under. | string | No | — | — | Security |
location Where it happened, as 'latitude, longitude', so the app shows a map. | string | No | — | — | 40.6413111,-73.7781391 |
alerting_scenario How the team is notified: one person acknowledges, everyone on duty acknowledges, or everyone in the team is alerted. | string | No | — | one of "single_ack", "multi_ack", "emergency" | — |
filtering Apply the team's keyword filtering to this event, so it only alerts when it matches a category. | boolean | No | false | — | — |
data Extra name-and-value fields to carry on the event and show on the Signl. | object | No | — | — | {"Host":"db-01","Source":"Nagios"} |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"data": {
"Host": "db-01",
"Source": "Nagios"
},
"external_id": "INC091210",
"filtering": false,
"location": "40.6413111,-73.7781391",
"service": "Security",
"status": "new",
"title": "Disk almost full on db-01"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id SIGNL4's id for the event that was accepted. | string | — |
alertId Id of the Signl this event raised, when it raised one. | string | — |
eventStatus SIGNL4's event status code. | number | — |
acknowledgedAlerts Ids of the alerts this event acknowledged. | array | — |
closedAlerts Ids of the alerts this event resolved. | array | — |
status The status the event was sent with. | string | — |
externalId The external id the event carried. | string | — |
{
"acknowledgedAlerts": [],
"alertId": "",
"closedAlerts": [],
"eventStatus": 0,
"externalId": "",
"id": "",
"status": ""
}See Send Event 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.