send_sequenceDispatch a built sequence.
Once a sequence is built and reviewed, the agent needs to actually send. send_sequence dispatches the sequence through your connected sender (email provider, X DM, LinkedIn-via-MCP) on the schedule baked into the sequence, with throttling and tracking. Two credits. Returns a job id you can poll with sequence_status.
When to call this tool
Always after a human or higher-confidence agent has reviewed the sequence. The tool will fail-fast if the connected sender isn't authorised, if the recipient lacks a contact channel, or if the recipient is on the suppression list. It is intentionally a single-purpose dispatcher — sequence editing happens in the build step.
Input schema
{ "sequence_id": "…", "start_at": "…", "sender_id": "…" }
Output schema
{ "job_id": "…", "first_step_at": "…", "credits_used": 2 }
Example invocations
1. Claude Desktop
Send sequence seq_a92 starting tomorrow 9am Tokyo time.
2. ChatGPT custom GPT
After human approval ("approved", "send it"), call
send_sequence and report the job id back to the user.
3. Cursor MCP
Build a one-liner: foxapis send <seq_id> --start "now+1d".
4. n8n
{ "jsonrpc": "2.0", "method": "tools/call", "params": { "name": "send_sequence", "arguments": { "sequence_id": "seq_a92" } } }
5. Raw curl
curl -X POST https://www.mentionfox.com/mcp \ -H "Authorization: Bearer $FOXAPIS_KEY" \ -d '{"jsonrpc":"2.0","method":"tools/call","params":{"name":"send_sequence","arguments":{"sequence_id":"seq_a92","start_at":"2026-05-11T00:00:00Z"}}}'
Sample output
{ "job_id": "job_zk9", "first_step_at": "2026-05-11T00:00:00Z", "credits_used": 2 }
Credit cost & rate limits
2 credits per dispatch. 120 per minute.
Error codes & recovery
403 SENDER_NOT_AUTHEDConnect the sender in the dashboard.409 SUPPRESSEDRecipient is on the suppression list.422 NO_CHANNELNo reachable channel for recipient.