Skip to main content

Integrations

Learn how to connect the Apify platform with your projects. You can use our tools in cloud services like Zapier, Make (formerly Integromat), Keboola, and more.

You can connect Apify with practically any cloud service or web app. They allow you to pass your actor run results to other services, process them, and receive notifications on important events.

What is software integration?​

Integration allows you to combine separate applications and take advantage of their combined capabilities. It allows you to combine the abilities of applications that are not directly linked. This helps to free your data from isolation and make it more productive.

How does integration work?​

Integrations use APIs and webhooks to transfer data between applications. Our RESTful API allows you to control the Apify platform from any application. You can create actors and tasks, start and stop your runs, and manage your data using only HTTP requests (or our handy API clients for JavaScript and for Python). Meanwhile, webhooks allow you to perform tasks like sending HTTP requests or notifications when certain events occur.

Get started​

Below are some examples of the kind of integrations you can set up with Apify.

Services you can connect to to extend the functionality of your actors:

Other platforms you can connect to Apify:

API token​

To access our API in your integrations, you will need to use your secret API token. You can find it on the Integrations page in the Apify Console. Give your token a reasonable description and never use one token for several services, much like you shouldn't use the same password for different accounts.

Integrations page in the Apify Console

When providing your API authentication token, we recommend using the request's Authorization header, rather than the URL. (More info).

IMPORTANT: Do not share the API token with untrusted parties, or use it directly from client-side code, unless you fully understand the consequences!

Note that some API endpoints, such as Get list of keys, do not require an authentication token because they contain a hard-to-guess identifier that effectively serves as an authentication key.