Alert the team on duty in SIGNL4 and resolve the alert when the issue is fixed.
Explore 2 workflow actions for SIGNL4, including account permissions and operation limits.
0 read actions2 write actions
WORKFLOW ACTIONS
What you can configure.
Choose an action in the workflow builder, connect an account, and map its inputs. These actions are available in the catalog; your account access and a successful test determine whether they work for your setup.
Resolve alert
Write
Resolve the Signl that an alert with this external ID raised.
Permissions and limits
Account permissions
The SIGNL4 team secret
Operation limits
Only a Signl raised with the same external ID is resolved.
SIGNL4 takes no idempotency key, so a lost answer remains uncertain and is never resent automatically.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Send alert
Write
Alert the team on duty with a new Signl.
Permissions and limits
Account permissions
The SIGNL4 team secret
Operation limits
People who muted the Signl's category get no notification.
SIGNL4 takes no idempotency key, so a lost answer remains uncertain and is never resent automatically.
A repeated request may repeat the external action. Review the previous result before retrying a write.
SETUP
Start with a controlled test.
01Connect the intended account
Use the account and permissions required for your process. Review the connection check before configuring a workflow action.
02Review inputs and access
Select a listed operation and map its required inputs. Use test records and add a human approval before writes that need review.
03Confirm the result
Inspect step outputs and confirm the result in SIGNL4. A saved workflow is not a completed provider action.