You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: sources/platform/integrations/workflows-and-notifications/n8n.md
+37-29Lines changed: 37 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,10 @@
1
1
---
2
-
3
2
title: n8n integration
4
3
description: Connect Apify with n8n to automate workflows by running Actors, extracting data, and responding to Actor or task events.
5
4
sidebar_label: n8n
6
5
sidebar_position: 7
7
6
slug: /integrations/n8n
8
-
-----------------------
7
+
---
9
8
10
9
**Connect Apify with n8n to automate workflows by running Actors, extracting structured data, and responding to Actor or task events.**
11
10
@@ -47,26 +46,29 @@ If you’re using n8n Cloud, installing community nodes is even simpler:
47
46
48
47
:::note
49
48
50
-
On n8n cloud users can choose not to show verified community nodes. Instance owners can toggle this in the Cloud Admin Panel. To install the Apify node, make sure the installation of verified community nodes is enabled.
49
+
On n8n cloud users can choose not to show verified community nodes. Instance owners can toggle this in the Cloud Admin Panel. To install the Apify node, make sure the installation of verified community nodes is enabled.
51
50
52
51
:::
53
52
54
53
## Authentication
55
-
The Apify node supports two authentication methods:
56
54
57
-
1. API Key (cloud & self-hosted instance):
58
-
- In the n8n Editor UI, click on **Create Credential**
59
-
- Search for Apify API and click **Continue**
60
-
- Enter your Apify API token. You can find the API token in the [console](https://console.apify.com/settings/integrations)
61
-
- Click **Save**
55
+
The Apify node supports two authentication methods:
56
+
57
+
### API Key (cloud & self-hosted instance)
58
+
59
+
1. In the n8n Editor UI, click on **Create Credential**
60
+
2. Search for Apify API and click **Continue**
61
+
3. Enter your Apify API token. You can find the API token in the [console](https://console.apify.com/settings/integrations)
62
+
4. Click **Save**
62
63
63
64

64
65
65
-
2. OAuth2 (cloud instance only):
66
-
- In n8n Cloud, click on **Create Credential**
67
-
- Search for Apify OAuth2 API and click **Continue**
68
-
- Click **Connect my account** and authorize with your Apify account
69
-
- n8n will retrieve and store OAuth2 tokens automatically
66
+
### OAuth2 (cloud instance only)
67
+
68
+
1. In n8n Cloud, click on **Create Credential**
69
+
2. Search for Apify OAuth2 API and click **Continue**
70
+
3. Click **Connect my account** and authorize with your Apify account
71
+
4. n8n will retrieve and store OAuth2 tokens automatically
70
72
71
73

72
74
@@ -87,37 +89,43 @@ If you’re using n8n Cloud, installing community nodes is even simpler:
2. Click **Add Node**, search for **Apify**, and select it
92
95
3. Select **On new Apify Event** trigger
93
-
4. Configure it:
94
-
-**Actor or Actor task**: select the Actor or task to listen for terminal events
95
-
-**Event Type**: the status of the Actor or task run that should trigger the workflow
96
-
5. Add subsequent nodes (e.g., HTTP Request, Google Sheets) to process or store the output
97
-
6. Save and execute the workflow
96
+
4. Configure it:
97
+
98
+
***Actor or Actor task**: select the Actor or task to listen for terminal events
99
+
***Event Type**: the status of the Actor or task run that should trigger the workflow
100
+
101
+
1. Add subsequent nodes (e.g., HTTP Request, Google Sheets) to process or store the output
102
+
2. Save and execute the workflow
98
103
99
104

100
105
101
106
## Use Apify node as an action
107
+
102
108
1. Create a new workflow
103
109
2. Click **Add Node**, search for **Apify**, and select it
104
110
3. Select any operation. In this example we will use **Run Actor**
105
-
4. Configure it:
106
-
-**Custom input**: JSON input for the Actor run, which you can find on the Actor input page in Apify Console. See [Inputs](/platform/actors/running/input-and-output#input) for more information. If empty, the run uses the input specified in the default run configuration
107
-
-**Timeout**: Timeout for the Actor run in seconds. Zero value means there is no timeout
108
-
-**Memory**: Amount of memory allocated for the Actor run, in megabytes
109
-
-**Build Tag**: Specifies the Actor build tag to run. By default, the run uses the build specified in the default run configuration for the Actor (typically `latest`)
110
-
-**Wait for finish**: Whether to wait for the run to finish before continuing. If true, the node will wait for the run to complete (successfully or not) before moving to the next node
111
+
4. Configure it:
112
+
113
+
***Custom input**: JSON input for the Actor run, which you can find on the Actor input page in Apify Console. See [Inputs](/platform/actors/running/input-and-output#input) for more information. If empty, the run uses the input specified in the default run configuration
114
+
***Timeout**: Timeout for the Actor run in seconds. Zero value means there is no timeout
115
+
***Memory**: Amount of memory allocated for the Actor run, in megabytes
116
+
***Build Tag**: Specifies the Actor build tag to run. By default, the run uses the build specified in the default run configuration for the Actor (typically `latest`)
117
+
***Wait for finish**: Whether to wait for the run to finish before continuing. If true, the node will wait for the run to complete (successfully or not) before moving to the next node
0 commit comments