Conversation properties for email
This article is the Email channel on a Conversation property. Shared settings — Sending messages, Message writing instructions, attachments, Disable replies, and the rest — live there. This page is what is different when the channel is Email: a distinct email thread per work item, forms in the message, the sender name, and how to put a form in the outgoing email.
To start new work items from emails sent to the thunk's own address, see Send requests to your thunk by email instead.
Email channel configuration
Each Conversation property configured with the Email channel tracks the conversation as a distinct email thread per work item.
Set Channel to Email, then the Email-only fields:
Form responses: When enabled, the AI agent can send structured forms embedded in outgoing emails to collect structured replies. This is useful when the response requires the external party to select from defined options rather than compose a free-form reply.
One-time form submissions: When enabled, each form can be answered only once. When off, the person can submit the same form again.
From Display Name: the sender name that external recipients see. If left blank, messages appear from the account's default display name. A team or role name (for example "HR Support Team", "Compliance Review") is appropriate in most cases, since messages are sent on behalf of a workflow rather than an individual.
Message Signature: text appended to every outgoing message sent through this property.
The shared settings on Conversation properties still apply on Email, including AI file attachments, User file attachments, AI messaging, Sending messages, Message writing instructions, Disable replies, and Send structured data. Reply when work item is closed and Closed work item reply do not apply to email replies.
Instructing the AI agent
The three-part pattern for a conversational step — initiating action, processing incoming messages, concluding condition — is in Conversation properties (Instructing the AI agent). Use that pattern on Email the same way, and list the conversation under the step's Output properties.
Sending a form
When Form responses is enabled, the step instructions can direct the AI agent to include a structured form in the outgoing email. The form is defined as a JSON schema directly in the step instructions:
{"type":"object","properties":{"Status":{"type":"string","enum":["Completed","Pending","Not Started","Cancelled"]}}}
Replace the property name and enum values with the options relevant to the workflow. The three-part step structure applies in the same way:
Initiating action: instruct the AI agent to send the email with the form attached, using the JSON schema above.
Processing incoming messages: specify how to map the submitted form values to workflow state properties. For example: "When the user submits the form, map the selected status directly to the
ActionItemStatusproperty."Concluding condition: base the condition on the form response received. For example: "Only finish this step if
ActionItemStatusbecomesCompletedorCancelled." This keeps the step open if the recipient submits a value that requires further action.
One-way emails
For one-way notifications where no response is expected or acted upon, enable Disable replies on the Conversation property. This allows the AI agent to send through the property while ignoring any incoming replies. See Conversation properties (Common settings).
Examples in the sample library
The following samples use Conversation properties to manage email threads within their workflows.
Process Support Tickets: conducts a clarification conversation with the customer before drafting a response, with a time-bounded wait before proceeding on available information.
Process Patient Support Program Applications: manages parallel threads with the prescribing provider and the patient, each in a separate Conversation property on the same work item.
Unblock Payment Transactions via Partner Review: runs three independent conversation loops per transaction: one with the partner to confirm review requirements, one with the sender, and one with the recipient for document collection.
Manage Application Intake Process: emails candidates to request a missing resume and holds the extraction step open until a response is received.
Automating Expense Receipt Submission: contacts the submitter when a receipt fails the initial integrity check, waiting for a response before continuing.

