Slack n8n integrationAutomate Slack with n8n.

Archiving closes a conversation without deleting it: the channel leaves the active list, its history stays readable, and Unarchive brings it back later.

• Channel: the Slack channel to archive, chosen from the list, by ID or by URL. The field is not marked required, so it often arrives from a previous step through an expression of the form {{ $json.channel }}.

Close ends a direct message or a multi-person direct message. The conversation is not deleted, it simply stops sitting in the sidebar of the people involved.

• Channel: required. The direct message to close, selected from the list, by ID or by URL. Feed it the ID that Open a channel returned, so the run closes what it opened.

This operation starts a new channel-based conversation and returns its ID, which every later step of the same run can reuse.

• Channel: required, a plain text field holding the channel name (the placeholder reads Channel name), so an expression can build it from the record that started the workflow.
• Channel Visibility: required, either public (Public Channel) or private (Private Channel).

Get a channel reads the information Slack holds about one conversation, which is how a workflow checks what it is about to write into.

• Channel: required, the channel to read, from the list, by ID or by URL.
• Include Num of Members: an option that adds the member count to the response, handy when a rule depends on how many people sit in the room.

Get many channels returns the conversations of a Slack team as a list of items, one per channel, ready to loop over.

• Return All: on, n8n walks the pages of the API and brings back every channel; off, Limit caps how many come back.
• Exclude Archived: a filter that leaves archived conversations out of the list.
• Types: mix and match public_channel, private_channel, mpim and im to keep only the kinds you care about.

History pulls the messages and events of one conversation, so a workflow can read what was said instead of only writing into Slack.

• Channel: required, the conversation to read the history from.
• Oldest and Latest: the start and the end of the time range to include; Inclusive keeps the messages sitting exactly on those timestamps.
• Return All: page through the whole range, or leave it off and set Limit.

Invite adds one or several people to a channel. They find it in their sidebar, with the conversation that already took place.

• Channel: required, the channel to invite to.
• User Names or IDs: required, the users to bring in. Choose them from the list, or pass their IDs with an expression when they come from a previous node.

Here the app itself joins an existing conversation. Slack only delivers events from channels the app belongs to, which makes this operation the usual fix when a trigger stays quiet.

• Channel: required, the conversation to join, from the list, by ID or by URL.

Kick removes a user from a channel, the mirror image of Invite. The person keeps access to everything else in the workspace.

• Channel: required, the channel to remove the user from.
• User Name or ID: the account to remove, picked from the list or given as an ID through an expression.

Leave takes the app out of a conversation. Events from that channel stop reaching the Slack Trigger, and the bot can no longer post there.

• Channel: required, the conversation to leave.

This operation lists the people in a conversation, one item per member, which is what an audit or a reminder needs before it goes out.

• Channel: required, the channel to read the members from.
• Resolve Data: on, n8n resolves the data automatically, since the response otherwise carries only the ID of each resource.
• Return All: take the full roster, or leave it off and set Limit.

Open starts a direct message, or resumes one that already exists. With a single user it creates a one to one conversation; with several it opens a group message and preserves the order of the users.

• User Names or IDs: the people to open the conversation with. Supply a channel when you do not supply users.
• Channel ID: resumes an existing im or mpim from its ID, instead of the users field.
• Return IM: asks Slack for the full IM channel definition in the response.

Rename changes the name of a conversation. Two values do the whole job: the channel to rename, and the name it carries from now on.

• Channel: required, the channel to rename.
• Name: required, the new name for the conversation.

Replies returns a thread: the parent message and everything posted underneath, which is where most of the real conversation happens.

• Channel: required, the channel holding the thread.
• Message Timestamp: required, the timestamp of the parent message, in the 1663233118.856619 form Slack uses to identify a message.
• Oldest, Latest and Inclusive: bound the replies to a time range; Return All pages through the rest.

Sets the purpose of a conversation, which is where a channel says what it exists for. Writing it from a workflow means a channel never stays anonymous.

• Channel: required, the channel to set the purpose of.
• Purpose: required, the new text.

Sets the topic of a conversation. The topic changes far more often than the purpose, which describes the channel, and that is what makes it worth automating.

