Moves one prospect to the front of the workspace's sending order for their next unsent email. Sender Pools never sends on demand: every sending rule still applies (the prospect's business hours and weekends, the gap between sequence steps, each mailbox's daily and per-provider limits, the spacing between a mailbox's sends, tenant limits, sending credits, email validation, do-not-contact). The queue only decides who gets the next free slot. Queued prospects go out first-in first-out, spread across the fleet at its normal rate, so queueing many prospects is safe. Typical latency is the next 10-minute pass that has a free slot during the prospect's business hours.
Identify the prospect by icpContactId (from list_icp_prospects) or by icpId plus email. Optional subjectText / bodyText replace the copy of that one next email, whatever the step's type (AI, template or per-contact), written in the same shorthand as per-contact copy. Without copy the email the sequence already wrote is sent as-is; if it has not been written yet it is moved to the front of the writing queue too.
Calling again for the same prospect keeps their position and replaces the copy. The entry clears itself once that email is sent. warnings lists anything that will hold the send until it changes (unverified address, ICP paused, no sending credits, email not written yet). The workspace must be a concrete id; all is not accepted here.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
400Neither icpContactId nor icpId + email was sent, the copy is unusable (a first email needs a subject and a body), the prospect has unsubscribed, is on the do-not-contact list or is paused, or the workspace is all.
404No such prospect in your account
409The prospect cannot be queued right now: every email in the sequence was already sent, a previous email failed or bounced, the next email is already on its way, or it is being written at this moment (retry in a minute).