Resources · Make integration

Missive Make integrationAutomate Missive with Make.

Your shared inbox can feed the rest of your stack on its own. The Missive Make integration gives you 10 modules: 3 triggers, 6 actions and 1 search. This guide walks you through the connection, a first scenario and when to pick each module.

Try the Missive integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Missive Make integration do for your team?

The Missive Make integration links your Missive organization to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that runs on a schedule or when an app calls Make. Each module is one brick, such as a trigger that starts the run or an action that writes back into Missive.

Keep your contact book in sync. Watch Contacts picks up contacts created or updated in Missive, so a CRM or a spreadsheet on the other side always gets the latest version. Going the other way, Create a Contact and Update a Contact write changes coming from a signup form straight into Missive.

Push context into a conversation. Create a Post drops data into any Missive conversation. A support lead can see an order status or a form answer right where the team is already talking, without opening another tab.

Prepare replies before anyone types. Watch New Message reacts the moment a message arrives, and Create a Draft sets up an email or SMS draft that a teammate edits and sends from Missive, or that goes out immediately if you prefer.

Two limits to know. Using Missive in Make requires an organization on the Missive Productive plan, and the Make documentation page for Missive states it was generated with AI from the vendor docs, so double-check anything critical with Missive. If you also weigh n8n, read n8n vs Make. New to scenarios? Make training covers the basics, and Make troubleshooting helps when a run fails.

Connect

How do you connect Missive to Make?

  1. 01

    Create an API token in Missive

    In Missive, open Preferences, go to the API tab and click Create a new token. Copy the token shown on screen. This only works if your organization is on the Missive Productive plan.

  2. 02

    Add a Missive module and open the connection

    In your Make scenario, add any Missive module and click Create a connection. A connection is your Missive account linked to Make once, then reused by every Missive module. You can fill Connection name so you recognize it later.

  3. 03

    Paste the token and save

    Paste the token you copied from Missive into the credentials field, or follow the on-screen instructions, and confirm. Make now lists what it can read in your Missive account, which is the sign the link works.

First scenario

Your first scenario: a draft ready for every new message

GoalWhen a new message arrives in Missive, Make prepares a draft your team can review and send from Missive.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module. Everything you build next hangs off that starting point.

  2. 02

    Add Watch New Message

    Search for Missive, pick Watch New Message, click Create a webhook, then Create a connection with your API token. From now on, Missive tells Make each time a message comes in.

  3. 03

    Add Create a Draft

    Click the + on the right of the trigger and choose Create a Draft. Map data from the message bundle, meaning the single item the trigger passed along, into the draft so the reply starts with the right context.

  4. 04

    Test with Run once

    Click Run once, then send a test message to your Missive inbox. Open the bubbles above each module to read the bundles they received and check the draft shows up in Missive.

  5. 05

    Switch it on

    Turn the scenario on. Because the trigger is instant, it runs as messages arrive instead of waiting for the default 15 minutes schedule. Each module run counts as one operation on your Make plan.

Triggers

What can start a Missive scenario?

3 modules start a scenario when something happens in Missive. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Missive as soon as it happens.

Missive1Watch Contacts

Watch Contacts

Scheduled trigger

In Make“Triggers when a new contact is created or updated.”

Hands your scenario every Missive contact that was just created or edited, so the systems around your inbox stop drifting apart.

How it fires
scheduled. Make checks Missive on the scenario's schedule, every 15 minutes by default, and never faster than that on the Free plan.
When to use it
your team corrects a contact's details in Missive, and you want your CRM or a Google Sheet to follow without retyping.
Watch out
edits count as well as new contacts, so a scenario that itself updates Missive contacts can pick up its own changes at the next check; keep that write in a separate scenario.
Missive2Watch New Comment

Watch New Comment

Instant trigger

In Make“Triggers when a new comment is added.”

Lets you react to the internal side of Missive: whenever a teammate leaves a comment, your scenario starts with that comment in hand. Handy for turning quick chat notes into tasks or alerts elsewhere.

How it fires
instant. Missive calls Make through a webhook as soon as the comment is added, with no schedule to wait for.
When to use it
a manager wants every comment on escalated conversations copied into a project tool so nothing discussed in the inbox gets lost.
Watch out
when you add it, click Create a webhook before Create a connection, otherwise Make has no address for Missive to call.
Missive3Watch New Message

Watch New Message

Instant trigger

In Make“Triggers when a new message is received.”

Starts your scenario the moment a message lands in Missive, which makes it the natural entry point for anything customer facing: routing, logging, or preparing an answer before a human opens the thread.

How it fires
instant. Missive notifies Make through a webhook right after the message is received.
When to use it
a sales team wants every inbound request logged in a spreadsheet, or a draft reply waiting, before anyone picks up the conversation.
Watch out
if the same scenario sends a message back through Missive, make sure it cannot trigger itself again; test the chain with Run once before switching it on.
Modules

