Take 10 minutes.
Get hours back every week.
Short walkthroughs that turn the platform into your operations team: automated pipelines, instant follow-ups, AI-handled admin. One video, one less thing to do manually.
How to Use Incoming Webhooks to Trigger Automations
How to create an incoming webhook URL in TrustPager, configure optional authentication, and connect external systems — forms, Zapier, Make, or custom apps — to trigger automations automatically.
Incoming webhooks let external systems fire a TrustPager automation by sending an HTTP POST to a unique URL. Instead of polling or manual imports, you define the integration once — and any time your form tool, Zapier zap, Make scenario, or custom app POSTs to that URL, the automation runs immediately.
How it works
Each incoming webhook is a generated URL tied to a specific automation in TrustPager. When an external system sends a payload to that URL, TrustPager fires the automation exactly as if it had been triggered manually — all configured actions execute in sequence, the run is logged, and the full audit trail is available at https://app.trustpager.com/auto/automations.
The webhook URL format is:
POST https://ucqwijexmjctglmrxlej.supabase.co/functions/v1/automations_webhook/{webhook_id}The webhook_id is unique to each incoming webhook you create. You never type it manually — TrustPager generates it and shows the full URL in the automation builder.
Setting up an incoming webhook
Open the automation you want to trigger at https://app.trustpager.com/auto/automations. In the automation builder, set the trigger type to Webhook Received. A configuration panel will open — fill in the following:
- Webhook Name — a friendly label to identify the source (e.g. "Lead Gen Form", "Zapier Contact Sync")
- Enable Authentication — toggle this on if you want to require a secret header. When enabled, enter a Webhook Secret of your choosing.
Click Create Webhook. TrustPager generates a unique URL immediately and displays it in the panel.
Your webhook URL and authentication headers
Once created, the panel shows your ready-to-use webhook URL. Copy it and paste it into your external service — the form builder, Zapier, Make, or wherever the POST will originate from.
If you enabled authentication, the panel also shows the header your external service needs to include with every POST:
- Header name:
x-webhook-secret - Header value: the secret you entered
Requests that arrive without the correct header will be rejected. This keeps your automation protected from unauthorised calls.
If you did not enable authentication, any POST to the URL will trigger the automation. This is fine for internal tools or services running in a private network, but for public-facing integrations it is worth enabling the secret.
What to POST
TrustPager accepts any valid JSON body. You can send the payload as-is from your external system — field names, structure, and values are all up to you. The automation receives the full payload and can use those values in its actions (for example, populating a contact field from a form submission value).
A minimal test POST looks like this:
curl -X POST https://ucqwijexmjctglmrxlej.supabase.co/functions/v1/automations_webhook/{your_webhook_id} -H "Content-Type: application/json" -H "x-webhook-secret: your-secret" -d '{"name": "Jane Smith", "email": "jane@example.com", "source": "contact-form"}'Common use cases
- Third-party form tools — Typeform, JotForm, Gravity Forms. Set the webhook destination to your TrustPager URL and new submissions trigger the automation instantly.
- Zapier / Make — Use a "Webhooks by Zapier" or Make HTTP module as the last step of a zap/scenario. Point it at your TrustPager URL to pass data across platforms.
- Custom applications — Any app that can fire an HTTP POST can trigger a TrustPager automation. No SDK or special library required.
- CRM data from other tools — Receive contact or opportunity data from a legacy system and use automation actions to create or update records in TrustPager.
Viewing webhook activity
Every incoming webhook call is logged. You can see all webhook activity at https://app.trustpager.com/data/webhooks. Each log entry shows the timestamp, the payload received, and whether the automation fired successfully.
For automation run history — the actions that executed and their outcomes — open the automation at https://app.trustpager.com/auto/automations and check the Run History tab.
Managing your webhooks
You can rename or update a webhook's secret at any time by opening the automation and clicking the webhook trigger configuration. Rotating the secret takes effect immediately — update the header value in your external service at the same time to avoid dropped calls.
Deleting a webhook disables the URL permanently. Any POSTs to the old URL after deletion will not trigger the automation.
Tip: Give each incoming webhook a descriptive name that reflects its source — "Typeform Lead Capture" is easier to debug six months later than "Webhook 1". When testing, send a minimal payload first to confirm the automation fires, then add the full data structure your service will send in production.
Two ways to
meet FinalPiece.
Talk to Evie right now, or book a real human for a deeper walkthrough. Whichever feels right.
Pick up the phone.
Hear her in 10 seconds.
- RealHer voice passes for human.
- SmartKnows your prices, hours, and trade.
- PatientPolite, attentive, never has a bad day.
Pencil us in.
60 minutes with a real human · Google Meet · Free.