Use Close CRM's bulk email sequence enrollment API to add a list of leads to a sequence, handle partial failures, and track sequence state via the activity feed
domain: close.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
GET /api/v1/sequence/ to retrieve available sequences and identify the sequence ID to enroll leads into
POST /api/v1/sequence/{sequence_id}/subscription/ for each lead with a body containing 'lead_id' and optionally 'assigned_to' (sender user ID) to create the enrollment
Parse each response for the 'id' (subscription ID) and 'status' field; a status of 'paused' or 'error' indicates the enrollment did not activate successfully
GET /api/v1/activity/?lead_id={lead_id}&type=Email to poll the activity feed and confirm the first sequence email was sent or scheduled
POST /api/v1/sequence/{sequence_id}/subscription/{subscription_id}/pause or /resume to manage sequence state per lead
Known gotchas
Close CRM sequence enrollments are per-lead, not per-contact; if a lead has multiple contacts, the sequence targets the lead's primary contact by default — verify the correct contact receives the emails
A lead can only have one active subscription per sequence at a time; attempting to enroll an already-enrolled lead returns a 400 error with 'already subscribed' message rather than creating a duplicate
The Close API uses HTTP Basic Auth with the API key as the username and an empty password; passing the key as a Bearer token returns a 401 even though it looks like a valid token format
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?