Send alert in SIGNL4.
Application
SIGNL4
Inputs (what you have)
Name | Description | Data Type | Required? | Example |
Connected Account | The connected account to use for the request | Connected Account | Yes | |
Message | A more detailed description for the alert | Text (Long) | No | |
Alerting scenario | Predefined Choice List | No | ||
External ID | If the event originates from a record in a 3rd party system, use this parameter to pass the unique ID of that record. That ID will be communicated in outbound webhook notifications from SIGNL4, which is great for correlation/synchronization of that record with the alert. If you resolve / close an alert you must use the same External ID as in the original alert | Text (Short) | No | |
Filtering? | Whether to apply event filtering for this event, or not. If set to true, the event will only trigger a notification to the team, if it contains at least one keyword from one of your services and system categories (i.e. it is whitelisted) | True/False | No | |
Latitude | The location latitude | Text (Short) | No | |
Longitude | The location longitude | Text (Short) | No | |
Service | Assigns the alert to the service/system category with the specified name | Text (Short) | No | |
Title | The title or subject of this alert | Text (Short) | No |
Outputs (what you get)
Name | Description | Data Type | Required? | Example |
JSON Output | JSON output returned by the API | Text (Long) | No |
Outcomes
Name | Description |
Success | This status is selected if the job has successfully completed. |
Unsuccessful | This status is selected if the job has completed unsuccessfully. |
Requirements
N/A