How do I create records only for some webhooks (AI filter)?

Updated October 19, 2026

The AI filter reads each incoming webhook and decides whether it should create a record. Use it to keep out noise: personal email addresses, test submissions, event types you don't care about. Your endpoints are in Settings → Webhooks.

Owners, admins and managers can set the filter. It uses tokens on every webhook received, about 0.1 to 0.4 tokens each, even for the webhooks it skips.

Step by step

Open your endpoint from Settings → Webhooks → Manage receive endpoints. While you create an endpoint, the filter is on the last step, Activate.
Open the Settings tab and find Filter webhooks with AI.
Turn on Enable AI condition, then describe in Your condition (natural language) when to create a record. It saves when you click outside the box.
Click Run preview to test the condition on the test payload. The Decision reads Create record or Skip, with the reason.

A good condition names what the payload must contain, for example "Only create if the lead has a business email and the company has more than 10 employees." Click one of the examples under the box to start from it. On a new endpoint, the filter starts working when you click Confirm & Activate.

Good to know

The AI sees only the webhook's payload and your condition. It can't look up your Breakcold records, so a condition like "only if this person isn't already in my CRM" doesn't work. Use a unique identifier for that: matching records are updated instead of duplicated.
The AI is strict: when the payload doesn't clearly meet the condition, the webhook is skipped.
The filter runs once per webhook on the whole payload, before the mapping. A payload holding a list is kept or skipped as a whole.
A skipped webhook shows Skipped in the Delivery Logs. View log details shows the AI's decision and its reason.
When your organization has no tokens left, the filter can't run and every webhook is skipped.
On an existing endpoint, the filter works as soon as you turn it on, starting with the first example as the condition. Write your own condition right away.
Turn the filter off for high volumes, or when every webhook should create a record.

Still stuck?

Step by step

Open your endpoint from Settings → Webhooks → Manage receive endpoints. While you create an endpoint, the filter is on the last step, Activate.

Open the Settings tab and find Filter webhooks with AI.

Turn on Enable AI condition, then describe in Your condition (natural language) when to create a record. It saves when you click outside the box.

Click Run preview to test the condition on the test payload. The Decision reads Create record or Skip, with the reason.

Good to know

The AI sees only the webhook's payload and your condition. It can't look up your Breakcold records, so a condition like "only if this person isn't already in my CRM" doesn't work. Use a unique identifier for that: matching records are updated instead of duplicated.

The AI is strict: when the payload doesn't clearly meet the condition, the webhook is skipped.

The filter runs once per webhook on the whole payload, before the mapping. A payload holding a list is kept or skipped as a whole.

A skipped webhook shows Skipped in the Delivery Logs. View log details shows the AI's decision and its reason.

When your organization has no tokens left, the filter can't run and every webhook is skipped.

On an existing endpoint, the filter works as soon as you turn it on, starting with the first example as the condition. Write your own condition right away.

Turn the filter off for high volumes, or when every webhook should create a record.

How do I create records only for some webhooks (AI filter)?

Step by step

Good to know

Related

How do I create records only for some webhooks (AI filter)?

Step by step

Good to know

Related