---
title: Support email, in and out
description: Point your own email provider's inbound webhook at Venom Support and connect your own SMTP server or Postmark, SendGrid, Mailgun or Resend key for replies. Venom sends nothing through any account of its own.
section: cloud
order: 191
audience: [user, operator, builder]
sources: [services/nodejs-cloud/lib/support/inbound.ts, services/nodejs-cloud/lib/support/mail.ts, services/nodejs-cloud/lib/support/reply.ts, services/nodejs-cloud/components/support/Settings.tsx, docs/adr/0058-venom-support.md]
features: [cloud.page-support]
---

[Venom Support](/docs/cloud/support.md) never reads a mailbox and never sends from an address it owns. Mail comes **in** because
your provider calls Venom, and goes **out** only through a provider you set up. Both live in **Settings** at
`/support/settings` (owners and admins).

## Mail in

Create the **inbound secret** in Settings; it is shown once (only its hash is kept), together with your org's address:

```text
https://<your cloud>/api/integrations/support-inbound/<org id>
```

Give your provider the address, with the secret as `?secret=…`, as the `x-venom-support-secret` header, or as the password
of HTTP Basic auth (user name anything):

| Provider | Setup |
|---|---|
| Postmark | Inbound webhook URL `https://x:SECRET@<host>/api/integrations/support-inbound/<org>` |
| SendGrid | Inbound Parse destination URL with `?secret=SECRET` |
| Mailgun | A route that forwards to the URL with `?secret=SECRET` |
| Anything else | `POST` the message as JSON (`from`, `subject`, `text`, optional `to`, `cc`, `messageId`, `inReplyTo`) |

The endpoint takes Postmark's inbound JSON, SendGrid's Inbound Parse fields, Mailgun's route fields and the plain shape
above, as JSON or form fields, up to 2 MiB, at most 300 a minute per org. Quoted history ("On Monday, Ana wrote:") is
cut from the message. A wrong secret, a wrong org id and a missing secret all answer `401`, and nothing is read before
the secret is checked.

A message joins the conversation it answers (by `In-Reply-To` and `References`, else by the `[#42]` Support puts in
subjects) and reopens it; otherwise it opens a new one. Sending the same `Message-ID` twice changes nothing. A new
secret stops the old one at once.

## Mail out

Choose the provider, give the sender name and address, and paste its key. The key is sealed in the vault (a deployment
needs `VENOM_VAULT_KEYS`), never shown again, and only its last four characters are kept as a hint. Leave the key blank to
keep the saved one when you change other settings.

| Provider | Needs |
|---|---|
| Postmark | Server token; the sender address must be a verified signature or domain |
| SendGrid | API key with Mail Send |
| Mailgun | API key, the sending domain, US or EU region |
| Resend | API key |
| SMTP | Host, port (`465` implicit TLS, `587` STARTTLS), username, password |

Calls go to the provider's own host. For SMTP, the host is resolved and refused if it is a private address (in
production), and the password is never sent unless the connection is encrypted. A reply carries `Re: subject [#42]`,
`In-Reply-To` and `References`, and copies the people on the thread.

If no provider is connected, the customer has no address, or the provider refuses (a wrong key, an unverified sender),
the reply is **saved on the thread marked "not sent"** with the provider's reason. Fix the setting and send again.

## Saved replies

Settings also holds the saved replies. A name is unique in the org. Variables: `{{customer.name}}`,
`{{customer.first_name}}`, `{{agent.name}}`, `{{conversation.subject}}`, `{{conversation.number}}`; others stay as written.
