Skip to main content
Outcome: workflows that run without anyone asking — inbound leads answered in minutes, lists that stay clean, dormant contacts revived on a schedule.

​
Best interface

API + webhooks — event-driven automation is REST-only: subscribe once, react in real time. CLI + cron — scheduled jobs like a weekly hygiene sweep are a natural fit for --json composition.

​
Pattern 1: Event-driven (inbound lead follow-up)

Speed-to-lead is most of the conversion rate. This loop is event-driven end to end — no polling:
1

Receive the signal

A webhook event (or your product’s own signup/demo-request event) tells the agent a lead arrived. Payload shapes: Webhook event payloads.
2

Upsert and qualify

Create/update the contact with source context in custom fields (Create contacts); score against your ICP.
Auto-enrichment of the lead is coming soon (Enrichment API).
3

Route to the right sequence

Hot leads → short, direct sequence; colder → nurture. Add the contact and start (Launch outreach). For an immediate one-off first response outside a sequence, use the outreach-action endpoints (API Reference).
4

Manage the conversation

Watch reply categories and meeting intent (Process replies); meetings and activity land in reporting automatically.

​
Pattern 2: Scheduled (list hygiene + re-engagement)

Deliverability is a compounding asset. A weekly cron sweep keeps the base clean, then re-engages what survives:
1

Segment stale and risky contacts

Filter by last activity, bounce history, or missing fields. GET /v3/contacts/filter/fields lists the fields, operators and values your workspace accepts; page with top and skip until hasMore is false.
2

Validate and suppress

Schedule email validation across the segment; add bounced domains, opt-outs, and competitor domains to blacklist rules (Suppression & Blacklist API — see API Reference).
3

Prune and re-segment

Bulk-update or remove dead records; move survivors into clean lists.
4

Re-engage the dormant segment

Run a light-touch sequence (2–3 low-pressure touches) against contacts that finished without converting. Load reengagement cards into a Jason knowledge base for a fresh angle (Build an AI SDR).
Re-enrichment before re-engagement (“did they change jobs?”) is coming soon.
5

Measure the effect

Compare bounce and reply rates before/after with POST /v3/reporting/emails/overview (its compareTo field returns the trend against a previous period); track the revival rate to decide if the sweep becomes quarterly.

​
Availability notes

  • Webhooks, contact CRUD, validation, suppression, sequences, and reporting: available today.
  • Enrichment-dependent steps (lead auto-enrichment, dormant-refresh): coming soon.