SIGNL4
Raise, acknowledge, annotate and resolve SIGNL4 on-call alerts so the team on duty is paged, with resolve-by-external-id for monitoring systems that close their own incidents.
OCNORA ships 8 typed SIGNL4 operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run. Endpoints not covered by a typed node are called at https://connect.signl4.com/api through the HTTP node with the same credential.
Before you connect SIGNL4
- Authentication
- API key
- Credential
- the API key, or {"api_key": "…"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with SIGNL4
Operations, grouped by what they do to your data.
Create and send 2
Read and search 3
Delete and cancel 1
Other operations 2
A sample SIGNL4 workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no SIGNL4 trigger is needed.
- 2Get Alertsignl4.get_alertRead one alert, including its current status and its timeline.
- 3Acknowledge Alertsignl4.acknowledge_alertConfirm an alert on behalf of a user, so SIGNL4 stops escalating it to the rest of the team.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 8
- Acknowledge AlertConfirm an alert on behalf of a user, so SIGNL4 stops escalating it to the rest of the team.signl4.acknowledge_alert
- Annotate AlertAdd a text note to an alert's timeline, attributed to a user.signl4.annotate_alert
- Close AlertResolve an acknowledged alert on behalf of a user.signl4.close_alert
- Get AlertRead one alert, including its current status and its timeline.signl4.get_alert
- List AlertsList a page of alerts for a team, filtered by status, external id or a text search.signl4.list_alerts
- List TeamsList the SIGNL4 teams this credential can alert, with the ids the other nodes need.signl4.list_teams
- Send EventSend 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.signl4.send_event
- Trigger AlertRaise a Signl for a team directly, so everyone on duty receives an alert notification.signl4.trigger_alert
SIGNL4 questions
- How does OCNORA authenticate with SIGNL4?
- With a stored API key credential, shaped the API key, or {"api_key": "…"}. A connection test can check it when you add it.
- What can I automate with SIGNL4?
- 8 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the SIGNL4 operation I need is not listed?
- Call https://connect.signl4.com/api from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use SIGNL4?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are SIGNL4 calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
More in Chat & messaging
See your first SIGNL4 workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.