Add the data to the workspace (step 2 of 2)
Starts adding the pulled data to your workspace (the dashboard's "Start import"): status ready only. The field mapping is applied now: new attributes are created first.
Live emails with a dynamic audience would send to the people the import adds: then the call answers 409 confirmation_required with details.liveEmails (how many, and their names when you may manage outbound). Tell the user; send confirmLiveEmails: true only if they agree (or pause those emails first). The same for details.snoozeEffects and confirmSnoozeEffects. Never send a confirmation before a 409 asked for it.
Body
Send true only after the user agreed: live emails with a dynamic audience will send to the people the import adds. Asked only when such emails are live (409 with details.liveEmails).
trueResponse
Success
While the import waits for you (draft, ready, paused, needs_reconnect): when it is cancelled if nothing happens.
2026-11-02T12:00:00.000ZThe field mapping. Null for a draft (the fields are known after the pull).
The saved teammate, team and brand choices (see GET /v2/helpdesk_imports/{id}/teammates for what each one maps to).
Object type identifier
helpdesk_importhelpdesk_importpull: reads the source into a private staging area; nothing is added to your workspace. write: adds the data.
pull, writepulldraft: connected, not started. running: reading the source (phase: pull) or adding the data (phase: write). ready: everything was read; map the fields, then start. paused. needs_reconnect: the source refused the key. completed, cancelled, failed.
draft, running, paused, needs_reconnect, ready, completed, cancelled, failedreadyInvite them (in the dashboard) and their imported messages become their own when they join.
Why a running import waits (for example the source's rate limit), and until when. It continues by itself.