Automate SIGNL4

What SIGNL4 is

Use our API for systems integration or to build your own use cases. Sample scenarios include but are not limited to: 2-way integration: Triggering of Signls and updates in the third party systems when alert state changes occur Retrieving alarms for logging purposes Calendar integrations: Creation and management of on-call duties Punch users in and out based on

API host: connect.signl4.com

What HumDay can do in SIGNL4

49 documented operations change something in SIGNL4.

• POSTCreate Webhook/webhooks
• POSTGet overview event paged./events/paged
• POSTCreates a new script instance in the in the SIGNL4 team./scripts/instances
• POSTCreate a new category/categories/{teamId}
• POSTSends invite email again if an invite exists/teams/{teamId}/memberships/resendInviteMail
• POSTUploaded a profile image for a specified user./users/{userId}/image
• PUTUpdates user profile of an user/users/{userId}/profile
• POSTPunch User in/users/{userId}/punchIn
• POSTPunch User out/users/{userId}/punchOut
• POSTCreate/Update given duty schedule./teams/{teamId}/schedules
• POSTInvite users to a team/teams/{teamId}/memberships
• PUTUpdates the password of a user/users/{userId}/changePassword
• POSTPunch User in as Manager/users/{userId}/punchInAsManager
• PUTUpdate your subscription's current prepaid settings./prepaid/settings
• DELETEDelete Webhook by Id/webhooks/{webhookId}
• PUTUpdate Webhook by Id/webhooks/{webhookId}
• POSTTrigger Alert/alerts
• POSTAbility to disable a webHook./webhooks/{webhookId}/enable
• POSTAbility to enable a webHook./webhooks/{webhookId}/disable
• POSTGets alerts paged/alerts/paged
• POSTClose all acknowledged alerts./alerts/closeAll
• POSTClose multiple alerts/alerts/closeMultiple
• POSTConfirms all visible alerts/alerts/acknowledgeAll
• PUTUpdate a subscription's current prepaid settings./subscriptions/{subscriptionId}/prepaidSettings
• POSTWithdraw closure of multiple alerts/alerts/undoCloseMultiple
• POSTAcknowlegde multiple alerts/alerts/acknowledgeMultiple
• POSTQueue undo of multiple acknowledgments./alerts/undoAcknowledgeMultiple
• DELETERemoves a user or invitation from a team, and may delete the user if he is not in any team./teams/{teamId}/memberships/{userId}
• PUTUpdate user's team membership./teams/{teamId}/memberships/{userId}
• POSTClose an alert/alerts/{alertId}/close
• PUTUpdates team profile of a team/teams/{teamId}/profile
• POSTAnnotate Alert/alerts/{alertId}/annotate
• POSTUndo the closure of an alert./alerts/{alertId}/undoClose
• POSTAcknowledge an alert/alerts/{alertId}/acknowledge
• POSTSets alert settings of a specific team./teams/{teamId}/alertSettings
• DELETEDeletes a script instance./scripts/instances/{instanceId}
• PUTUpdates a given script instance, typically used for updating the configuration of a script./scripts/instances/{instanceId}
• POSTUndo the acknowledgement of an alert./alerts/{alertId}/undoAcknowledge
• PUTUpdates a subscriptions profile./subscriptions/{subscriptionId}/profile
• DELETEDelete an existing category/categories/{teamId}/{categoryId}
• PUTUpdate an existing category/categories/{teamId}/{categoryId}
• POSTSave multiple schedules./teams/{teamId}/schedules/multiple
• PUTUpdates custom data of a given script instance which includes its display name./scripts/instances/{instanceId}/data
• POSTDelete duty schedules in range/teams/{teamId}/schedules/deleteRange
• POSTEnables a script instance./scripts/instances/{instanceId}/enable
• POSTDisables a given script instance./scripts/instances/{instanceId}/disable
• DELETEDelete a specific duty./teams/{teamId}/schedules/{dutyId}
• POSTSet category subscriptions/categories/{teamId}/{categoryId}/subscriptions
• POSTChecks if a user has the provided permission./users/{userId}/checkPermissions

What HumDay can read from SIGNL4

These are the operations a schedule or a trigger can watch.

