Collect data from third parties with webhooks
Intempt collects events from the webhooks of supported third-party software. The vendor pushes its own event stream to your Intempt collector, where it is normalised onto a named stream and attributed to a source.
Intempt collects events from the webhooks of supported third-party software.
Webhooks let a third party send its own internal event stream to your Intempt collector for further processing. They are sometimes called streaming APIs or HTTP response APIs. A webhook event is not loaded loose: it is verified, attributed to a source, normalised onto a named stream, and written to the same customer profile your SDK events land on.
How a connector is put together
Every platform source has two halves, because neither half can do the other's job.
| Half | What it does | Why it is not enough alone |
|---|---|---|
| Historical load | Runs once, at connect time. Loads the vendor's existing records | Cannot deliver anything after it finishes |
| Webhook stream | Delivers every event from registration onward, in seconds | Cannot produce history. It starts when you register it |
You get both from one connect flow. The historical load runs first, the connector reports connected only when it finishes, and the webhook carries everything after that. Both halves are attributed to the same source, so a profile assembled from history and live events shows one continuous timeline.
Backfilled records never trigger journeys, workflows or experiments. Loading two years of orders does not send two years of email.
Research Preview. Webhook sources are rolling out account by account. Ask your Intempt contact to enable a connector for your workspace.
Supported webhooks
| Webhook | Track |
|---|---|
| Shopify | Orders, checkouts, customers and products from your store |
| Stripe | Payments, subscriptions, invoices and disputes |
| HubSpot | Contact, company and deal changes logged by HubSpot |
| Klaviyo | Email and SMS engagement logged by Klaviyo |
| Chargebee | Subscription state, invoices and payment events |
| Intercom | Conversations, replies and contact changes |
| Zendesk | Tickets, comments and satisfaction ratings |
| Freshdesk | Tickets, replies and contact changes |
| Typeform | Form responses as they are submitted |
| Generic webhook | Any JSON payload from any source |
The full connector list
Seventeen connectors, in two waves. Every one pairs a webhook with an Airbyte source that Airbyte itself certifies, and every one serves a GTM team in ecommerce or SaaS.
| Vendor | Group | Wave | Also a destination |
|---|---|---|---|
| Shopify | Commerce | 1 | |
| Stripe | Payments | 1 | |
| HubSpot | CRM | 1 | Yes |
| Klaviyo | Messaging | 1 | |
| Chargebee | Payments | 1 | |
| Intercom | Support | 1 | |
| Freshdesk | Support | 1 | Yes |
| Zendesk Support | Support | 1 | |
| Typeform | Lead capture | 1 | |
| Generic collector | Any | 1 | |
| Salesforce | CRM | 2 | |
| Mailchimp | Messaging | 2 | |
| WooCommerce | Commerce | 2 | |
| PayPal | Payments | 2 | |
| SendGrid | Messaging | 2 | Yes |
| Slack | Routing | 2 | Yes |
| Twilio | Messaging | 2 | Yes |
Five are already destinations. HubSpot, Freshdesk, SendGrid, Slack and Twilio can already receive from Intempt. Adding the source closes the loop on one profile: we send the message, their webhook tells us it was opened, and both sit on the same timeline.
Why certified only
Airbyte marks a source certified when Airbyte maintains and supports it. Community sources are contributor-maintained with no such commitment.
That matters more than it looks. If a community connector breaks, the backfill breaks while the webhook keeps running, so new events keep arriving and history quietly does not. The profile reads as healthy and is incomplete. We would rather ship fewer sources than one that fails in a way you cannot see.
Recharge, Gorgias and Calendly all have webhooks and all have Airbyte sources, but those sources are community-maintained, so they are not on this list.
Vendors that cannot be collected by webhook
Some systems publish no outbound webhook at all. Databases, warehouses and object stores are pull-only by design, and so is every major ad platform: Google Ads, Google Analytics 4, Bing Ads, Amazon Ads, LinkedIn Ads, Snapchat and TikTok.
Those are still available as scheduled sources, on a sync interval rather than a live stream. The connector catalogue marks which of the two you are getting, because the difference decides whether a journey can be triggered by the event or only reported on afterwards.