Workflows

Lead intake can start a workflow automatically. A newly created lead fires the new_lead trigger with campaign context, while a deduplicated lead returns without creating duplicate workflow work.

Typical flow

External form → lead intake → dedupe → contact sync → new_lead trigger
              → lead.created webhook → optional dial hopper

Reliable orchestration

• Use one source-specific API key with leads:write.
• Set source consistently for attribution.
• Use the intended list_id; a configured fallback is operational safety, not routing logic.
• Enable hopper only when the lead should be immediately eligible for dialing.
• Store returned lead_id as the canonical identifier.
• Use message operation_id values when a downstream workflow sends outreach.

Deduplication behavior

Phone deduplication is scoped to a list and uses the last 10 digits. If cross-list identity matters, resolve that in the source system or perform an explicit lookup before intake.