Fill a rep’s dial list from their call tasks
Rebuilds a rep’s Sequencer dial list from their open call tasks: it places each pending call task that has no dial-list row, oldest due first, and removes rows whose task is no longer pending.
This is what Start dialing runs in the task inbox. The work happens in the background, so the response describes what will happen, not what has landed: wait until the list holds expected rows before you open it. One pass places at most 200 tasks. Contacts with no dialable number (none, or only do-not-call or wrong numbers) are not placed.
Call tasks normally reach the list on their own when their step comes due; this repairs a list that missed some, or that a rep cleared by hand. Safe to repeat. user_id is the acting member and assignee_id (default user_id) names whose list to rebuild. Counts against the Sequencer writes rate limit.
Waiting for the result
The work runs in the background, and the response says what to expect:expected rows before sending the rep to the dialer; a rep who opens it at once may see it as it was. contact_list is null the first time a rep has call tasks, and the job creates the list.
Good to know
- One pass places at most 200 tasks, oldest due first. Call it again for the rest.
- A contact with no dialable number (none, or only do-not-call or wrong numbers) is not placed. Its task stays in the queue to work by hand or skip.
- It also removes rows whose task is no longer pending, so it is safe to run whenever the list looks stale.
Authorizations
Team-scoped API key generated in the Salesfinity dashboard under Settings → Connections → API & Webhooks. A missing or invalid key returns HTTP 403.
Headers
Makes this write safe to retry. Send a unique value, such as a UUID, and send the same value again when you retry the same request. A retry with the same key and the same request (method, path including the query string, and JSON body) returns the original successful response without acting twice. The same key with a different body or path returns 409, and so does a retry while the first request is still running; that one is safe to repeat after a moment. A request that fails frees its key, so a retry runs the write again: after a 5xx on a create, confirm with a GET before retrying. Keys are kept for 24 hours and are scoped to your team.
Body
Response
What the background job will do.
Pending call tasks for this rep that have no dial-list row.
How many of those this pass places: at most 200.
Id of the rep's Sequencer dial list, or null when the rep has none yet (the job creates it).
Rows the list will hold once the job has run: the rep's pending call tasks, up to 200, whose contact has a dialable number.