n8n Integrations: Connecting Slack, Gmail and Google Sheets with Credentials

We checked this article against the official n8n documentation on October 2, 2026. Screen names and steps change between versions. Before you configure anything, check the latest information in the sources at the end.

n8n integrations are built from two parts: nodes that hold the operations for each service, and credentials for logging in to that service. Commonly used services such as Slack, Gmail, and Google Sheets have dedicated nodes. We explain basic n8n operations in how to use n8n.

How n8n Integrations Work: Nodes and Credentials

A node is one step in a workflow. Each node holds operations for a service, such as sending a message with the Slack node or adding a row with the Google Sheets node.

Credentials are the authentication information that connects a workflow to an external API or database. They are stored inside n8n. You create credentials from the Create button at the top left, or from the credential selector in a node's edit screen. When you save, n8n tests the connection.

By default, the name is ‘node name account’. The official docs recommend renaming it so the service, type, and purpose are clear. That way you can tell what each credential is for as their number grows.

Finding Available Integrations

You can find available services on n8n's Integrations page. You can filter by type (regular nodes, triggers, core nodes) and by category, such as AI, analytics, and communication. According to the pricing page, all plans can use all integrations (nodes).

The credentials list in the official docs has setup steps for each service. Before using a node, open the steps for that service.

Even for the same service, there are trigger nodes that start on an event (such as Slack Trigger) and nodes that perform actions (such as Slack). The two may support different authentication methods.

Notion and Google Drive

Notion and Google Drive also have dedicated nodes. Notion authenticates with an integration token or OAuth2. With a token, share the Notion pages you want to use with the integration you created. Requests to pages that are not shared return an error. Google Drive uses the Google authentication described below.

Connecting Slack

Slack has two authentication methods. Which one you can choose depends on the node.

Connecting with OAuth2

On n8n Cloud, choose Connect my account on the credentials screen and log in to Slack in the browser. With self-hosting, you create a Slack app yourself.

1. Copy the OAuth Callback URL from the Slack credentials in n8n
2. On the Slack API Apps page, choose Create New App, then From a manifest
3. Select the workspace to develop in, add the copied URL and required scopes to the manifest JSON, and create the app
4. Enter the Client ID and Client Secret from App Credentials under Basic Information into n8n
5. Under OAuth & Permissions, choose Install to Workspace, allow it, and connect from the credentials in n8n

Installing the app in a workspace requires Slack workspace admin permissions. If you are connecting to your company's Slack, talk to the admin. If you turn on Slack token rotation, tokens expire after 12 hours and the n8n credentials stop working. Keep it off in production.

Triggering on Slack events

Slack Trigger uses the Slack app's Event Subscriptions. Enter the n8n webhook URL as the Slack app's Request URL. Slack allows only one Request URL per app. After testing with the test URL, switch to the production URL. n8n recommends entering Slack's Signing Secret in the credentials to verify request signatures.

We explain how to use AI employees inside Slack in using AI employees in Slack and Microsoft Teams.

Connecting Gmail and Google Sheets (Google Authentication)

Google nodes such as Gmail, Google Sheets, and Google Drive authenticate with OAuth2 or a service account. n8n recommends OAuth2, which is widely usable and easy to set up. Using a service account with Gmail requires domain-wide delegation, which Google does not recommend. So use OAuth2 for Gmail.

On n8n Cloud

On n8n Cloud, you can use Managed OAuth2 with nodes such as Gmail, Google Sheets, and Google Drive. Just choose Sign in with Google on the credentials screen. No setup in Google Cloud Console is needed.

With self-hosting

Managed OAuth2 is not available with self-hosting. Create an app in Google Cloud Console and enter the Client ID and Client Secret into n8n.

1. Create a project in Google Cloud Console
2. Enable the APIs you will use. For Gmail, the Gmail API. For Sheets, you need the Google Drive API in addition to the Google Sheets API
3. Configure the OAuth consent screen. Choose Internal if it is used only within your Google Workspace, otherwise External
4. Create an OAuth client ID. Set the type to Web application and add n8n's OAuth Redirect URL as an authorized redirect URI
5. Enter the Client ID and Client Secret into n8n, authenticate with Sign in with Google, and save

If you choose External, the app starts in testing mode. Only Google accounts added as test users can authenticate. If you run it on your own computer, you can use localhost as the redirect URI. You do not need a public domain or SSL certificate.

Available operations

The Google Sheets node can create and delete spreadsheets, and append, update, get, and delete rows. The Gmail node can send, reply to, and get messages, add labels, and create drafts. The Gmail node can also be used as a tool for AI agents.

Use HTTP Request for Services Without a Dedicated Node

For services without a dedicated node, or operations a node does not cover, call the API with the HTTP Request node. If the service has a REST API, you can get and send data. You can also paste a curl command to import its settings.

• Predefined Credential Type: reuse credentials for a service n8n supports. n8n recommends this option
• Generic Credential Type: for services n8n does not support. Choose from Basic auth, header auth, query auth, OAuth1, OAuth2, and others

You can also call operations a dedicated node lacks by selecting that service's credentials in the HTTP Request node. The official Google Sheets node docs describe this method too.

Many credentials have an Allowed HTTP Request Domains setting. You choose which domains the HTTP Request node can use that credential for: all, only specified domains, or none. This setting keeps credentials from being sent to unintended URLs.

Handling Credentials Safely

n8n encrypts credentials before storing them in the database. With self-hosting, the encryption key created on first startup is saved in the ~/.n8n folder. If you lose the key, you cannot restore credentials from a backup.

• Decide the sharing scope: credential sharing is available on all n8n Cloud plans and on self-hosted Business and Enterprise. People you share with cannot view or edit the credential contents
• In the Community edition, only the instance owner and the creator can access workflows and credentials
• Narrow permissions: limit Slack scopes and Google APIs to what your operations need
• Be careful with exports: delete --decrypted exports, which write credentials in plain text, when you are done
• Use an external vault: paid plans can connect to an external secrets vault

We explain how to hand over the workflows you build in exporting n8n workflows.

Employee Store is a marketplace where companies can adopt AI agents built by developers. You can list n8n workflows too. There is no listing fee or upfront cost. The fee is 20% of the deal amount and applies only when a deal closes. For details, see the seller guide.