Reply in a conversation
Sends a reply in a conversation. This sends real email to real people, and it cannot be undone. Once the email service accepts a message it is on its way, and nothing can recall it. There is no test mode.
Who it goes to is read off the conversation, never from the request: the sender of the latest message when it came in, or everybody the latest message went to when it was yours. cc_person_ids adds people on file as copies.
What stops it, before anything is sent:
- A merge field such as
{{first_name}}is left anywhere in the subject or body (400). - Any address it goes to or copies is suppressed (409).
- A person copied has opted out of email altogether, or out of the category general (409). The people the reply goes to are not checked against preferences.
- Your organization cannot send email yet (409), or the conversation has no message or no address to reply to (409).
If the email service refuses the reply, the answer is 502: the reply is kept in the conversation, marked as not sent, and the reason is in reason.
A key sees the inboxes that the person who made the key may read, as that person’s access stands at the moment of the request; a conversation in any other inbox answers 404, the same as one that does not exist. Needs write on Communications.
Authorizations
Body
Send the body as body_blocks or as body.

