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 Outgoing Webhooks
Set up outgoing webhooks to push TrustPager events — opportunity updates, contact creation, form submissions, and more — to any external endpoint in real time.
Outgoing webhooks let TrustPager push data to your own systems the moment something happens in the CRM. Instead of polling the API for changes, you register an endpoint and TrustPager POSTs a payload to it automatically — for every event you care about, in real time.
There are two ways to set up outgoing webhooks depending on your use case:
- Outgoing webhook configs — configured per workspace, useful for sending data to external tools when automations fire
- API webhook subscriptions — configured via the API or MCP, designed for developers and AI agents receiving platform events
Outgoing webhook configs
Outgoing webhook configs let you define a named endpoint that TrustPager can call from an automation action. Go to https://app.trustpager.com/settings/api to create and manage them.
When creating a config, you'll fill in:
- Name — a friendly label (e.g. "Notify Slack", "Push to custom CRM")
- URL — the endpoint TrustPager will POST to
- Headers — optional key/value pairs added to every request (e.g.
Authorization: Bearer your-token) - Trigger events — which platform events fire this webhook
- Include trigger data — whether to include the full event payload in the request body
Once saved, the webhook can be used as an action inside any automation at https://app.trustpager.com/auto/automations. TrustPager sends a POST with a JSON body whenever the trigger fires.
Testing a webhook config
Every outgoing webhook config has a test action. TrustPager sends a sample payload to your endpoint immediately so you can confirm it's reachable before wiring it into a live automation. The test result — response code, duration, and any error — is logged and visible in the delivery log for that config.
View delivery logs at https://app.trustpager.com/data/webhooks. Each log entry shows the URL called, the event that triggered it, the HTTP response code, duration in milliseconds, and any error message. Whether it was a live delivery or a test is also recorded.
API webhook subscriptions
If you're building an integration using the TrustPager API or MCP, webhook subscriptions are the right tool. They let you subscribe to platform events and receive a POST to your endpoint every time one fires — without touching the automation builder.
Create a subscription via the API:
POST https://api.trustpager.com/v1/webhooks/subscribe
Authorization: Bearer tp_live_xxxxxxxxxxxx
Content-Type: application/json
{
"url": "https://your-server.com/trustpager-events",
"events": ["opportunity.updated", "contact.created", "form.submitted"],
"secret": "your-signing-secret"
}Or via the MCP tool create_webhook_subscription with the same three fields.
The events array accepts any combination of platform event names. Use list_webhook_subscriptions (MCP) or GET /webhooks/subscriptions (API) to see your active subscriptions and their delivery status.
Event payload and signature verification
TrustPager signs every delivery with the secret you provided at subscription time. The signature is included in the X-TrustPager-Signature request header. Verify it on your server before processing the payload:
// Node.js example
const crypto = require('crypto');
function verifySignature(rawBody, signature, secret) {
const expected = crypto
.createHmac('sha256', secret)
.update(rawBody)
.digest('hex');
return crypto.timingSafeEqual(
Buffer.from(expected),
Buffer.from(signature)
);
}Always verify the signature before acting on the payload. Any request that fails verification should be rejected with a 401.
Retries and delivery logging
If your endpoint returns a non-2xx response or times out, TrustPager retries the delivery automatically. Each attempt is logged with the event type, attempt count, response code, duration, and any error message.
For API subscriptions, view delivery logs via GET /webhooks/subscriptions/{id}/logs or the MCP tool list_webhook_subscription_logs. Subscriptions that accumulate repeated failures are flagged with a disabled_reason — check the subscription's failure_count and last_delivered_at fields to diagnose issues early.
For outgoing webhook configs, logs are available at https://app.trustpager.com/data/webhooks.
Managing your API key scopes
Both outgoing webhook configs and API subscriptions require the webhooks:write scope on your API key to create or update, and webhooks:read to list or view logs. Deleting a webhook requires webhooks:delete. Manage your keys and scopes at https://app.trustpager.com/settings/api.
Tip: Use API webhook subscriptions when you're building an integration that needs to react to platform events — they're simpler to wire up than polling. Use outgoing webhook configs when you want a named, reusable endpoint that your team can drop into any automation without touching code.
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.