Resources · Make integration

Twist Make integrationAutomate Twist with Make.

Can Make react to Twist the moment a thread or message lands? Yes. The Twist Make integration gives you 12 modules, including 6 instant triggers. This guide connects your account, builds a first scenario with you and explains each module in plain words.

Try the Twist integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Twist Make integration do?

The Twist Make integration links your Twist workspace to Make, a no-code tool where you build a scenario (the automation itself, a chain of modules). Twist alerts Make when something happens to a channel, a thread, a comment, a message, a group or a team, and Make can post, upload or list content back in Twist.

Turn a direct message into a tracked thread. A client request often arrives in a private conversation and gets buried. With Watch Messages as the starting point and Create a Thread as the next module, the request becomes a thread in a support channel where the whole team can see it and answer.

Keep a channel in sync with another tool. Watch Threads hands every new discussion to Make, so you can copy its title into a project board or a spreadsheet. The reverse also works: a form answer or a CRM update can open a thread with Create a Thread, or add a reply with Create a Comment.

Share files and review a channel. Upload an Attachment sends a file into Twist, and List All Threads returns every thread in a channel so a scenario can go through them one by one, for example to build a digest.

What the app does not cover out of the box, Make an API Call can reach with the same connection. The same app also exists in n8n: see the Twist n8n integration and the n8n vs Make comparison. Before you pick a plan, read Make pricing.

Connect

How do you connect Twist to Make?

  1. 01

    Register an app in Twist

    Twist asks for your own OAuth credentials. In your Twist account, open the App Console or Developer section, click Create Application, give it a name and enter the callback URI https://www.integromat.com/oauth/cb/twist. Copy the Client ID and the Client secret.

  2. 02

    Add a Twist module

    In your Make scenario, add any Twist module and click Create a connection. A connection is your Twist account linked to Make once, then reused by every Twist module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the credentials

    Enter the Client ID and Client secret you copied, or follow the instructions on screen, then approve access. The connection now appears in the list, and Make can read your channels and threads when you fill the next fields.

First scenario

Build your first scenario with Twist

GoalWhen a message arrives in a Twist conversation, Make opens a thread in a channel so the team can follow it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module. Search for Twist and pick Watch Messages.

  2. 02

    Set up the webhook

    Click Create a webhook, then Create a connection with the credentials from your Twist app. Twist will now call Make each time a message event happens.

  3. 03

    Add the thread action

    Click the + on the right of the trigger and add Create a Thread. Pick the channel from the list Make loads, then map the message text into the thread content.

  4. 04

    Test with Run once

    Click Run once, then send a test message in Twist. Each module shows the bundle it received, meaning the item passed along, so you can check that the right text reached the thread.

  5. 05

    Switch it on

    Save, then turn the scenario on. Because the trigger is instant, it runs as soon as Twist calls Make, not on a timer. Each module run counts as one operation on your Make plan.

Triggers

Twist triggers in Make

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

Twist1Watch Channels

Watch Channels

Instant trigger

In Make“Triggers when channel related event occurs.”

Starts your scenario whenever Twist reports an event about a channel, so the rest of your stack hears about workspace structure changes without anyone copying them by hand.

How it fires
instant, Twist calls Make through a webhook as soon as it happens.
When to use it
pick it when a channel change should be logged, announced elsewhere or mirrored in a project tool that lists your team spaces.
Watch out
Twist's documentation does not say which channel events it covers, so run a test and read the bundle before you map anything.
Twist2Watch Comments

Watch Comments

Instant trigger

In Make“Triggers when comment related event occurs.”

Hands each comment event to Make, which means replies inside a Twist thread can feed a helpdesk, a CRM note or a follow-up list the moment they appear.

How it fires
instant, Twist alerts Make by webhook right when the event occurs.
When to use it
choose it over Watch Threads when the reply matters more than the opening post, for example on a support thread where the client answers.
Watch out
if the same scenario also posts with Create a Comment, it can wake itself up again, so add a filter before that action.
Twist3Watch Groups

Watch Groups

Instant trigger

In Make“Triggers when group related event occurs.”

Gives you a starting point each time Twist signals something about a group, which helps you keep access lists and directories aligned with who is in which group.

How it fires
instant, Twist sends the event to Make via webhook the moment it takes place.
When to use it
use it when group membership drives something outside Twist, like a shared drive folder or an onboarding checklist in another app.
Watch out
the documentation lists no detail of the group events, so read the first bundle in the editor before building filters on it.
Twist4Watch Messages

Watch Messages

Instant trigger

In Make“Triggers when message related event occurs.”

Catches message events from Twist conversations, so requests people send you there do not stay hidden from the rest of your tools.

How it fires
instant, the app reaches Make through a webhook as soon as the message event happens.
When to use it
it is the right pick when people message you directly with requests that should end up in a tracked place, such as a channel thread.
Watch out
conversations can be personal, so only forward what the team actually needs and map fields with care.
Twist5Watch Teams

Watch Teams

Instant trigger

In Make“Triggers when team related event occurs.”

