Close all acknowledged alerts in SIGNL4
A documented SIGNL4 operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Close all acknowledged alerts.
- POSTChanges data · Alerts
connect.signl4.com/alerts/closeAll
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which SIGNL4 operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other SIGNL4 operations
- Create WebhookPOST · changes data
- Get overview event pagedPOST · changes data
- Creates a new script instance in the in the SIGNL4 teamPOST · changes data
- Create a new categoryPOST · changes data
- Sends invite email again if an invite existsPOST · changes data
- Uploaded a profile image for a specified userPOST · changes data
- Updates user profile of an userPUT · changes data
- Punch User inPOST · changes data
Questions
- Can HumDay close all acknowledged alerts in SIGNL4?
- Yes. This operation is published in SIGNL4's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my SIGNL4 data?
- Yes — this is a POST operation, so it changes something in SIGNL4. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your SIGNL4 account.
Where this came from
Read from a published API description for SIGNL4 at connect.signl4.com/api/docs/v1/swagger.json. The description above is the provider’s own wording, not ours. Last published 2021-06-21.