• GETGet User by Id/users/{userId}
• GETGet all Users/users
• GETGet overview event/events/{eventId}/overview
• GETGet duty status by user Id/users/{userId}/dutyStatus
• GETGet event parameters/events/{eventId}/parameters
• GETGets setup progress of a specific user./users/{userId}/setupProgress
• GETGet your subscription's current prepaid balance./prepaid/balance
• GETGet your subscription's current prepaid settings./prepaid/settings
• GETReturns all available inventory scripts which can be added to a SIGNL4 subscription./scripts/inventory
• GETGets a subscription's user licenses./subscriptions/{subscriptionId}/userLicenses
• GETReturns the subscription's channel price information./subscriptions/{subscriptionId}/channelPrices
• GETGet your subscription's prepaid transactions./prepaid/transactions
• GETGet Webhook by Id/webhooks/{webhookId}
• GETGet infos of a specific subscription./subscriptions/{subscriptionId}
• GETGet infos of all teams./teams
• GETGet Webhooks/webhooks
• GETGet infos of all available/managed subscriptions./subscriptions
• GETGets event sources of a specific team./teams/{teamId}/eventSources
• GETGet infos for all teams of the subscription./subscriptions/{subscriptionId}/teams
• GETGet Alert Report/alerts/report
• GETReturns the features of a specified subscription./subscriptions/{subscriptionId}/features
• GETGets the names of all alert category images./categories/images
• GETReturns all script instances of the SIGNL4 team/scripts/instances
• GETGet a subscription's current prepaid balance./subscriptions/{subscriptionId}/prepaidBalance
• GETGet a subscription's current prepaid settings./subscriptions/{subscriptionId}/prepaidSettings
• GETGet a subscription's prepaid transactions./subscriptions/{subscriptionId}/prepaidTransactions
• GETGets infos of a specific team./teams/{teamId}
• GETGet Alert/alerts/{alertId}
• GETGet all categories/categories/{teamId}
• GETReturns all inventory scripts./scripts/inventory/parsed
• GETReturns information of the duty schedule with the specified Id./teams/{teamId}/schedules/{scheduleId}
• GETReturns information about all duties that belong to the team./teams/{teamId}/schedules
• GETGet an overview alert./alerts/{alertId}/overview
• GETGet Information about downloadable reports/teams/{teamId}/dutyReports
• GETGet duty assistant info for a team/teams/{teamId}/dutysummary
• GETGet all invites of a team./teams/{teamId}/memberships
• GETGet metrics for all categories/categories/{teamId}/metrics
• GETGet information about downloadable alert reports/teams/{teamId}/alertReports
• GETGet annotations of an alert/alerts/{alertId}/annotations
• GETGet attachments of an alert/alerts/{alertId}/attachments
• GETGets alert settings of a specific team./teams/{teamId}/alertSettings
• GETGets setup progress of a specific team./teams/{teamId}/setupProgress
• GETGet alert notifications/alerts/{alertId}/notifications
• GETReturns all information about a given script instance which includes its runtime status./scripts/instances/{instanceId}
• GETGet a specific category/categories/{teamId}/{categoryId}
• GETReturns an inventory script by its id./scripts/inventory/parsed/{scriptId}
• GETDownload duty report with a specific fileName/teams/{teamId}/dutyReports/{fileName}
• GETReturns Alert Report/teams/{teamId}/alertReports/{fileName}
• GETGet metrics for a specific category/categories/{teamId}/{categoryId}/metrics
• GETGets a specified attachment of a specified alert./alerts/{alertId}/attachments/{attachmentId}
• GETGet category subscriptions/categories/{teamId}/{categoryId}/subscriptions

How automating SIGNL4 works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live SIGNL4 account.
4. Grant access, then go live. You approve the specific SIGNL4 operations it may use — and only those.

Automate SIGNL4 with these

• Zendesk636 operations
• Discord242 operations
• Twilio199 operations
• Slack174 operations
• Twilio Preview147 operations
• Circuitsandbox 2123 operations
• Intercom108 operations
• Twilio Conversations101 operations
• Telegram Bot74 operations
• Twilio Taskrouter60 operations
• WhatsApp Business55 operations
• www.zoomconnect.com54 operations

Categories

• Messaging

Questions about SIGNL4 automation

Can HumDay connect to SIGNL4?

Yes. HumDay reads SIGNL4's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 101 operations are documented.

Do I need to write code to automate SIGNL4?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your SIGNL4 account.

What can HumDay do in SIGNL4?

49 of the 101 documented operations change something in SIGNL4, and 52 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my SIGNL4 account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to SIGNL4 is held behind that approval.

Where this came from

The operations above are read from a published API description for SIGNL4 at connect.signl4.com/api/docs/v1/swagger.json. Descriptions are the provider’s own words, not ours. Last published 2021-06-21.