A form submission becomes a conversation
- 1
Your server posts the submission
Save the form in your own database first, then send it to Intray with an idempotency key built from the record's ID.
- 2
The conversation appears in Todo
It shows the customer, the message, and the fields you sent, such as company and team size. Creating the conversation sends no email.
- 3
Your team replies by email
Someone replies from the inbox, and from then on the conversation is a normal email thread.
Replies to your app's email reach your team
Your app can send email through Intray from a shared address, for example a welcome message after signup. Those conversations start in Done, so they stay out of Todo. When the customer replies, the thread moves to Todo with your app's email above the reply.
Your app can read, reply, and triage
Keys, retries, and opt-outs in the API
Each key is limited to the addresses and permissions you pick. Writes need an idempotency key, and email sent through the API ends with an opt-out link.
A key for each integration
A key works only for the addresses and permissions you choose. You can rotate or revoke it at any time.
A retry does not create a duplicate
Every write needs an idempotency key. The same request sent twice has the effect of sending it once.
Recipients can opt out
Every email the API sends ends with an opt-out link. Intray stops sending to a recipient who uses it.