Resources · n8n integration

Twist n8n integrationAutomate Twist with n8n.

Every Twist thread a team opens by hand could be opened by a workflow instead. The Twist n8n integration ships as a built-in node with 22 operations across 4 resources: channels, threads, comments and conversation messages. No Twist trigger exists, so a schedule or another app starts the run.

Try the Twist integration on n8n See the 22 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Twist n8n integration actually do?

The Twist node ships with n8n and calls the Twist API on behalf of a workspace. It exposes 22 operations spread over 4 resources: Channel, Thread, Comment and Message Conversation. A workflow can open a channel, start a thread inside it, answer that thread with a comment, or write straight into a conversation, with nobody typing in Twist.

Scenario one, the recurring report. A Schedule Trigger fires on Monday morning, a Google Sheets node reads the numbers of the week, and thread.create opens a thread in the channel of the team concerned, with the title and the body built from the sheet. The discussion then happens under the figures instead of next to them.

Scenario two, the alert that has to reach a person rather than a room. A monitoring tool calls an n8n Webhook, which is a URL n8n exposes so an outside service can start a workflow, and messageConversation.create writes into the conversation of whoever is on duty, using the mention syntax [Name](twist-mention://user_id). The same run can post the public version as a channel thread, so the team reads what the on-call engineer reads.

Scenario three, the workspace clean-up. channel.getAll lists a workspace with Return All on, a Filter node keeps the channels whose names match finished projects, and channel.archive moves them out of the active list. Run it once a month and the sidebar stops growing on its own.

Twist has no trigger node in n8n, so every workflow above starts elsewhere: a Schedule Trigger at a fixed interval, an n8n Webhook called by a third-party service, or the trigger of another tool. That last option is the common one in a mixed setup, where an event caught on Slack or Discord ends its journey as a Twist thread, and where a digest leaves by Gmail for the people who do not open Twist daily.

The 22 operations stop at channels, threads, comments and conversation messages. When an endpoint of the Twist API is missing from the node, the HTTP Request node calls it directly and reuses the same Twist credential through its predefined authentication, so there is no second connection to maintain. If the question is whether n8n is the right host for all of this, the n8n review goes through it in detail.

Connect

How do you connect Twist to n8n?

01
Create a general integration in Twist
Twist authenticates n8n with OAuth2, and OAuth2 needs an app declared on the Twist side. Start from a Twist account, then create a general integration in the Twist app console. That page issues the Client ID and the Client Secret n8n will ask for, and it is also where a valid OAuth Redirect URL has to be configured before anything connects.
02
Register the redirect URL
Open a new Twist credential in n8n, from the Credentials menu, and copy the OAuth Redirect URL it displays. Paste that value into the OAuth 2 redirect URL field of the Twist integration, then select Update OAuth settings to save the change. Twist only completes an authorization that comes back to a URL registered there.
03
Finish the credential in n8n
Copy the Client ID and the Client Secret from Twist into the matching fields in n8n and run the connection. A credential is created once and reused everywhere: every Twist node added afterwards picks it from its dropdown, in any workflow of the instance, whether that instance runs on n8n Cloud or on a self-hosted server.

Actions

What can the Twist node do, operation by operation?

The Twist node exposes 22 operations across 4 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
Resource	Create	Get	Get Many	Update	Delete	Archive	Unarchive
Channel	✓	✓	✓	✓	✓	✓	✓
Comment	✓	✓	✓	✓	✓
Message Conversation	✓	✓	✓	✓	✓
Thread	✓	✓	✓	✓	✓

Channel

7 operations

Archive a channel

channel.archive

What you see in n8n

Notes & use cases

Archiving switches a channel to the archived state instead of removing it. Archived channels still answer Get many channels when its Archived filter is on, and Unarchive a channel brings one back to the active list.

Key parameters

Channel ID: the identifier of the channel to archive, typed in or read from an earlier node with {{ $json.field }}.

Use cases

a quarterly tidy-up lists the workspace, keeps the channels of projects marked delivered in the project tracker, and archives them so the sidebar shows current work only.

Create a channel

channel.create

What you see in n8n

Notes & use cases

This is how a workflow opens a channel-based conversation in Twist. Every thread posted later points at the channel this operation creates.

Key parameters

Workspace Name or ID: pick the workspace from the list n8n loads, or pass an ID through an expression.
Name: the name of the channel.
Color: the color of the channel, one of the twelve Twist values, Blue, Teal Blue or Salmon for instance.
User Names or IDs: the users who will take part in the channel.

Use cases

a client signed in the CRM gets its own channel, colored by account tier, with the account manager and the delivery lead already inside.

Delete a channel

channel.delete

What you see in n8n

Notes & use cases

Delete removes the channel from the workspace. It reads the same single identifier as the archive path, which makes the two easy to swap by mistake in a branch, so check which one a workflow calls before pointing it at a live workspace.

Key parameters

Channel ID: the channel to delete. The field is required, and n8n stops the node when it arrives empty.

Use cases

a demo workspace rebuilt from scratch every night, where the closing workflow deletes the channels created during the day.

Get a channel

channel.get

What you see in n8n

Notes & use cases

One channel in, its information out. This is the read step a workflow runs before deciding anything, typically to confirm a channel still exists before writing into it.

Key parameters

Channel ID: the identifier of the channel to look up.

Use cases

a support routing workflow reads the channel referenced on a ticket, and only opens its thread when the lookup returns something.

Get many channels

channel.getAll

What you see in n8n

Notes & use cases

Listing happens at workspace level: give the workspace, get its channels back as items, ready for a loop or a filter.

Key parameters

Workspace Name or ID: the workspace to list, from the dropdown or through an expression.
Return All: on, n8n walks the API pages until every channel is in; off, it stops at Limit.
Limit: the maximum number of channels returned when Return All is off.
Archived: returns only the archived conversations.

Use cases

a monthly inventory of the workspace, exported to a spreadsheet so a manager can see which channels are still open and who sits in them.

Unarchive a channel

channel.unarchive

What you see in n8n

Notes & use cases

Unarchive is the return path. A channel that was archived goes back among the active conversations, and the workflow that archived it can reverse its own move.

Key parameters

Channel ID: the archived channel to restore. Get many channels with the Archived filter is the usual way to find that identifier.

Use cases

a client comes back after 6 months; the workflow that reopens the account also puts the old channel back in the sidebar, with its threads where they were.

Update a channel

channel.update

What you see in n8n

Notes & use cases

Update edits a channel already in place. Fill only the entries that change under Update Fields, and leave the others out.

Key parameters

Channel ID: the channel to edit.
Name: the name of the channel.
Description: the description of the channel.
Color: the color of the channel, from Grey to Yellow through Berry Red.

Use cases

a channel turns red the day the project it tracks slips past its due date, and its description carries the new deadline. The status is visible before anyone opens the channel.

Comment

5 operations

Create a comment

comment.create

What you see in n8n

Notes & use cases

A comment answers inside a thread that already exists. The thread is the anchor, the content is the message, and the mention fields decide which users are named in it.

Key parameters

Thread ID: the thread the comment is attached to.
Content: the content of the comment.
Direct Mention Names or IDs: the users directly mentioned, from the list or by ID.
Send as Integration: whether the integration is displayed as the comment creator.

Use cases

a failed build posts its log link as a comment under the thread that announced the release, so the fix is discussed where the release was announced.

Delete a comment

comment.delete

What you see in n8n

Notes & use cases

Deletion works on one comment, named by its own identifier rather than by the thread it sits in.

Key parameters

Comment ID: the comment to delete, usually carried over from Get many comments.

Use cases

a status comment that a workflow rewrites every hour: the previous one is deleted before the new one is posted, so the thread keeps a single running update instead of 40 stacked lines.

Get a comment

comment.get

What you see in n8n

Notes & use cases

Reading a single comment is what a workflow does when another system kept the identifier and needs the current version of what was written.

Key parameters

Comment ID: the identifier of the comment to read.

Use cases

an approval flow stores the ID of the comment it created, then reads it back at closing time to attach the reviewer's actual wording to the record.

Get many comments

comment.getAll

What you see in n8n

Notes & use cases

All the comments of one thread come back as items, in the order asked for. That is the raw material for a digest, an export or a summary step.

Key parameters

Thread ID: the thread whose comments are read.
Return All: on, every page of comments is fetched; off, the node stops at Limit.
Limit: the maximum number of comments returned.
Order By: ASC or DESC.
As IDs: returns only the IDs of the comments.

Use cases

a Friday recap collects a thread in ASC order and turns the exchange into 5 bullet points for the client.

Update a comment

comment.update

What you see in n8n

Notes & use cases

Editing replaces the text of a comment already posted, instead of adding a second one below it.

Key parameters

Comment ID: the comment to edit.
Content: the content of the comment.
Attachments: the name of the property holding the binary data, several of them separated by commas.

Use cases

a deployment comment that starts at "in progress" and is rewritten with the final result and its report file, so nobody scrolls the thread to find which line is current.

Message Conversation

5 operations

Create a message

messageConversation.create

What you see in n8n

Notes & use cases

A conversation is the other place a workflow can write to, alongside channel threads. This operation drops a message into one of them.

Key parameters

Workspace Name or ID: the workspace holding the conversation.
Conversation Name or ID: the conversation to post in, from the list or through an expression.
Content: the content of the new message. Mentions are written [Name](twist-mention://user_id) for a user and [Group name](twist-group-mention://group_id) for a group.
Direct Mention Names or IDs: the users directly mentioned.

Use cases

a night alert lands in the ops conversation with the engineer on duty mentioned by ID.

Delete a message

messageConversation.delete

What you see in n8n

Notes & use cases

One message leaves the conversation. The node works from the message identifier, not from the conversation it belongs to, so the delete branch needs the ID captured when the message was posted.

Key parameters

Message ID: the ID of the conversation message to delete.

Use cases

a workflow that posts short-lived reminders clears yesterday's message before writing today's, and the conversation stays readable.

Get a message

messageConversation.get

What you see in n8n

Notes & use cases

Fetching a single conversation message hands a workflow the current state of something written earlier, by a person or by an earlier run.

Key parameters

Message ID: the ID of the conversation message to read.

Use cases

a handover workflow keeps the message ID when a request is opened, then reads it back when the request closes to file the original wording with the archive.

Get many messages

messageConversation.getAll

What you see in n8n

Notes & use cases

Reading a whole conversation is a paging job, driven by Limit and by the two object indexes.

Key parameters

Workspace Name or ID: the workspace of the conversation.
Conversation Name or ID: the conversation to read.
Limit: the maximum number of messages returned.
Order By: ASC or DESC.
Starting Object Index: limits messages starting at the specified object index.

Use cases

the end-of-project export of a client conversation into a spreadsheet, oldest message first, so the account history survives the workspace clean-up.

Update a message

messageConversation.update

What you see in n8n

Notes & use cases

The text of a conversation message can be rewritten in place, attachments included.

Key parameters

Conversation Message ID: the message to edit.
Content: the content of the new message, with the same mention syntax as at creation.
Attachments: the property that holds the binary data, comma separated when there are several.

Use cases

a shipping status posted once to a customer conversation and updated as the parcel moves, in the same message from order to delivery.

Thread

5 operations

Create a thread

thread.create

What you see in n8n

Notes & use cases

Threads are where a channel discussion starts. Three fields are required here, and they map to what a person would type: where, what about, and the message itself.

Key parameters

Channel ID: the channel the thread opens in.
Title: the title of the new thread, shorter than 300 characters.
Content: the content of the thread.
Recipient Names or IDs: the users attached to the thread.

Use cases

the weekly report built from a spreadsheet opens its own thread, titled with the week number, in the channel of the team it concerns.

Delete a thread

thread.delete

What you see in n8n

Notes & use cases

Deletion takes the thread identifier, the same one Create a thread produces and Get many threads returns. Nothing else is asked, so the safety net has to sit before the node, in the branch that decides which thread deserves to go.

Key parameters

Thread ID: the thread to delete.

Use cases

a duplicate thread opened by a workflow that was retried, removed by the error branch so the channel keeps one thread per event and the team stops answering the wrong one.

Get a thread

thread.get

What you see in n8n

Notes & use cases

A single thread, read on demand. Useful whenever an identifier arrives from somewhere else and the workflow needs the thread behind it before acting.

Key parameters

Thread ID: the identifier of the thread to read.

Use cases

a message carrying a Twist thread ID from another tool: the workflow reads the thread first, then adds its comment only when the thread is the expected one.

Get many threads

thread.getAll

What you see in n8n

Notes & use cases

Channel by channel, the node returns threads as items, with filters that narrow the window before the rest of the workflow runs.

Key parameters

Channel ID: the channel to read threads from.
Return All: on, every page comes back; off, the node stops at Limit.
Limit: the maximum number of threads returned.
Filter By: attached_to_me, everyone or is_starred.
Newer Than: keeps the threads newer than the Unix time given.

Use cases

a Monday digest pulls the starred threads of a project channel and mails them out.

Update a thread

thread.update

What you see in n8n

Notes & use cases

Title and content can both be corrected after posting, which matters when the first version came out of a template with a wrong value in it.

Key parameters

Thread ID: the thread to edit.
Title: the title of the thread, under 300 characters.
Content: the content of the thread.
Direct Mention Names or IDs: the users directly mentioned.

Use cases

an incident thread whose title carries the status, moved from investigating to resolved by the workflow that closes the incident.

Need help

Need help automating Twist with n8n?

A person reads every message.

FAQ

Twist and n8n, the questions that come up

01Is the Twist n8n integration free?

On the n8n side, yes. The Twist node ships with n8n, so there is nothing to install and no extra cost to use it, on n8n Cloud as well as on a self-hosted instance running through Docker or npm under the Community Edition and its Sustainable Use licence. A workflow built on one runs identically on the other. What a Twist plan costs is a separate matter and this page does not cover it. The only thing to create on the Twist side is the general integration that issues the OAuth2 keys, which is also what lets n8n call the API as your workspace.

02What credentials do you need to connect Twist to n8n?

One credential, OAuth2. Twist supports OAuth2 as its authentication method, which means a Client ID and a Client Secret generated when a general integration is created in the Twist app console. The redirect URL matters as much as the keys: the OAuth Redirect URL displayed by n8n has to be entered as the OAuth 2 redirect URL on the Twist integration, then saved with Update OAuth settings. In n8n the credential lives in the Credentials menu, is created once, and every Twist node picks it from a dropdown afterwards, so the secret is never typed twice.

03What are the limits of the Twist node in n8n?

The node covers 22 operations over 4 resources, and the reading operations are the ones to plan for. With Return All on, Get many channels, Get many comments and Get many threads walk the API pages until everything is in; with it off, they stop at Limit. Get many messages is paged with Limit and the object indexes instead. For an endpoint of the Twist API that the node does not expose, the HTTP Request node calls it directly and reuses the same Twist credential through its predefined authentication, so there is no second connection to maintain and no separate secret to rotate.

04Does the Twist node in n8n react in real time?

There is no Twist trigger node in n8n, so a workflow involving Twist starts somewhere else. Three options cover almost everything: a Schedule Trigger at a fixed interval, an n8n Webhook, meaning a URL n8n exposes so another service can start the run, or the trigger of another tool already in the workflow. For reading side, a schedule every 10 minutes calling Get many threads with the Newer Than filter gives a near-continuous view without hammering the API. For writing side, the question does not arise: the workflow posts when its own trigger fires.

05n8n or Make for Twist?

It depends on where the data should live and how the bill is counted. Make is hosted by Make, has no self-hosting option, and is billed per operation, so a workflow that lists a workspace and loops over its channels grows more expensive as the workspace grows. n8n runs on n8n Cloud or on your own server through Docker or npm, and the same workflow behaves the same way on both. Compare four things: hosting, control over the data passing through, cost model, and how each visual editor handles branches. Neither tool is wrong; the answer follows the constraint that weighs most for the team.

Create a general integration in Twist

Register the redirect URL

Finish the credential in n8n

Need help automating Twist with n8n?