• Channel: required, the channel to set the topic of.
• Topic: required, the text to display.

Unarchive brings an archived conversation back to the active list, with its history untouched.

• Channel: required, the archived conversation to restore, picked from the list or passed as the ID your workflow stored when it archived the channel.

Get a file reads a single file stored in Slack and returns what the API knows about it.

• File ID: the identifier of the file to read. The field is not marked required, so it usually arrives through an expression pointing at the field of the incoming item that carries the ID.

Get many files searches and filters the files of the team, the operation to reach for when nobody remembers where a document ended up.

• Channel Name or ID: keeps only the files listed in one channel.
• Types: filters by kind, among all, gdocs, images, pdfs, snippets, spaces and zips.
• Message Timestamp From and Message Timestamp To: keep the files created inside that window, both bounds included.
• Return All: page through every match, or leave it off and set Limit.

Upload sends a file produced by the workflow into Slack, either as a new file in the workspace or posted directly into the channels you name.

• File Property: required, the name of the binary property that holds the data of the file to upload, so the node knows which output of the previous step to take.
• Channel Names or IDs: the channels the file is sent to, with Initial Comment for the message that introduces it.
• Thread Timestamp: posts the file as a reply. Use the timestamp of the parent message, never that of a reply.

Removes a single message from Slack. Two values point at it: the conversation it belongs to, and its timestamp, which Slack uses in place of a message ID.

• Delete Message From: pick channel or user, depending on whether the message was posted in a channel or in a direct message.
• Channel: the Slack channel to delete the message from, picked from the channel list.
• Message Timestamp: the timestamp of the message to delete, in the 1663233118.856619 form.

A permalink is the stable Slack URL of one message. The node builds it from the message timestamp, so another tool can point back into the conversation instead of copying the text out of it.

• Message Timestamp: the timestamp of the message you want the link for, for example 1663233118.856619.
• Channel: optional here, the Slack channel to get the message permalink from.

Searches Slack messages for a piece of text and returns the matches, one item per hit. Order and volume are set in the same node.

• Search Query: the text to search for within messages.
• Sort By: desc for newest first, asc for oldest first, relevance to let Slack rank by relevance score.
• Return All: switch it on to page through every match; left off, Limit caps how many messages come back.
• Search in Channel: under Options, restricts the search to the channels you select.

Posts a message to a channel or as a direct message. The options decide whether the result reads like a plain notification or like a small interface.

• Send Message To: channel to post in a channel, user to send a direct message.
• Channel: the Slack channel to send to.
• Message Text: the text to post, with Slack markdown on by default and switchable in Options.
• Message Type: text for a simple message, block to paste JSON from Slack's Block Kit Builder into Blocks, attachment for attachments.
• Include Link to Workflow: appends a link to the workflow, useful once several workflows post to the same channel.

Pauses the workflow until someone answers in Slack. n8n posts the request, waits, then resumes with the decision attached to the item.

• Message: the request the approver reads, sent to the Channel or user in Send Message To.
• Response Type: approval for buttons, freeText for a written reply, customForm for a form built in Form Elements.
• Capture Who Responded: turn it on to switch the approval buttons to Slack interactive buttons and record who responded. Restrict Who Can Approve then limits who may act.

Rewrites a message already in the channel, so one post carries the current state.

• Channel: the Slack channel to update the message from.
• Message Timestamp: the timestamp of the message to update, carried over from the node that posted it.
• Blocks: the JSON from Slack's Block Kit Builder, pasted in to replace the layout, with expressions for the variable part.
• Notification Text: the fallback text shown in Slack notifications, markdown included unless Options say otherwise.
• Parse: under Update Fields, client, full or none changes how Slack treats the new text.

Puts an emoji on a message that already exists, a mark the team reads at a glance.

• Channel: the Slack channel the message sits in.
• Message Timestamp: the timestamp of the message to react to.
• Emoji Code: the code, not the character, so +1 rather than the thumbs-up emoji itself.

Reads the reactions on one message and hands them to the next node, so a workflow can count who reacted with what. Nothing is written back to Slack.

• Channel: the Slack channel to get the reactions from.
• Message Timestamp: the timestamp of the message to read.

