Nº 35 · Integrations
Build on SIGNL with Custom Webhook
One inbound address, secured by a per-client secret. See what syncs, where it stops and how to set it up.
Applications open soon
See the whole workspaceWorks with Custom Webhook
What it does
Generic inbound channel secured by a per-client bearer secret.
What syncs
What it covers
3- Arbitrary events
- Score + tag mutations
- Bearer auth
Automation triggers
1- Webhook Received
What it does not do
- It takes five kinds of event: page views, booked calls, form submissions, payments and custom events. Anything else is refused.
Set it up
Connect in SIGNL
- Create an API key in Settings, or use this workspace's webhook secret.
- POST JSON to /api/webhooks/inbound with it; each delivery appears under Recent deliveries.
Questions people ask
What does SIGNL receive from Custom Webhook?
From Custom Webhook: Arbitrary events, Score + tag mutations, Bearer auth. Data moves one way, into SIGNL.
How do I set up the connection to Custom Webhook?
It takes 2 steps, listed above. The first: Create an API key in Settings, or use this workspace's webhook secret.
Where does the connection to Custom Webhook stop?
Here is where the Custom Webhook connection stops. It takes five kinds of event: page views, booked calls, form submissions, payments and custom events. Anything else is refused.
How ready is the connection to Custom Webhook?
The Custom Webhook connection is built and switched on for every workspace.
Can an automation start from or act on Custom Webhook?
Yes. The builder offers 1 trigger (Webhook Received).
Keep going
All product names and logos belong to their owners. They identify integrations only and do not imply endorsement.