Reamaze Make integrationAutomate Reamaze with Make.
What if every new Reamaze conversation reached the right tool on its own? The Reamaze Make integration gives you 14 modules: 3 triggers, 8 actions and 3 searches. This guide is for support leads who run Reamaze, and it walks you from the connection to a working scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Reamaze Make integration automate?
The Reamaze Make integration links your Reamaze help desk to the other apps you use, without code. Make watches Reamaze for new contacts, conversations and messages, then passes each one to the next step of a scenario: the automation you build in Make, one brick at a time.
A shared view of every new ticket. Watch New Conversations picks up each conversation opened in Reamaze and hands it to a spreadsheet, a chat tool or a CRM, so the people outside the help desk see what customers ask about.
Contacts that stay the same everywhere. When a customer signs up in your shop or your CRM, Create a Contact adds them to Reamaze, and Update a Contact keeps their details in step when something changes on the other side.
Conversations started from other tools. A form, an order problem or an alert elsewhere can open a thread in Reamaze with Create a Conversation, then Create a Message adds the reply your agents would otherwise type by hand.
All three triggers are scheduled: Make checks Reamaze on the scenario's clock, so nothing here fires the moment a customer writes. When a listed module does not cover what you need, Make an API Call reaches the rest of the Reamaze API with the same connection. The Make review explains the editor in depth, and the n8n vs Make page helps if you are still choosing a platform. When a run fails, Make troubleshooting covers the usual causes.
How do you connect Reamaze to Make?
- 01
Generate an API token in Reamaze
Log in to Reamaze and open Settings. Under the Developer section, click API Token, then Generate New Token. Copy the token that appears on screen; Make needs it in a moment.
- 02
Add a Reamaze module in Make
In your scenario, add any Reamaze module and click Create a connection. The Connection name field is optional: a clear label helps when several brands or accounts live in the same Make organization.
- 03
Paste the credentials and save
Enter the credentials copied from your Reamaze account, or follow the instructions shown on screen, then save. This connection, your Reamaze account linked to Make once, is reused by every Reamaze module after that.
Build your first Reamaze scenario
GoalWhen a new contact appears in Reamaze, Make opens a welcome conversation for them.
- 01
Create the scenario
From the Scenarios page, create a new scenario and click the big +. Search for Reamaze and pick Watch New Contacts as the first module, the one that starts everything.
- 02
Link your account
Click Create a connection and paste your Reamaze API token. Once the connection exists, Make can read your Reamaze data and fill the choices in the module for you.
- 03
Add the conversation step
Click the + on the right of the trigger and add Create a Conversation. Map the contact coming from the first module into it, so each new person gets their own thread.
- 04
Test with Run once
Click Run once. Make runs the scenario one time and shows the bundles each module received; a bundle is one item passed along, here one contact. Check that the conversation looks right in Reamaze.
- 05
Schedule it and switch it on
Open the clock on the first module. A new scenario checks every 15 minutes by default; keep that or pick another interval your plan allows, then switch the scenario on.
Reamaze triggers in Make
3 modules start a scenario when something happens in Reamaze. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Reamaze as soon as it happens.
Watch New Contacts
Scheduled triggerIn Make“Triggers when a new contact is created.”
You get every new Reamaze contact as a bundle, ready to copy into a CRM, a mailing tool or a sheet. The trigger starts the scenario with the people who just entered your help desk, so your other tools learn about them without anyone exporting a list.
Watch New Conversations
Scheduled triggerIn Make“Triggers when a new conversation is created.”
This trigger gives you each conversation opened in Reamaze, which makes it the natural start for routing or reporting. It fits scenarios that care about the ticket as a whole: who opened it and what it is about, rather than every reply inside it.
Watch New Messages
Scheduled triggerIn Make“Triggers when a new message is created.”
With this trigger, each new message in Reamaze becomes a bundle, whether it opens a thread or continues one. It is the finer-grained option: the scenario sees the actual back and forth between customers and agents, not only the fact that a conversation exists.
Reamaze modules in Make
Reamaze gives you 11 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Create a Contact
ActionIn Make“Creates a contact.”
Create a Contact puts a new person into Reamaze from another app, so your agents recognize a customer before the first message arrives. The data comes from whatever module sits before it.
Create a Contact Identity
ActionIn Make“Creates a contact identity.”
This module adds an identity to a contact that already lives in Reamaze. It is the step for enriching an existing record rather than creating a second person, which keeps the customer's history under one profile.
Create a Conversation
ActionIn Make“Creates a conversation.”
Create a Conversation opens a fresh thread in Reamaze from an event elsewhere, so the case lands in the inbox your agents already work from. Nobody has to copy a request by hand from a form or an order system.
Create a Message
ActionIn Make“Creates a message.”
Here you add a message to a Reamaze conversation, which lets a scenario post an update into a thread instead of starting a new one. The customer's history stays in one place, and agents read the whole story in order.
Get a Conversation
ActionIn Make“Gets a conversation.”
Get a Conversation fetches one specific Reamaze conversation, which is handy when a scenario holds a reference and needs the full details behind it. You get a single bundle back, ready to map into the next step.
Make an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
Make an API Call is the way out when no listed module does what you need. It sends a request to any part of the Reamaze API, using the same connection as the other modules, so you do not set up a second login.
Update a Contact
ActionIn Make“Updates a contact.”
Update a Contact changes an existing Reamaze contact, which keeps your help desk in line with the tool where customer data really lives. Agents see the latest details without editing the profile by hand.
Update a Conversation
ActionIn Make“Updates a conversation.”
With Update a Conversation, a scenario edits a thread that is already open in Reamaze. It lets events in other tools move a case forward, so your inbox reflects what actually happened without an agent stepping in.
List Contacts
SearchIn Make“Gets all contacts.”
List Contacts pulls contacts out of Reamaze, one bundle per person, which is how a scenario checks who is already there before it creates or updates anyone. It can return zero, one or many results.
List Conversations
SearchIn Make“Gets all conversations.”
This search returns Reamaze conversations as separate bundles, which suits reporting or bulk follow-up done from Make. Each conversation then travels through the rest of the scenario on its own, like a row in a spreadsheet.
List Messages
SearchIn Make“Gets all messages.”
List Messages retrieves the messages stored in Reamaze, so a scenario can read what was actually said and not just that a thread exists. Every message comes back as its own bundle.
Need help automating Reamaze with Make?
A person reads every message.
