What events can trigger an outbound webhook?

You select the event that should trigger each outbound webhook when you configure it, then trigger it once and check the receiving system and the delivery log. Confirm the events and payload structure you need with our team before you build against them.

Should I use Zapier or a webhook?

Use Zapier for no-code connections to common applications - it suits a business user. Use a webhook for a direct connection to a system you control - it suits a developer. Zapier is a separate add-on module. Where a dedicated integration already exists, use that instead.

How do I know whether a webhook was delivered?

Check the delivery log. It records each attempt made by the webhook engine and its result, so it is the first place to look when an automation appears not to have run.

Can a webhook create records?

The engine supports inbound webhooks as well as outbound, so an external system can send data in. Confirm the supported inbound actions with our team for your use case.

Is this how an AI assistant connects?

No. AI assistants connect through the MCP server, signing in with your account or using a personal access token, so your own permissions and audit trail apply. A webhook cannot bypass CrmLeaf's rules and permissions.

Who can set up webhooks, and is it on every plan?

Only Administrators can configure webhooks. The webhook engine is an add-on module, so confirm plan inclusion before building a process that depends on it.

Developers · Webhooks · add-on

Configurable webhooks with a delivery log you can actually debug

The webhook engine gives you configurable outbound and inbound webhooks with a delivery log, for when you or a developer want a direct connection to CrmLeaf rather than a middleware service like Zapier.

Start Free Trial →Book a 30-min Demo

Free trial
No credit card
Free onboarding

Webhooks · Delivery logEvery attempt recorded

Destination

POST https://hooks.example.com/crmleaf

lead.created
Outbound · 09:41:12
200
deal.stage_changed
Outbound · 09:38:05
200
invoice.paid
Outbound · 09:31:47
500
contact.upsert
Inbound · 09:29:30
202

invoice.paid failed - attempt and result in the log

How it works

How a webhook fires

01
Enable module
An Administrator turns on the Webhooks add-on in Settings → Module Settings.
02
Configure destination
Point an outbound webhook at a URL you own.
03
Trigger the event
Something happens in CrmLeaf that matches a configured trigger.
04
Delivery recorded in log
Every attempt is recorded in a delivery log, so a missed automation is easy to diagnose.
05
Receiving system acts
Your system receives the payload and acts on it.

Outbound vs inbound

Two directions, one delivery log

Outbound webhooks

Send data to a URL you own when something happens in CrmLeaf.

See how it works

Inbound webhooks

Let an external system send data into CrmLeaf.

See how it works

Delivery log

Every attempt is recorded, so a missed automation is easy to diagnose rather than a mystery.

See how it works

In detail

Where webhooks sit versus other integrations

Several other integrations are already webhook-driven under the hood, including Meta Lead Ads, Calendly bookings, Gupshup delivery reports and payment gateway notifications - those have their own dedicated settings and don't need to be rebuilt here. Zapier remains the no-code path for an ops person; webhooks are the developer surface for a systems integrator who wants direct HTTP control.

Add-on module
Administrators configure
Delivery log

Built in

Configurable outbound webhooks to a URL you own
Inbound webhooks for external systems to send data in
A delivery log recording every attempt and its result
Cannot bypass CrmLeaf's own rules and permissions - use tokens for permission-aware AI access
Webhooks move business data out of the platform - only send to destinations you control

FAQ

Wire up your own event-driven integration

Configure an outbound webhook and see every delivery attempt in the log.

Start Free Trial →Book a 30-min Demo

Configurable webhooks with a delivery log you can actually debug

How a webhook fires

Enable module

Configure destination

Trigger the event

Delivery recorded in log

Receiving system acts

Two directions, one delivery log

Outbound webhooks

Inbound webhooks

Delivery log

Where webhooks sit versus other integrations

Frequently asked questions

Explore further

Webhooks guide

Public API (mTLS)

Workflow Automation

All integrations

Wire up your own event-driven integration