Resources · n8n integration

Twake n8n integrationAutomate Twake with n8n.

One operation, and any workflow can post in Twake. The Twake n8n integration exposes a single node action, Send a Message: write the Content, pick the channel, and n8n delivers it. No Twake trigger exists, so the workflow starts from a schedule, a webhook, or another app.

Try the Twake integration on n8nSee the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Twake n8n integration actually give you?

The Twake n8n integration wires your n8n workflows into Twake through one node that sends messages. The node ships with n8n, so you drag it onto the canvas, attach a Twake credential, and any step of a running workflow can drop a line into a channel. The catalog lists 1 operation, message.send. Everything else in the Twake API stays reachable through the HTTP Request node, which calls any endpoint and reuses the same credential.

Start with the gesture, not the field list. Take a workflow that already runs, add the Twake node as its last step, open Content, and type the sentence a teammate should read tomorrow morning. Anything that changes from run to run comes from the item entering the node, written as an expression, the n8n syntax that reads a value from the previous step: {{ $json.field }}. Pick the channel, save, run once. That is the build.

First result, a lead never waits for someone to refresh a tab. A Google Sheets step reads the row that just landed in the signup sheet, the Twake node posts one clean line into the channel set in Channel Name or ID, and the person who calls back sees it where they already spend the day.

Second result, a ticket stops aging in silence. A Schedule Trigger wakes the workflow at a fixed interval, a Jira Software step pulls what is still open, and Twake gets one message the team can act on instead of a report nobody opens. Third result, the stand-up writes itself: Google Calendar returns the day's meetings, and the channel opens on the agenda before anyone asks for it.

When the thing you want from Twake is not in the node, use the HTTP Request node. It calls any endpoint of the Twake API and reuses the same credential through predefined authentication, so you stay on one connection instead of managing two. Same workflow, same canvas, one node that speaks raw API next to one node that speaks Twake.

Twake has no trigger node in n8n, which shapes how you design: a Twake workflow always starts somewhere else, with a Schedule Trigger on a fixed interval, with the n8n Webhook node called by a third-party service, or with the trigger of another tool. Plan that entry point first and the message step becomes trivial. If you are weighing platforms before you build, the n8n review covers hosting and cost, and the n8n training walks through expressions and credentials on real workflows.

Connect

How do you connect Twake to n8n?

  1. 01

    Pick the credential type that matches your Twake

    Twake credentials come in two supported methods, Cloud API key and Server API key. Cloud API key is for a Twake Cloud environment. Server API key is for a Twake instance you host yourself. Decide this first, because the two ask for different values and you fill only one of them. A Twake account is the prerequisite in both cases.

  2. 02

    Collect the values inside Twake

    On Cloud API key, n8n wants a Workspace Key, generated when you install the n8n application in your Twake Cloud environment and select Configure. On Server API key, n8n wants a Host URL, the address of your self-hosted instance, plus a Public ID and a Private API Key, both generated when you create an app.

  3. 03

    Create the app, then save the credential once

    For the server path, go to Workspace Settings, Applications and connectors, access your applications and connectors, then create an application. Open its API Details, copy the Public identifier into Public ID and the Private key into Private API Key. Save the credential from the n8n Credentials menu: every workflow can then select it in the node dropdown.

Actions

What the Twake node does

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

Resources × operations matrix
ResourceSend
Message✓

Message

1 operation
01

Send a message

message.send

What you see in n8n

Notes & use cases

Posts a message into a Twake channel from anywhere in a workflow, so a result computed three nodes earlier reaches the right people.

Key parameters

  • Content: the message text, the only required field. Empty, it blocks the node. Use an expression like {{ $json.field }} to carry a value from the previous step.
  • Channel Name or ID: the channel's ID, picked from the list n8n loads or set with an expression.
  • Sender Icon: in Additional Fields, the URL of the image used as the icon on the message.
Use cases
a nightly check posts its verdict into the ops channel, and a Gmail step forwards an inbound request to the team that owns it.
Need help

Need help automating Twake with n8n?

A person reads every message.

FAQ

Twake and n8n, the questions that come up next

01Is the Twake n8n integration free to use?
Yes on the n8n side. The Twake node ships with n8n, so there is nothing to install and no add-on to buy, on n8n Cloud or on an instance you host yourself under the Community Edition and its Sustainable Use license. The workflow you build is the same in both places, which means you can prototype on Cloud and move the same canvas to your own server later. What you do need is a Twake account, since the credential authenticates against your workspace. The credential itself is created once from the Credentials menu and reused across every workflow that talks to Twake.
02What credentials do you need for the Twake node?
Two authentication methods are supported: Cloud API key and Server API key. The Cloud API key path needs a Workspace Key, generated when you install the n8n application into your Twake Cloud environment and select Configure. The Server API key path needs three values: a Host URL pointing at your self-hosted instance, a Public ID, and a Private API Key. Those last two come from an app you create in Twake, under Workspace Settings, Applications and connectors, then Create an application. Open the app's API Details, copy the Public identifier into Public ID and the Private key into Private API Key.
03What are the limits of the Twake node in n8n?
The catalog gives the Twake node 1 resource and 1 operation, message.send, so the node itself covers sending a message with its Content, its channel, and the optional sender fields. When the call you want is not part of that operation, the HTTP Request node takes over: it reaches any endpoint of the Twake API and reuses the same Twake credential through predefined authentication, so you do not create a second connection. In practice, one workflow can hold both, the Twake node for messages and an HTTP Request node next to it for the rest.
04Does the Twake integration react in real time?
Twake has no trigger node in n8n, so nothing on the Twake side starts a workflow on its own. A workflow that involves Twake begins with another trigger, and you pick it based on the timing you need. A Schedule Trigger runs the workflow at a fixed interval, which fits recaps, reminders, and periodic checks. The n8n Webhook node gives you a URL that a third-party service calls, so the workflow starts when that service has something to say. The trigger of another tool works the same way: its event fires, and the Twake node posts at the end of the chain.
05n8n or Make for Twake?
It depends on four criteria, and both tools are legitimate. Hosting comes first: n8n runs on n8n Cloud or on infrastructure you control with Docker or npm, while Make is a hosted platform with no self-hosting option. Data control follows from that choice, since a self-hosted n8n keeps message content and credentials inside your own environment. Cost model is the third: Make bills per operation, which matters when a workflow sends many messages. The fourth is how you think about visual logic and which canvas fits the way your team builds. For Twake specifically, both reach the same messages.
Same platform

Other docs you might need on this stack.

Browse all integrations