Cby Close
Subscribe a contact to a sequence
Enrolls a contact in a sequence (workflow), whose timed email and call steps run until the contact replies.
Description
The docs' example request names the sequence (`sequence_id`), the contact (`contact_id` and `contact_email`), the sender (`sender_account_id`, `sender_name` and `sender_email`) and `calls_assigned_to`, a list of user IDs. Subscribing starts real outbound email: confirm the sequence, sender and contact first. The MCP server can create a draft sequence (`create_workflow`) but has no tool that subscribes contacts.
subscribe-to-sequence.md
Subscribe a contact to a sequence
Enrolls a contact in a sequence (workflow), whose timed email and call steps run until the contact replies.
The docs' example request names the sequence (sequence_id), the contact
(contact_id and contact_email), the sender (sender_account_id,
sender_name and sender_email) and calls_assigned_to, a list of user IDs.
Subscribing starts real outbound email: confirm the sequence, sender and
contact first. The MCP server can create a draft sequence
(create_workflow) but has no tool that subscribes contacts.
Set up
Use the first option your agent supports.
API (official)
- Base URL: https://api.close.com/api/v1
- Endpoint:
POST /sequence_subscription/ - Auth: send the header
Authorization: Basic $CLOSE_API_KEY - Docs: https://developer.close.com/api/overview
Before doing anything else, make one read-only call to confirm access.
Rules
- Ask the user before anything that sends messages, costs money, or changes data.
- Never print API keys.
Built from these files in the repository
The layout and the rules come from lib/catalog/render-markdown.ts, the set-up wording from lib/catalog/render-access.ts.
Ways in
| Route | Source | Call | Required | Docs |
|---|---|---|---|---|
| Official | POST /sequence_subscription/ | API key in $CLOSE_API_KEY | Docs |