Enroll a contact in a Reply.io sequence with dynamic content generation.
Sequences
Enroll a contact in a Reply.io sequence with dynamic content generation.
Enroll a contact in a Reply.io sequence with dynamic content generation.
Works even if the contact does NOT yet have a Pipedrive record — the
provided overrides (first_name/last_name/company/title/linkedin_url/phone)
are used to synthesize a person object for the content generator.
Required:
sequence_id: Lowercase slug (e.g. "healthcare-cold"). Must match a Reply
campaign name AND have a corresponding playbook in Spaces
(docs/spaces/sequences/<slug>.yaml) unless `sequence` is
passed inline.
email: Target email address.
Optional overrides (used in content generation when no PD record exists):
first_name, last_name, company, title, linkedin_url, phone
Optional rich config:
sequence: Full sequence playbook dict (summary, steps, voice, etc.).
If omitted, loaded from Spaces by slug. See workflows/sequence.py
module docstring for the schema.
campaign: Campaign metadata {summary, template_path, campaign_id} for UTM
tagging and prompt augmentation.
ignore_duplicate: If true (default), Reply.io ignores duplicate-contact errors.
Returns:
{sequence_id, reply_campaign_id, email, generated_steps, reply: {...}}
POST
Enroll a contact in a Reply.io sequence with dynamic content generation.
Authorizations
Body
application/json
Response
Tool result. The shape is tool-specific; most tools return a JSON object, some a {"result": ...} envelope.
The response is of type object.