Sequencers

A sequencer is the tool your customer sends cold email from: Instantly, Smartlead or EmailBison. Connect an account there once, then export mailboxes into it: one, a list, or every mailbox on a domain. For each mailbox we trust the tool's Google app on the domain, add its tracking record if you turned custom tracking on, put the mailbox into the tool, and set its warmup, limits and tags.

Nothing here is billed. Connecting, exporting, retrying and removing are free.

What each tool needsCopy Anchor Link

GET /v1/sequencers/platforms answers the same list, with each field, whether it is required, and the range of every setting. Build a form from it rather than writing the ranges down.

Connect an accountCopy Anchor Link

curl -X POST https://resellerhq.com/api/v1/sequencer-connections \
  -H "Authorization: Bearer $RHQ_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{ "name": "Acme Instantly",
        "platform": "instantly",
        "apiKey": "…",
        "settings": { "warmupLimit": 20, "dailyLimit": 30, "customTracking": true } }'

We check the account with the tool before saving it. One the tool refuses is answered 422 with the reason (api_key_invalid, invalid_credentials, missing_credentials, workspace_expired or workspace_not_found), and nothing is saved. If the tool can't be reached, it's 502 sequencer_unavailable: try again.

Keys and passwords are never shown again. They are kept sealed by our mailbox platform and used only to add mailboxes for you. ResellerHQ never stores them, and no answer, event or log line carries them: a connection only says hasApiKey and hasPassword.

Each connection is checked with its tool every day. One the tool stops accepting turns status: invalid with a statusReason and a statusMessage saying what to do, and sends sequencer_connection.invalid. New exports to it are refused with connection_invalid until you fix it with PATCH /v1/sequencer-connections/{id} (new details are checked first) or it passes POST /v1/sequencer-connections/{id}/validate.

SettingsCopy Anchor Link

Applied to every mailbox exported through the connection. Null leaves the tool's own default.

A change to the settings applies to mailboxes exported from then on.

Export mailboxesCopy Anchor Link

curl -X POST https://resellerhq.com/api/v1/sequencer-exports \
  -H "Authorization: Bearer $RHQ_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{ "connectionIds": ["sqn_01K6..."], "mailboxDomainId": "mdm_01K6..." }'

Send mailboxIds (up to 1,000) or mailboxDomainId for every mailbox on a domain, and one to five connectionIds. You get one export per mailbox and connection: 12 mailboxes to 2 tools are 24 exports. The answer (202) has three lists:

• created: the new exports.
• alreadyExported: pairs that already had one, on its way, done or failed. A repeat never makes a second.
• skipped: each mailbox that got no export, with its reason and a message. Only a mailbox that is set up (active) can be exported, so one still being set up is mailbox_not_active. None is ever left out silently.

Each export then runs on its own, in steps:

A step that goes wrong for a passing reason is tried again with backoff: the export stays queued with retrying: true, lastError and nextRunAt. One that needs something fixed at the tool stops as failed with a reason, and sends sequencer_export.failed.

GET /v1/sequencer-exports lists them, one row per mailbox and tool, filtered by connectionId, mailboxId, mailboxDomainId, platform or status. Its counts say how many are in each status across every page.

Which tools a mailbox is inCopy Anchor Link

GET /v1/mailboxes and GET /v1/mailboxes/{id} show each mailbox's sequencers: the connection, tool and status of every export it has that wasn't removed. GET /v1/mailboxes filters by sequencerConnectionId or platform, and notExported=true lists the mailboxes in no tool at all.

When an export failsCopy Anchor Link

Fix the reason at the tool, then retry: POST /v1/sequencer-exports/{id}/retry for one, or POST /v1/sequencer-exports/retry with up to 500 ids. Each export also has reasonMessage, which says the same as this table.

Remove a mailbox from a toolCopy Anchor Link

DELETE /v1/sequencer-exports/{id} takes the mailbox back out of the tool where its API allows it (Instantly and EmailBison, removedAtSequencer: true) and marks the export removed, either way. Smartlead has no way to, so take the mailbox out in Smartlead yourself. A removed pair can be exported again.

DELETE /v1/sequencer-connections/{id} forgets the account and its keys. Mailboxes already in the tool stay there. Exports still on their way stop as failed with connection_deleted.

From the dashboardCopy Anchor Link

Everything above is in the dashboard too, under Sending tools, once sequencers are on for your account.

• Connect a tool asks for what that tool needs and checks it with the tool before saving. A key or password it refuses is said under its field. Editing a connection keeps a saved key or password unless you type a new one.
• Export to tool is on the mailbox list (by mailbox), a domain's page (every set-up mailbox on it) and the domain list. Choose up to five connections and it shows what will happen first, for example "12 mailboxes × 2 tools = 24 exports". A mailbox that can't go yet is listed with why, not dropped.
• The Exports tab lists every export with its status. Filter it to failed ones, read what to fix, and retry or remove them together.
• On Mailboxes, switch to the list by mailbox to see which tools each one is in, or filter to the ones not exported yet.

From an AI agentCopy Anchor Link

The MCP server can list your connections, export mailboxes, follow the exports and retry or remove them, with a Read and manage key. It can't connect an account: the key and password would end up in the chat, so connect it in the dashboard or over the API first. Then ask, for example:

Export every mailbox on northwind-mail.com to Acme Instantly, then tell me which ones failed and what I need to fix.

The assistant calls export_mailboxes_to_sequencer, then list_sequencer_exports with status: failed, and reads each reasonMessage back to you.

SandboxCopy Anchor Link

In the sandbox nothing reaches any tool, and exports finish within seconds. A key starting with invalid is refused with api_key_invalid. A connection whose key starts with full takes exports that fail with no_mailbox_slots, and go through once retried.

Permissions and webhooksCopy Anchor Link

Reading needs sequencer.read, and connecting, exporting, retrying and removing need sequencer.manage (a manage API key or above). See team and roles.

The sequencer_connection.* and sequencer_export.* events are listed in the webhooks guide's Events table, with an example payload. None carries a key or a password.