APP Credentials Collection
Managing Credentials
•
You can collect connected credentials in the Credentials tab.
OpenAI
•
To use the openAI API, you must first register a payment method . Please prepare a card that supports international payments in advance. Fees are pay-as-you-go, and to avoid excessive charges, be sure to set a limit.
•
Next, you'll issue an API_KEY . Be sure to save the API key in Notepad. For security reasons, once exposed, the API key cannot be exposed again. The API key is structured like this: sk-...ifFb .
•
When linking an openAI account in n8n, copy and paste the API KEY issued above into the API KEY field to complete the process.
Slack
1.
2.
Select Create New App > From scratch.
3.
Enter the App Name
4.
Select the Workspace to apply to .
5.
Create an app with Create App.
6.
From the left menu, select Features > OAuth & Permissions.
7.
In Scopes, select the scope appropriate for your app. For a list of recommended scopes, see Scopes .
8.
After adding the scope, go to the OAuth Tokens section and select Install to Workspace . You must be a Slack workspace administrator to complete this task.
9.
Select Allow.
10.
Copy the Bot User OAuth Token value and paste it after authenticating with n8n below.
11.
If you are using these credentials for a Slack trigger, complete the app setup by following the steps in Configuring Slack triggers .
Google OAuth2 (Calendar, Drive, Sheets, Mail, Youtube)
Prerequisites
•
Set up OAuth #
There are five steps to connecting your n8n credentials to Google services:
2.
4.
Create a Google Cloud Console Project
First, create a Google Cloud Console project. If you already have a project, skip to the next section:
1.
2.
From the top menu, select the Projects dropdown in the top navigation and select New Project , or go directly to the New Project page.
3.
Enter a Project Name and select a Project Location .
4.
Select Create .
5.
Check the top navigation and make sure your project is selected in the Project dropdown. If not, select the project you just created.
Using the API
Once your project is created, enable the APIs you need to access:
1.
Check the Projects dropdown in the top navigation of Google Cloud.
2.
Go to APIs & Services > Libraries .
3.
Search for and select the API you want to enable.
For example, for the Gmail node, we retrieve and enable the Gmail API.
4.
Some integrations may require or require access to other APIs:
•
•
5.
Select Enable .
Configuring the OAuth consent screen
If you have never used OAuth in a Google Cloud project before, you will need to configure the OAuth consent screen :
1.
Check the Projects dropdown in the top navigation of Google Cloud.
2.
Open the left navigation menu and go to APIs & Services > OAuth Consent Screen .
3.
For User Type , select Internal for user access within your organization's Google Workspace, or External for all users with a Google Account .
4.
Select Create .
5.
Enter the required information:
•
App name
•
User Support Email
•
Email address field in Developer Contact Information
6.
Add in the Verified Domains section: n8n.cloud
7.
Select Save and then Continue to go to the Scope page.
8.
There is no need to set a range.
To go to the summary page , select Save , then select Continue again .
9.
Review the information on the summary page for accuracy.
Creating Google OAuth client credentials
Then generate OAuth client credentials from Google:
1.
In the APIs and Services section, select Credentials .
2.
+ Select Create Credentials > OAuth Client ID .
3.
Select Web Application from the Application Type drop - down .
4.
Google automatically generates a name .
Update to a name recognizable in the console .
5.
Copy the OAuth redirect URL from your n8n credentials . Paste it into Authorized redirect URIs in your Google Console.
6.
Select CREATE .
N8n credentials completed
Complete the n8n credentials with your Google project and credentials fully configured:
1.
Copy the Client ID from the mode you created in Google's OAuth Client .
Enter this entry in your n8n credentials.
2.
Copy the Client Secret from the same Google mode .
Enter this entry in your n8n credentials.
3.
Complete Google authentication by selecting Google Sign-in in n8n .
4.
Save your new credentials .
Airtable
Prerequisites
Supported authentication methods
•
Personal Access Token (PAT)
•
OAuth2
API Key deprecation
N8n was used to provide API key authentication with Airtable. Airtable will fully depreciate these keys as of February 2024. If you are using Airtable API credentials, replace them with Airtable personal access tokens or Airtable OAuth2 credentials. We recommend using personal access tokens instead.
Related Resources
Using personal access tokens
To configure these credentials, you will need:
•
Personal Access Token (PAT)
To create a PAT:
1.
2.
+ Select Create a new token .
Airtable opens the Create Personal Access Token page.
3.
Enter the name of the token n8n credential
4.
Add scopes to your token . For more information, see Airtable's scopes guide. n8n recommends using the following scopes:
•
Data.records:read
•
Data.records:write
•
Schema.bases:read
5.
Select Access to Tokens .
You can choose from a single base, multiple bases (including bases from different workspaces), current and future bases from any workspace you own, or all bases from all workspaces you own, including any bases/workspaces you add in the future.
6.
Select Create Token .
7.
Airtable opens a mode where tokens are displayed.
Copy this token and enter it as an access token in your n8n credentials.
Using OAuth2 #
To configure these credentials, you will need:
•
OAuth redirect URL
•
Client ID
•
Customer Secrets
To generate all of this information, register a new Airtable integration:
1.
2.
Select the Register New OAuth Integration button.
3.
Enter a name for your OAuth integration.
4.
Copy the OAuth redirect URL from your n8n credentials .
5.
In Airtable, paste that redirect URL into OAuth Redirect URL .
6.
Select Unified Registration .
7.
On the next page, copy the Client ID from Airtable and paste it into the Client ID field in your n8n credentials .
8.
In Airtable, select Generate Client Secret .
9.
Copy the client secret and paste it into the Client Secret field in your n8n credentials.
10.
In Airtable, select the following ranges:
•
Data.records:read
•
Data.records:write
•
Schema.bases:read
11.
Select Save Changes in Airtable .
12.
Select Link My Account in n8n Credentials .
Subsidy Access Mode opens.
13.
Select the base (or all bases) you want to work on, following the instructions.
14.
Complete the connection by selecting Grant Access .
Please see the Airtable New Integrations documentation for new OAuth integration registration steps .
IMAP (when using mail other than Gmail)
Naver Mail
•
Enable IMAP in Naver Mail settings
•
•
Enter the password that appears when you proceed in the order below.
1.
Menu location: Naver ID > Security settings > Basic security settings > 2-step authentication > Management
2.
After reconfirming your Naver login password, check the ‘Application Password Management’ function.
3.
Select the type of application you want to use or enter it directly and click the Create button
4.
Confirm or copy the generated password and enter it in the password field on the application's login screen.
Kakao Mail
•
Configure IMAP settings. You can check the IMAP server, port, ID, and password in Kakao Mail. https://mail.kakao.com/setting/POP3IMAP
•
At this time, the PW must be imported as a two-factor authentication, not the password of the email account.
Notion
Use API integration tokens (Recommended)
To configure these credentials, you will need:
•
Internal Integration Secret :
It is created when you create a Notion integration.
To create a unified secret, create a concept unified and retrieve the unified secret from the Secrets tab:
1.
2.
+ Select the New Integration button.
3.
For example, enter the name of the integration: n8n integration
. Add a logo if you want.
4.
Select Submit to create the integration.
5.
Open the Features tab. Select the following features:
•
Read content
•
Update content
•
Insert content
•
User information without email addresses
6.
You must save your changes .
7.
Select the Secrets tab.
8.
Copy the Internal Integration Token and add it as the n8n Internal Integration Secret .
For more information about service authentication, see the Setting up an internal integrated authentication flow document .
Share concept pages through integration
For the integration to interact with Notion, you need to grant the integration page permission to interact with pages in your Notion workspace :
1.
Visit the page in your Notion workspace.
2.
Select the triple dot menu at the top right of the page.
3.
In Connections , select the connection target .
4.
Use the search bar to find and select Integration from the drop-down list.
If you share one or more pages with the integration, you can initiate an API request. If the pages are not shared, an API request will respond with an error.
Using OAuth2 #
To configure these credentials, you will need:
•
Client ID : Generated when you configure public integration.
•
Customer Secrets :
It is created when you configure a public integration.
1.
2.
+ Select the New Integration button.
3.
For example, enter the name of the integration: n8n integration
. Add a logo if you want.
4.
Select Submit to create the integration.
5.
Open the Features tab. Select the following features:
•
Read content
•
Update content
•
Insert content
•
User information without email addresses
6.
Select Save Changes .
7.
Go to the Distribution tab.
8.
Would you like to make this integration public?
Control.
9.
Enter your company name and website in the Organization Information section.
10.
Copy the n8n OAuth redirect URL and add it as a Redirect URI in the OAuth Domains and URLs section of your Notion integration.
11.
Go to the Secrets tab.
12.
Copy the Client ID and Client Secret and add them to your n8n credentials.
For more information about service authentication, see Setting up Notion's public unified authentication flow .
•
You can check it at the link below
Internal integration and public integration
The internal integration is as follows:
•
Applies to a single workspace only.
•
Only members of that workspace can access it.
•
Ideal for improving your personalized workspace.
Internal integrations use a simpler authentication process (integrated secrets) and do not require security review prior to publishing.
Public integration is as follows:
•
Can be used across multiple, unrelated Notion workspaces.
•
Accessible to all Notion users, regardless of workspace.
•
Ideal for meeting a wide range of use cases.
Public integrations use the OAuth 2.0 protocol for authentication and require Notion security review before publishing.
Philips Hue
•
•
◦
Copy the OAuth callback URL from n8n and add it as a callback URL .
◦
Copy the AppId , ClientId , and ClientSecret and enter them into the corresponding fields in n8n.
•
Once completed, copy the ClientId and ClientSecret values and enter them into n8n.
•
If “Account connected” appears, it is successful.
Github
Prerequisites
Supported authentication methods
•
API Access Token:
We use this method on all GitHub nodes.
•
OAuth2:
This method only works with GitHub and the GitHub trigger node, and is not used by the GitHub document loader .
Related Resources
Using API Access Tokens
There are two steps to setting up these credentials:
2.
Please see the sections below for detailed instructions.
Generate a personal access token
Recommended Access Token Types
N8n recommends using personal access tokens (classic). GitHub's fine-grained personal access tokens are still in beta and do not have access to all endpoints.
To generate a personal access token:
1.
If you haven't already, verify your email address on GitHub.
2.
3.
4.
In the left navigation, under Personal Access Tokens, select Tokens (Classic ) .
5.
Select Create New Token > Create New Token (Classic ) .
6.
Enter a descriptive name for the token in the Memo field. n8n integration
7.
Select the desired expiration for the token or select No expiration .
8.
Select the scope of the token . n8n repo for GitHub node
Just select the range
•
Tokens that are not scoped can only access public information.
•
Reference
9.
Select Generate Token .
10.
Copy the token.
For more information, see Creating a Personal Access Token (Classic) . For more information about GitHub scopes , see Scopes for OAuth Apps .
Set credentials
Then with your n8n credentials:
1.
If you are not using GitHub Enterprise Server, do not change your GitHub server URL.
•
If you're using GitHub Enterprise Server, update your GitHub server to match the URL of your server .
2.
Enter your username as it appears on your GitHub profile .
3.
Enter the access token generated above .
OpenWeather
Apps not provided
Buffer
•
Make provides it, but does not currently provide new APIs.
•
•
Unofficial Support
•
Below is a guide on how to use it via API, although it is not officially supported by n8n.
How to easily get cURL information into HTTP Node
•
Documents providing an API usually provide an API Endpoint .
◦
This is the API documentation provided by OpenAI. https://platform.openai.com/docs/api-reference/chat/create
◦
After finding the content that says cURL, find your API key value and other required input parameters, enter them, and copy them.
curl https://api.openai.com/v1/chat/completions \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $OPENAI_API_KEY" \
-d '{
"model": "gpt-4o",
"messages": [
{
"role": "system",
"content": "You are a helpful assistant."
},
{
"role": "user",
"content": "Hello!"
}
]
}'
•
Open the HTTP Request node and select Import cURL.
•
Just paste the content you copied.
•
Sometimes some values are missing due to bugs. You can run it and check if all values work properly.
Perplexity
•
Perplexity API issuance link (API_KEY can be issued only after registering a payment method and charging at least $3)
•
Perplexity API Usage Documentation
N8n setting value
•
Method: POST
•
Authentication: Generic Credential Type
•
Generic Auth Type: Header Auth
◦
Header Auth Name: Authorization
◦
Header Auth Value: Bearer
•
Send Headers : Enable
◦
Using Fields Below
▪
Name: Content-Type
▪
Value: application/json
▪
Name : accept
▪
Value: application/json
•
Send Body : Enable
◦
Body Content Type: JSON
Specify Body: Using JSON
{
"model": "llama-3.1-sonar-small-128k-online",
"messages": [
{
"role": "system",
"content": "Be precise and concise."
},
{
"role": "user",
"content": "How many stars are there in our galaxy?"
}
],
"max_tokens": 1000,
"temperature": 0.2,
"top_p": 0.9,
"return_citations": true,
"search_domain_filter": [
"perplexity.ai"
],
"return_images": false,
"return_related_questions": false,
"search_recency_filter": "month",
"top_k": 0,
"stream": false,
"presence_penalty": 0,
"frequency_penalty": 1
}
Naver API
•
Calendar
◦
The API provided is only for creation and has low usability.
SOLAPI (KakaoTalk notification, text message) - WIP
Threads API
(Gen AI) Lumalabs API
(Gen AI) Elevenlabs API
