Connect to your whole stack
Inbound and outbound webhooks let your WorkApps tools talk to the rest of your stack. Native Zapier support is coming soon — connect to 7,000+ apps without writing an endpoint.
Outbound Webhooks
Notify any service when something changes
When a record is created, updated, or deleted in your app, WorkApps fires a signed HTTP POST to any endpoint you specify. No polling, no middleware, no glue code.
- Post to Slack when a new request is submitted
- Trigger an email when a record status changes
- Sync updates to your CRM or ERP in real time
- Hit any internal API on any app event
Inbound Webhooks
Let external services push data in
WorkApps generates a unique inbound URL per connection. Give it to any external service — a form builder, CRM, payment processor — and incoming payloads automatically create or update records in your app.
- Accept form submissions from Typeform, Tally, or any provider
- Create records from CRM events or deal stage changes
- Receive payment webhooks from Stripe or similar
- Connect to any service that can send an HTTP POST
Built for reliability
Webhooks that work when you need them — and give you the visibility to know when they don't.
Outbound webhooks
Notify any external service when something changes in your app. A new record submitted? Fire a webhook to Slack, your CRM, an email service, or any HTTP endpoint.
Inbound webhooks
Let external services push data into your app. A form submission, a CRM update, a payment event — inbound webhooks accept the payload and create or update records automatically.
Secure signing
Every webhook is scoped to its app and signed with a secret. Your receiving endpoint can verify the signature to confirm the request came from WorkApps.
Automatic retries
Failed deliveries are retried automatically. No manual intervention needed if the receiving endpoint is temporarily unavailable.
Webhook logs
Every delivery attempt is logged — payload, response code, and timestamp. Baseline keeps 7 days. Enterprise keeps 30. Compliance keeps 90.
Per-app scoping
Webhooks are configured per app, not org-wide. Each app manages its own connections independently — no risk of one tool's webhooks affecting another.
Connection limits by plan
Start with 3 connections per app. Scale up with Enterprise or Compliance.
Common questions
What services can I connect to?
Any service that accepts HTTP requests — Slack, email providers, CRMs, ERPs, internal APIs, and more. Outbound webhooks POST a JSON payload to any URL you specify. Native Zapier support is coming soon, which will open up 7,000+ apps without any endpoint configuration.
How do inbound webhooks work?
WorkApps generates a unique inbound URL per connection. You give that URL to the external service (e.g. a form builder or CRM). When it fires, WorkApps receives the payload and can create or update records in your app.
What happens if a delivery fails?
Failed deliveries are retried automatically. You can also inspect the delivery log to see the response code and payload for any attempt.
How do I verify a webhook came from WorkApps?
Every outbound webhook is signed with a per-connection secret. Your endpoint can verify the HMAC signature in the request header to confirm authenticity.
Can I increase the 3-connection limit?
Yes — the Enterprise add-on raises the limit to 25 inbound and 25 outbound connections per app, and extends log retention to 30 days. The Compliance add-on includes the same limits with 90-day log retention.
When will Zapier be available?
Native Zapier integration is on our roadmap. If you'd like early access or want to be notified when it launches, reach out via the contact page and we'll keep you posted.
Explore more features
Ready to connect your stack?
Webhooks are included on every Workflow plan. Sign up and start connecting in minutes.