Takes one emoji back off a message. The reaction is named the same way it was added, by channel, timestamp and code, so the removal undoes exactly what an earlier step marked.

• Channel: the Slack channel the message was posted in.
• Message Timestamp: the timestamp of the message.
• Emoji Code: the same code used when the reaction was added, +1 for instance.

Stars a message or a file for the account the credential belongs to, the same account whose list Get many stars reads back.

• Item to Add Star: message or file.
• Channel and Message Timestamp: where the message sits, when the target is a message.
• File ID: the file to star, when the target is a file.
• File Comment: under Options, stars a comment left on a file instead.

Unstars an item. Nothing is required at the top of the node: every value travels in Options, and you fill only the ones that match what was starred.

• Channel Name or ID: the channel where the starred message was posted, chosen from the list or set with an expression.
• Message Timestamp: the timestamp of the message to unstar.
• File ID or File Comment: the file, or the comment on a file, to unstar instead.

Lists the stars of the authenticated user, one item per starred message or file. It reads the account behind the credential, not the workspace as a whole.

• Return All: on, the node keeps asking for pages until the list is exhausted; off, Limit fixes the maximum number of stars.

Fetches the Slack record of a single user from an ID. Useful when an event or an earlier node leaves an ID behind and the rest of the workflow needs a name.

• User: the ID of the user to get information about, picked from the list or supplied by an expression such as {{ $json.data.responder.id }} after an approval step.

Pulls the list of users in the workspace, one item per member. From there a workflow can match Slack accounts against another system, or simply count them.

• Return All: enabled, n8n collects the full member list page by page; disabled, Limit decides how many users come back.

The profile holds what a person shows about themselves in Slack: first name, last name, status, custom fields. This operation reads it for one user and returns it as an item.

• User: the ID of the user whose profile you want, picked from the user list or set with an expression.

Checks whether a user is online in Slack right now. The answer describes the present moment, so read it just before the workflow needs to decide something.

• User: the ID of the user to get the online status of.

Writes values back into a Slack profile. Everything lives in Options, and two of those fields carry a condition worth checking before the workflow goes live.

• First Name and Last Name: the name shown in Slack.
• Email: can only be changed by admins, for users on paid teams.
• User ID: the user to change, which only team admins on paid teams may specify.
• Set Status and Custom Fields: the status line and the custom profile fields.

Adds people to a user group that already exists. Existing members are preserved, so the list you pass is an addition and never a replacement.

• User Group ID: the encoded ID of the user group to update.
• User Names or IDs: the users to add, chosen from the list or given as IDs through an expression.
• Include Count: under Options, returns the number of users in the group alongside the result.

Creates a user group, the handle that reaches several people at once. Two of its values have to be unique in the workspace, which any workflow generating groups needs to plan for.

• Name: a name for the user group, unique among user groups.
• Handle: the mention handle, unique among channels, users and user groups.
• Description: a short description of the group.
• Channel Names or IDs: the channels the group uses as a default.

Switches a user group off. The group is not destroyed, since Enable brings it back with the same ID, which makes this the safe way to retire a handle nobody should ping anymore.

• User Group ID: the encoded ID of the user group to update.
• Include Count: under Options, adds the number of users in the group to the response.

Turns a disabled user group back on. It takes the same single identifier as Disable, so the pair can be driven from a schedule or from a form without any other lookup.

• User Group ID: the encoded ID of the user group to update.

Every user group in the workspace comes back as an item, and three options widen what each one carries.

• Return All: leave it off and Limit bounds the number of groups; turn it on for the complete list.
• Include Users: adds the list of users for each group.
• Include Disabled: adds the groups that have been disabled.
• Include Count: adds the number of users in each group.

Open one group and get its members back. The response carries user IDs by default, and a single option turns them into full user objects, which spares a lookup per person.

• User Group ID: the encoded ID of the user group.
• Resolve Data: under Options, returns full user objects instead of just user IDs.

Edits an existing group without touching its membership. Name, handle, description and default channels all sit in Update Fields, where you add only what should change.

• User Group ID: the encoded ID of the user group to update.
• Name: a new name, still unique among user groups.
• Handle: a new mention handle, unique among channels, users and user groups.
• Channel Names or IDs: the default channels of the group.