Saved filters let you define exactly which leads you care about. Pair them with webhook endpoints and auto-skiptrace to fully automate your lead flow.
A saved filter is a named set of criteria — lead types and/or counties — that you apply to your lead stream. You can create as many filters as you like from Dashboard → Automations.
Filters are evaluated against every new lead at insert time. A lead matches if it satisfies all active criteria (lead type AND county, if both are set).
Each saved filter can have one or more HTTPS webhook endpoints attached. When a lead matches the filter, a signed POST request is dispatched to all active endpoints.
Use the Test button to send a synthetic payload and confirm delivery before going live. See the full Webhook Docs for payload schema and signature verification code.
Toggle auto-skiptrace on any saved filter to enrich matching leads automatically before the webhook fires. Phone numbers and email addresses are appended to the webhook payload — no extra API calls needed on your end.
One skiptrace credit is consumed per unique lead enriched. If a lead was already skiptraced, results are reused for free.
See the Skiptrace Guide for details on credits and returned data fields.