Email API accepts attachments
The Email API now accepts the files that end users attach to a contact form. Your AI Agent handles them the same way as attachments on an email sent to it directly.
What’s new
The POST /v2/conversations/email/ endpoint accepts a new request format. JSON requests work as before.
- Multipart requests: send the request as
multipart/form-data, with the JSON body in adatapart and oneattachmentspart per file. See Start a conversation over Ada’s email channel. - Attachment handling applies: files follow the attachment handling setting of the inbox the AI Agent replies from. On inboxes set to AI Agent replies using the attachment, the AI Agent reads up to 3 images. On the default Hand off to a human, the inquiry is handed off with its files.
- Limits: a request can include up to 10 attachments and 30 MB in total. A request with more files returns
400 Bad Request, and a larger one returns413 Content Too Large.
SEND steps can search and reference Knowledge
Contextual AI-generated SEND steps in Playbooks can now use Knowledge for a single reply. A reference in General Guidelines applies across the whole Playbook. A search or a reference in a SEND step grounds the reply of that step.
What’s new
Two options appear under Knowledge in the @ menu of a Contextual AI-generated SEND step.
- Search Knowledge. Select Search Knowledge to add a Search pill. When the step runs, the AI Agent writes a search query from the instruction and the recent conversation. The Agent then searches Knowledge and writes the reply from the results. Name a topic in the instruction to narrow the search.
- Reference an article. Select an article to ground the step’s reply in its content. The menu shows the locale of each article and marks articles that have availability rules. A step can reference up to 5 articles.
Availability rules apply to both options. Fixed message SEND steps do not support them.