Skip to content

Commit

Permalink
feat(integrations): Update make.com documentation
Browse files Browse the repository at this point in the history
  • Loading branch information
drobnikj committed Jan 7, 2025
1 parent c90e74b commit c0f45c3
Showing 1 changed file with 61 additions and 25 deletions.
86 changes: 61 additions & 25 deletions sources/platform/integrations/workflows-and-notifications/make.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,68 +19,104 @@ To use the Apify integration on Make, you will need:
- An [Apify account](https://console.apify.com/).
- A Make account (and a [scenario](https://www.make.com/en/help/scenarios/creating-a-scenario)).

### Add the Apify module to your Make scenario
### Add the Apify module to scenario

Add the Apify module to your scenario. You can find this module by searching for "Apify" in the module search bar.

Next, select one of the available options under Triggers, Actions and Searches, then click on the Apify module to open its configuration window.

![Apify module](../images/apify-module.png)

### Create a connection to your Apify account
### Create a connection to Apify

In the Connection configuration window, you will need to provide your Apify API token.

![API token](../images/apify-token.png)

You can find the token in the Apify Console by navigating to **Settings > Integrations**.
You can find the token in the Apify Console by navigating to **[Settings > API & Integrations](https://console.apify.com/settings/integrations)**.

![Integrations token](../images/apify-integrations-token.png)

Finally, copy your API token to the Make module and save it to create a connection.

Congratulations! You have successfully connected the Apify app and can now use it in your scenarios.

## How to run an Actor or task and get the results
## Run an Actor or task with output

There are two ways to run an Actor or task and get it's data in Make.com, depends on your needs and Actor complexity.
There are two ways to run an Actor or task and get its data in Make.com, depending on your needs and Actor complexity.

* **Synchronous run using action modules**
* **Asynchronous run using triggers**
* **Synchronous run using action module**
* **Asynchronous run using trigger**

The difference between the two is that the synchronous run will wait for the Actor or task to finish and once finish gets it's output using "Get Dataset Items",
while the asynchronous run will run the Actor and then use trigger in another scenario to catch run finish and get it's output using "Get Dataset Items".
:::info
There is a hard timeout of 5 minutes for the synchronous run in Make.com. If the Actor or task run takes longer than 5 minutes, the data will not be returned completely.
If you expect that your Actor run will take longer than 5 minutes, use the asynchronous run using a trigger.
:::

### Synchronous run using action modules
The difference between the two is that the synchronous run will wait for the Actor or task to finish and once finished gets its output using "Get Dataset Items",
while the asynchronous run will catch the Actor run which will run from another scenario or elsewhere.

In this example we will show you how to run an Actor synchronously and get it's output into Google Sheets.
The same principle applies to other modules run a task action.
### Synchronous with action module

:::info
There is hard timeout 5 minutes for the synchronous run in Make.com, if the Actor run takes longer than 5 minutes, the data will not be returned completely.
If you expect that your Actor run will take longer than 5 minutes, use the asynchronous run using triggers.
:::
In this example, we will show you how to run an Actor synchronously and get its output into Google Sheets.
The same principle applies to another module that runs a task action.

#### Step 1: Add the Apify "Run an Actor" module

Before you start, you need to [connect the Apify account with Make.com](#create-a-connection-to-apify).
After you need to add Apify module called "Run an Actor" to your scenario and set it up.
In the example, we will use the "Google Maps Review Scraper" Actor. The most important part is to set the "Run synchronously" to "Yes", which will wait for the Actor to finish.

![img_1.png](img_1.png)

#### Step 2: Add the Apify "Get Dataset Items" module

In the next step, you need to add the "Get Dataset Items" module to your scenario, which will get the output from the Actor run.
In the "Dataset ID" field, you need to provide the default dataset ID from the Actor run, which you can find in variables from the previous module "Run an Actor".
If you do not see variables, you can run the scenario and check again.

![img_2.png](img_2.png)

#### Step 3: Add the Google Sheets "Create a Spreadsheet Rows" module

In the last step, you need to add the Google Sheets "Bulk Add Rows" module to your scenario, which will create new rows in the Google Sheets.
In the "Spreadsheet ID" field, you need to provide the Google Sheets ID, which you can find in the URL of the Google Sheets.
You need to set the columns range "A-Z" and add the date from the previous step "Get Dataset Items" to Rows values.

![img_3.png](img_3.png)

You are done, now once you run the scenario, it will run the Actor and get the output into Google Sheets.

Step 1: Add the Apify "Run an Actor" module
### Asynchronous with trigger

Step 2: Add the Apify "Get Dataset Items" module
In this example, we will show you how to run an Actor asynchronously and get it's output into Google Sheets.
Before you start, you need to decide from where you want to run the Actor run. You can run it manually Apify console, using a schedule, or with a different Make.com scenario.

Step 3: Add the Google Sheets "Create a Spreadsheet Rows" module
#### Step 1: Add the Apify "Watch Actor Runs" module

Before you start, you need to [connect the Apify account with Make.com](#create-a-connection-to-apify).
After you need to add Apify module called "Watch Actor Runs" where you set up webhook for Actor you want to catch the run.
In the example, we will use the "Google Maps Review Scraper" Actor.

![img.png](img.png)
![img_4.png](img_4.png)

#### Step 2: Add the Apify "Get Dataset Items" module

### Asynchronous run using triggers
In the next step, you need to add the "Get Dataset Items" module to your scenario, which will get the output from the Actor run.
In the "Dataset ID" field, you need to provide the default dataset ID from the Actor run, which you can find in variables from the previous module "Watch Actor Runs".

In this example we will show you how to run an Actor asynchronously and get it's output into Google Sheets.
![img_5.png](img_5.png)

Step 1: Add the Apify "Watch Actor Runs" module
#### Step 3: Add the Google Sheets "Create a Spreadsheet Rows" module

Step 2: Add the Apify "Get Dataset Items" module
In the last step, you need to add the Google Sheets "Bulk Add Rows" module to your scenario, which will create new rows in the Google Sheets.
In the "Spreadsheet ID" field, you need to provide the Google Sheets ID, which you can find in the URL of the Google Sheets.
You need to set columns range "A-Z" and add the date from the previous step "Get Dataset Items" to Row values.

Step 3: Add the Google Sheets "Create a Spreadsheet Rows" module
![img_6.png](img_6.png)

You are done, now once the Actor run is finished, it will get the output into Google Sheets.
You can run the Actor using the Apify console, schedule, or different Make.com scenarios.

## Available modules and triggers

Expand Down

0 comments on commit c0f45c3

Please sign in to comment.