Skip to main content
POST
This reaches the requester over the task’s origin channel. For a connected personal mailbox the reply is staged as a draft for the mailbox owner to review and send, rather than sent immediately. The delivery_status on the returned message says which happened — sent or draft — so do not report a reply as delivered without reading it. For an internal note that the requester never sees, add a comment instead.
The requester thread is behind its own feature flag, separate from tasks. This endpoint returns 404 unless it is enabled for your organization.
A task that did not arrive over Slack, email or Teams has no requester to reply to. This endpoint returns 400 for such a task, and any job_id in attachments stays usable.

Partly delivered replies

A reply can reach the requester even though Wordsmith could not confirm that everything completed, for example an attachment that could not be delivered. The response is then a 400 with error_code task_thread_reply_partially_delivered:
Do not retry this request. The requester already has the reply, and sending it again delivers it twice. The thread may not show the reply, because recording it is one of the steps that can fail. Check the conversation in the origin channel (Slack, Teams or email) before you send a follow-up. Any other 400 means nothing was sent, so you can fix the request and retry.

Body parameters

string
required
The reply body, sent to the requester.
array
Ids of files already in Wordsmith to attach. A job_id does not go here; use attachments.
array
Up to 10 new files to attach, each with exactly one of upload_job_id (the job_id from the file upload endpoint, once the file is uploaded) or url (a public http(s) URL). See Attach Files for the limits.