Utility
Webhook integration: signed data to Zapier, Make or your own backend
Custom Webhook sends data from OrqLabs to any HTTPS address. Reach systems outside the catalog through Zapier, Make, n8n or your own server, with requests optionally signed using HMAC-SHA256.
- Connection type
- Custom
- Scope
- Per organization: all projects share one key
- Capabilities
- CRM sync
- Setup time
- 10 min
What it does in OrqLabs
The webhook integration lets OrqLabs hand data to any system that isn't in the catalog. The Send webhook node POSTs the items it receives as JSON, and when Custom Webhook is the target of a Sync to CRM / Sheet node, each lead is sent to the same address as its own request. That's how you reach CRMs such as Pipedrive or Salesforce through Zapier, Make or n8n.
If you set a signing secret on the connection, every request is signed with HMAC-SHA256 over the Unix timestamp joined with the raw body, and the signature and timestamp arrive in separate headers. Your server verifies the signature and rejects stale timestamps to filter out forged and replayed requests. You can also add your own headers, such as Authorization, in Extra headers.
The Send webhook node delivers with a 10-second timeout. When it sends through the connected account, network errors, 429 and 5xx responses are retried automatically, other 4xx responses are not, and failed deliveries can be routed down the node's error output.
What you can automate
Anywhere via Zapier or Make
Use the Catch Hook URL from Zapier or the Custom webhook URL from Make as the Endpoint URL, then fan qualified leads, published posts or report summaries out to your other apps.
Leads into your own CRM
Select Custom Webhook in a Sync to CRM / Sheet node, and each lead reaches your system as its own signed request.
Agent output to internal systems
Add Send webhook after an agent node to forward a report, content plan or lead list to your own dashboard or data warehouse.
Event subscriptions without a workflow
Under Settings → Webhooks you can register endpoints for platform events such as lead qualified, post published or budget warning (outgoing webhooks guide).
Nodes that use this integration
In the workflow editor these nodes run with your Custom Webhook account.
Sync to CRM / Sheet
Pushes leads to HubSpot, Google Sheets, Notion or your own system, e.g. adding qualified leads to your sales team's spreadsheet.
Send webhook
Sends the workflow's data, signed, to another system's address; e.g. to push qualified leads into your CRM.
Setup at a glance
Get the webhook URL from the target system: Webhooks by Zapier → Catch Hook (Catch Raw Hook if you'll verify signatures), Custom webhook in Make, or the Production URL of an n8n Webhook node.
In OrqLabs, open Integrations → Custom Webhook → Connect and enter the address in Endpoint URL.
Optionally add a Signing secret and Extra headers as JSON.
Test connection sends a small test request to your address and shows the status code.
Add a Send webhook node, select this connection as its account and change the event name (default
workflow.output) if you like.
Requirements
- A public HTTPS address; internal networks and private IP addresses are refused for security.
- The endpoint must answer with a
2xxwithin 10 seconds; queue long work and respond right away. - If you want signatures, a secret you generate yourself (e.g.
openssl rand -hex 32). - Owner or Admin role in OrqLabs.
What you enter when connecting
- Endpoint URL *
- Signing secret (optional)
- Extra headers (JSON)
Good to know
- This integration only sends data out. To let an outside system start an OrqLabs workflow, use the Webhook trigger (guide).
- If you type an address directly into the Send webhook node, the request goes out without this integration's signing secret and extra headers; select the connected Custom Webhook account for signed delivery.
- Retries can deliver the same data more than once, so deduplicate on the receiving side by email or record ID.
- Zapier and Make apply their own task and operation limits.
Frequently asked questions
Can I use it without writing code?
Yes. Paste the URL Zapier or Make gives you as the Endpoint URL; signing is optional.
How do I verify the HMAC signature?
Join the received timestamp and the raw request body with a dot, compute HMAC-SHA256 with your secret and compare it in constant time with the sha256=-prefixed signature header. Don't re-serialize the body; header names and a Node.js example are in the help guide.
How is this different from an incoming webhook?
Custom Webhook sends data out of OrqLabs. To start a workflow from outside, add a Webhook trigger to it; the trigger can check a shared secret in the X-Webhook-Secret header.
How fast must my server respond?
Within 10 seconds, with a 2xx. Queue long-running work and reply with 202 right away.
Get started with OrqLabs
Build your first workflow today
Start on the free plan: connect your accounts, pick a template and stay in control with approval steps. No credit card required.