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/make.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ Finally, copy your API token to the Make module and save it to create a connecti
41
41
42
42
Congratulations! You have successfully connected the Apify app and can now use it in your scenarios.
43
43
44
-
## Run an Actor or Task with Output
44
+
## Run an Actor or task with Output
45
45
46
46
We have two methods to run an Actor or task and retrieve its data in Make.com, depending on your needs and the complexity of the Actor:
47
47
@@ -53,7 +53,7 @@ Make.com imposes a hard timeout of 5 minutes for synchronous runs. If the Actor
53
53
If you anticipate that the Actor run will exceed 5 minutes, use the asynchronous method with a trigger module instead.
54
54
:::
55
55
56
-
The primary difference between the two methods is that the synchronous run waits for the Actor or Task to finish and retrieves its output using the "Get Dataset Items" module. By contrast, the asynchronous run watches for the run of an Actor or task (which could have been triggered from another scenario, manually from Apify console or elsewhere) and gets its output once it finishes.
56
+
The primary difference between the two methods is that the synchronous run waits for the Actor or task to finish and retrieves its output using the "Get Dataset Items" module. By contrast, the asynchronous run watches for the run of an Actor or task (which could have been triggered from another scenario, manually from Apify console or elsewhere) and gets its output once it finishes.
57
57
58
58
### Synchronous run using the action module
59
59
@@ -126,16 +126,16 @@ You can initiate the Actor run via the Apify console, a scheduler, or from anoth
126
126
127
127
### Triggers
128
128
129
-
- Watch Actor Runs: Triggers when a selected Actor run is finished.
130
-
- Watch Task Runs: Triggers when a selected task run is finished.
129
+
-**Watch Actor Runs:** Triggers when a selected Actor run is finished.
130
+
-**Watch Task Runs:** Triggers when a selected task run is finished.
131
131
132
132
### Actions
133
133
134
-
- Run a task: Runs a selected Actor task.
135
-
- Run an Actor: Runs a selected Actor.
136
-
- Scrape Single URL: Runs a scraper for the website and returns its content as text, markdown and HTML.
137
-
- Make an API Call: Makes an arbitrary authorized API call.
134
+
-**Run a Task:** Runs a selected Actor task.
135
+
-**Run an Actor:** Runs a selected Actor.
136
+
-**Scrape Single URL:** Runs a scraper for the website and returns its content as text, markdown and HTML.
137
+
-**Make an API Call:** Makes an arbitrary authorized API call.
138
138
139
139
### Searches
140
140
141
-
- Get Dataset Items: Retrieves items from a [dataset](/platform/storage/dataset).
141
+
-**Get Dataset Items:** Retrieves items from a [dataset](/platform/storage/dataset).
0 commit comments