Every Missive module, and when to pick it

Missive gives you 7 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Missive1

Create a Contact

Action

In Make“Creates a new contact.”

Adds a brand new person to your Missive contacts, so the team sees a known name instead of a bare address the next time that person writes.

When to use it
a lead fills in a web form or books a call in another tool, and you want the contact ready in Missive before the first email.
Watch out
it always creates; run Search Contacts first if the person might already exist, or you will end up with duplicates.
Missive2

Create a Draft

Action

In Make“Creates an email or SMS draft that can either be sent immediately or edited and sent from the Missive app.”

Prepares an email or an SMS inside Missive. You decide whether it leaves right away or sits as a draft that a teammate polishes and sends from the Missive app.

When to use it
a quote request comes in and you want a prefilled answer waiting, while a human still checks the tone before sending.
Watch out
sending immediately skips that human check, so keep the draft mode while you are still testing the scenario.
Missive3

Create a Post

Action

In Make“Injects data in any Missive conversation.”

Drops information from another app directly into a Missive conversation, so the people handling it get context without leaving the thread. Think payment status, form answers or a ticket number.

When to use it
a customer writes about an order and you want the order details from your shop posted in the same conversation for the agent.
Watch out
the post lands in the conversation you target, so map the right conversation from the trigger bundle rather than typing a fixed one.
Missive4

Get a Contact

Action

In Make“Fetches a specific contact using the contact ID.”

Retrieves one specific Missive contact when you already hold its contact ID, giving the next modules the full record to work with instead of a bare identifier.

When to use it
Watch Contacts or another module passed along an ID, and you need the complete contact before updating a CRM.
Watch out
it needs the exact ID; if all you have is a name or an email address, Search Contacts is the module to reach for.
Missive5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the Missive API from inside your scenario, reusing the same connection, so you can call any endpoint the listed modules do not cover.

When to use it
you need a Missive feature that has no dedicated module here, and you are comfortable reading the Missive API documentation to build the request.
Watch out
you build the request by hand. Check it against the Missive docs and run it once before going live.
Missive6

Update a Contact

Action

In Make“Updates an existing contact.”

Edits a contact that already exists in Missive, so the details your team relies on stay in line with your CRM or your billing tool.

When to use it
a customer's details change in your CRM, and the Missive record should follow without someone copying it by hand.
Watch out
it works on an existing contact; pair it with Search Contacts or Get a Contact to point at the right person first.
Missive7

Search Contacts

Search

In Make“Searches for contacts or lists them all.”

Looks through your Missive contacts, or lists them all, and returns every match as a separate bundle that later modules process one by one.

When to use it
before creating a contact, to check whether that person is already in Missive, or to export the whole list to a spreadsheet.
Watch out
it can return zero, one or many results, and each result costs operations in the modules that follow, so keep the search as precise as your case allows.
Need help

Need help automating Missive with Make?

A person reads every message.

FAQ

Missive and Make: common questions

01Is the Missive Make integration free?
Yes on the Make side: Missive is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute and count usage in credits, meaning operations, per month. On the Missive side, the app requires an organization on the Productive plan, which is a Missive subscription and not a Make one.
02What do you need to connect Missive to Make?
Two things: a Make account and an API token from a Missive organization subscribed to the Productive plan. In Missive, open Preferences, then the API tab, click Create a new token and copy it. In Make, add a Missive module, click Create a connection, optionally name it, and paste the token. For Watch New Comment or Watch New Message, click Create a webhook before Create a connection. The same connection then serves all 10 Missive modules.
03Do Missive triggers fire instantly in Make?
Two of them do. Watch New Comment and Watch New Message are instant: Missive calls Make through a webhook as soon as a comment is added or a message is received. Watch Contacts is scheduled: Make checks Missive on the scenario's schedule, every 15 minutes by default, down to 1 minute on paid plans. So pick an instant trigger when a reply or an alert should follow a message quickly, and Watch Contacts when a periodic sync of your contact list is enough.
04What if the Missive module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Missive API with the connection you already set up, which covers what the 9 other modules do not. You build the request from the Missive API documentation and test it with Run once. Also keep in mind that the Make documentation for Missive says it was generated with AI from vendor docs and may contain mistakes, so confirm important details with Missive before relying on them in a live scenario.
05Should you use Make or n8n for Missive?
It depends on where your team already builds automations. Make gives Missive 10 ready modules, including 2 instant triggers, and a visual editor where you test each step with Run once, which suits a team starting from the inbox. Many apps also exist as n8n nodes, so if your other workflows already live in n8n, check what it offers for Missive before splitting your tools. The comparison page linked above lays out the criteria side by side without picking a winner for you.
Same platform

Other docs you might need on this stack.

Browse all integrations