Lets Make know about events at the team level of Twist, useful when the whole workspace setup matters to another system such as an internal directory.

How it fires
instant, Twist pings Make by webhook immediately after the event.
When to use it
reach for it when team events should trigger admin work, like updating a staff list or notifying whoever manages tool access.
Watch out
do not mix it up with Watch Groups: this one follows the whole team, not one group inside it.
Twist6Watch Threads

Watch Threads

Instant trigger

In Make“Triggers when thread related event occurs.”

Sends every thread event to Make, so new discussions in your channels can land in a board, a sheet or a digest without anyone pasting links around.

How it fires
instant, Twist calls Make over a webhook as soon as the thread event happens.
When to use it
take it when the opening post is the signal, for instance a new request thread in a support or ideas channel.
Watch out
a scenario that watches threads and also runs Create a Thread in the same channel can loop, so point the action at another channel or filter it.
Modules

Twist actions and searches in Make

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

Twist1

Create a Comment

Action

In Make“Posts a new comment to a specific thread.”

Adds a reply to a Twist thread you choose, so an update from another tool shows up right where the discussion already happens instead of in a new place.

When to use it
when a ticket closes or a deal moves in your CRM, post the news under the matching thread.
Watch out
you need the target thread first, so place List All Threads or a trigger before it to supply that thread.
Twist2

Create a Message

Action

In Make“Posts a new message to a specific conversation.”

Posts a message into a Twist conversation rather than a channel, which is handy for a heads-up meant for one person or a small group.

When to use it
choose it over Create a Thread when the note is personal, like an alert to the owner of a record.
Watch out
the message goes to a specific conversation, so check which one is selected before you switch the scenario on.
Twist3

Create a Thread

Action

In Make“Creates a new thread in a specific channel.”

Opens a new thread in a channel, giving a topic its own titled space that the team can follow, answer and later search in Twist.

When to use it
for every new form request, lead or incident that deserves its own discussion rather than a line in an existing one.
Watch out
paired with Watch Threads on the same channel, it can trigger itself again and again; a filter stops that.
Twist4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the Twist API with the connection you already set up, which covers whatever the ready-made Twist modules leave out.

When to use it
when you need a Twist feature that has no dedicated module in the list above.
Watch out
you write the request yourself, so keep the Twist API documentation open and test with Run once before switching on.
Twist5

Upload an Attachment

Action

In Make“Uploads a file.”

Sends a file into Twist, so a document produced or received elsewhere can join the discussion without anyone downloading and uploading it again.

When to use it
after a report, a signed contract or an invoice is generated in another app and the team needs it in Twist.
Watch out
on the Free plan, Make handles files up to 5 MB, so large files call for a paid plan.
Twist6

List All Threads

Search

In Make“Lists all threads in a channel.”

Returns every thread of a channel as separate bundles, which gives you a full picture of a channel to review, copy or summarize in one run.

When to use it
to build a digest, archive a channel in a spreadsheet or find the thread a later module should reply to.
Watch out
each returned thread runs the next modules once, and each run counts as an operation on your plan.
Need help

Need help automating Twist with Make?

A person reads every message.

FAQ

Twist Make integration FAQ

01Is the Twist Make integration free?
Yes, Twist is a standard app, available from the Free plan of Make. That plan gives you 2 active scenarios, a minimum of 15 minutes between two scheduled runs, up to 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, allow unlimited active scenarios and 40 minutes of execution. Usage is counted in operations per month. You still need a Twist account, whose subscription is set on the Twist side.
02What is needed to connect Twist to Make?
A Twist account and a registered developer app to get OAuth credentials. In the App Console or Developer section of Twist, create an application, give it a name, enter the callback URI given by the Make documentation, then copy the Client ID and Client secret. In Make, add a Twist module, click Create a connection, optionally name it, and paste those credentials or follow the on-screen steps. For an instant module, click Create a webhook first, then Create a connection.
03Do Twist triggers in Make work in real time?
Yes. All 6 Twist triggers are instant: Twist calls Make through a webhook as soon as an event happens on a channel, comment, group, message, team or thread. The scenario starts right away instead of waiting for the schedule, which by default checks every 15 minutes. You recognize these modules by the lightning badge in the editor. Remember that each module run on each bundle still counts as one operation on your plan.
04What if a Twist module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Twist API with the same connection, so you can cover what the 5 actions and the search do not offer. You write the request yourself, which asks for a look at the Twist API documentation. Test it with Run once before activating. Also note that the Make documentation for Twist is AI-generated from the official Twist docs and may contain mistakes, so verify important details with Twist.
05Should Twist be automated with Make or n8n?
It depends on the tool your team already uses. Twist exists in both. In Make, you get 12 modules, including 6 instant triggers and a Make an API Call module for anything else, all set up in a visual editor where you test with Run once. On n8n, the same app has its own node, which has its own page in this resource section. The simplest criterion is where your other automations live, because one tool to maintain is easier than two.
Same platform

Other docs you might need on this stack.

Browse all integrations