Gravity Forms
+ Missive Premium

Turn every form submission into a conversation your whole team can see. The Gravity Forms Missive Premium Add-on takes each submission and, through the Missive REST API, opens a conversation in a shared inbox or team: a subject, a message and a desktop and mobile notification, all built from your form fields. It can instead create a ready-to-review email draft, so a reply is already waiting in Missive.

It is built for teams that live in a shared inbox: a new sales enquiry, a support request, a booking, an order, or any form your team needs to pick up and reply to together. Map the subject and the message from the fields, add a notification title and body, colour the conversation, choose plain text or Markdown, and route it to your Inbox or to a specific team. For replies, switch the feed to draft mode and set the from and to addresses so an email draft is created and left for a person to send.

You connect it with your own Missive API token, created in your Missive Preferences. The token is encrypted before it is stored on your site, it is never shown again and never written to an entry or a log, and the add-on only ever contacts the Missive REST API. A Test connection button on the settings page confirms your token works without creating anything, and each entry keeps the Missive conversation id for your records. A resend is safe: a conversation or draft is created once per entry and a retry never creates it again. Note that creating an API token requires a Missive plan whose API access is available on your account.

When a form is submitted and the feed condition is met, the add-on builds the request from the feed: for a conversation, the subject, the message (plain text or Markdown) and the notification title and body with your form fields merged in, plus any colour, team and routing; for a draft, the subject, body, from address and recipients. It then sends one request to the Missive REST API with your API token in the Authorization header. The host is fixed to public.missiveapp.com, a redirect is never followed, and the token never travels in the URL or the body. The Missive conversation id is saved on the entry, a clear note records what happened, and something is created once per entry so a retry never creates it again.