Start a conversation
Opens a new conversation in one of your inboxes and sends its first message. 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.
The message goes out from your organization’s sending address, and replies to it come back into this conversation. The people it is to and copied to, the animals, and the record named are linked to the conversation, confirmed, so it shows on their records.
What stops it, before anything is sent or any conversation is opened:
- A merge field such as
{{first_name}}is left anywhere in the subject or body (400). Fill templates first with Fill a template. - Any address it goes to or copies is suppressed (409). Nothing is sent to anybody.
- Any person named in
person_id,person_idsorcc_person_idshas opted out of email altogether, or out of the category general (409). Typed addresses are not checked against anybody’s preferences. - Your organization cannot send email yet, for example while its own sending domain waits to be verified (409).
If the email service refuses the message, the answer is 502: the conversation and the message are kept, 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
Name at least one recipient: a person or an address. Send the body as body_blocks or as body. Every person named must have an email address on file.
The kind of record a conversation can be about.
person, organization, animal, location_unit, donation, campaign, shift, volunteer_event, shift_signup, adoption_application, org_event, form_submission Send it with related_entity_type, or neither.

