Apify Integrations: Which One Should You Use?

Contains affiliate links. Disclosure.

Apify has three integration mechanisms, not a hundred: built-in connections you switch on from an Actor's Integrations tab, webhooks that POST to a URL you own, and the REST API that every third-party connector wraps. Choose by where the data has to land. The logo on the tile matters less than whether the tile is an Actor that bills you compute.

Apify's own directory at apify.com/integrations listed 101 named entries across 16 categories when we counted it on 9 September 2026. Its documentation site listed 25. Neither list tells you which one to wire up for a spreadsheet, a warehouse, a vector index, or an agent, and neither says what the thing costs once it runs every hour. That is what the table below does.

Which integration should I use for my destination?

Read the row for your destination. "Compute" means the step runs as a second Actor after your scrape finishes and bills compute units against your plan.

Where the data lands	Use this	How it runs	Cost beyond your scrape	Guide
A Google Sheet	lukaskrivka/google-sheets (Google Sheets Import & Export)	Actor run	Compute	Apify + Google Sheets
A file in Google Drive	Built-in Drive connection	Console Integrations tab	None	Apify + Google Drive
A Slack channel	Built-in Slack connection	Console Integrations tab	None	Apify run alerts in Slack
Your own HTTP endpoint	Webhook	Platform POST	None	Webhook actions
An Airtable base	Airtable Data Import integration (OAuth)	Actor run	Compute + your Airtable plan	Apify Airtable docs
A vector index	apify/pinecone-integration, apify/qdrant-integration, apify/milvus-integration	Actor run	Compute + your vector DB plan	Apify Pinecone docs
Snowflake	Apify's Snowflake Native App	Installed inside Snowflake	Snowflake credits	Apify Snowflake docs
A warehouse via ELT	Airbyte or Keboola connector	Their scheduler pulls your dataset	Their plan	Apify + Airbyte
An S3 bucket	The AWS SDK in your own code (see the warning below)	Your code	S3 storage and egress	Apify + AWS S3
A RAG pipeline	LangChain or LlamaIndex loaders	Your code	None	Apify + LangChain
An AI assistant or coding agent	Hosted MCP endpoint at https://mcp.apify.com	Remote MCP server	Compute for Actors the agent runs	Use MCP servers
HubSpot	Apify app from the HubSpot Marketplace	CRM card inside HubSpot	Your HubSpot plan	Apify HubSpot docs
A workflow spanning several apps	Make, n8n, or Zapier	Their connector calls the REST API	Their plan	Make · n8n · Zapier
Another Actor	Actor-to-Actor	Second Actor run	Compute	Actor integrations
A build or CI pipeline	GitHub	Build and run triggers	None	Apify + GitHub CI/CD

:::warning Two rows deserve a second look S3. The official apify/s3-uploader Actor still runs, but its last modification was 27 March 2025 and it had 55 total users and 18 in the previous 30 days when we checked the Apify API on 9 September 2026. Writing the upload yourself with the AWS SDK is the more maintainable choice.

Google Sheets. The community Actor lukaskrivka/google-sheets is healthy by the same measure: modified 29 July 2026, 4,669 total users, 764 in the previous 30 days. It is the working path even though Apify no longer lists Google Sheets as an integration at all. :::

Is a tile on the Integrations tab free?

No, and this is the cost trap in Console. Built-in connections such as Slack, Google Drive, and webhooks add no billing line. Several other tiles on the same tab are Actors: attaching Pinecone or Airtable starts a second Actor run once your scrape finishes, and that run bills compute units like any other. Apify charges $0.20 per compute unit on both the Free and Starter plans, verified on apify.com/pricing on 9 September 2026.

The mechanism you pick therefore changes the bill, not just the plumbing:

1. Built-in connection — no extra run, no extra compute.
2. Webhook — no extra run; your own server does the work.
3. Integration Actor — a second run, billed at your plan's CU rate.
4. Third-party connector (Make, Zapier, Airbyte, Keboola) — no extra Apify run, but their platform meters it on their plan.

If you are still sizing this up, how compute units are calculated has the arithmetic, and the Apify pricing breakdown covers what each plan includes.

Which of Apify's two official lists should I trust?

Both, for different things, because they disagree. We fetched each one on 9 September 2026.

	apify.com/integrations	docs.apify.com/integrations
Named entries	101 across 16 categories	25 across 5 groups
Purpose	Marketing catalogue, including partner-built tiles	Setup documentation
Only on this list	Slack, IFTTT, Kestra, Composio, Smithery, Clay, Payments (ap2, Skyfire, x402)	Snowflake, HubSpot
Practical use	Does the tile exist at all?	Can I actually configure it?

An entry on the marketing page is not a promise that a setup guide exists. Slack is the clean example: it appears under Collaboration on apify.com/integrations, and apify.com/integrations/slack returns a 404, while the real instructions sit at docs.apify.com/integrations/slack. Check the docs site before you commit an architecture to a tile you saw on the marketing page.

What changed recently, and what does it break?

Four changes that break links and assumptions written before this year. All checked 9 September 2026.

1. The docs moved. docs.apify.com/platform/integrations/* now redirects to docs.apify.com/integrations/*. Old links still resolve, with three exceptions that redirect to a 404: google-sheets, google-drive, and llamaindex. The live replacements are /integrations/drive and /integrations/llama-index. Google Sheets has no documentation page any more.
2. Google Sheets left both official lists. It is absent from the marketing directory and from the docs site. The Actor behind it is alive and actively used, so treat this as a documentation gap rather than a dead integration, and pin the Actor rather than a docs URL.
3. MCP is an endpoint, not an Actor. Apify's MCP server is hosted at https://mcp.apify.com over streamable HTTP, with OAuth or a bearer token. Four read-only tools (search-actors, fetch-actor-details, search-apify-docs, fetch-apify-docs) work anonymously; running an Actor or reading storage needs auth. The legacy SSE transport was removed on 1 April 2026. Source: Apify MCP docs.
4. The n8n node is no longer a community node. n8n.io describes it as "built and maintained by our partners at Apify and verified by n8n."

Make, n8n, or Zapier: which one?

All three call the same primitives underneath: authenticate with a token, start a run, read the dataset. The choice is about hosting and catalogue, not capability.

	What ships	Status	Pick it when
Make	2 triggers, 4 actions, 1 search: Watch Actor Runs, Watch Task Runs, Run an Actor, Run a Task, Make an API Call, Scrape Single URL, Get Dataset Items	Verified app, listed as maintained by the vendor	You want visual branching and rich JSON mapping
Zapier	2 triggers, 8 actions, including Fetch Dataset Items, Set Key-Value Store Record, Find Last Actor Run	Listed by Zapier with an MCP endpoint; the page does not state who maintains it	Your destination is one of the 10,000+ apps Zapier lists
n8n	Verified Apify node covering Actor, Actor Task, Actor Run, Dataset, and Key-Value Store resources (Run an Actor, Run an Actor and Get Dataset, Scrape Single URL, Get Last Run), plus 182 workflow examples listed on the integration page	Built by Apify, verified by n8n	You self-host and want Git-backed workflows

Module counts read from make.com/en/integrations/apify, zapier.com/apps/apify/integrations, and n8n.io/integrations/apify on 9 September 2026. Zapier states it connects "10071+ apps" on zapier.com/apps. n8n publishes no aggregate template total; 182 is our own count of the workflow examples rendered under "Popular ways to use the Apify integration" on 9 September 2026, and that list is complete rather than paginated.

Where Zapier genuinely wins: catalogue size. If the system you have to reach is on Zapier's list and nowhere else, that settles it, and nothing on this page argues otherwise. Where n8n genuinely wins: a self-hosted n8n has no per-operation meter. Make and Zapier both bill by operation on their own plans, so a scrape that fires hourly and fans out to twenty rows will cost you on their side of the wire, not Apify's. Price that before you build it.

Our deeper walkthroughs: Apify with Make, Apify with n8n, Apify with Zapier.

What do Apify webhooks actually guarantee?

A webhook is a POST to a URL you own. Your endpoint has to return a 2XX status within 2 minutes. If it does not, Apify retries up to 11 times with exponential backoff, the first retry after roughly a minute and the eleventh after roughly 32 hours, then stops trying. Source: webhook actions, checked 9 September 2026.

Events you can subscribe to:

Run events	Build events
ACTOR.RUN.CREATED, ACTOR.RUN.SUCCEEDED, ACTOR.RUN.FAILED, ACTOR.RUN.ABORTED, ACTOR.RUN.TIMED_OUT, ACTOR.RUN.RESURRECTED	ACTOR.BUILD.CREATED, ACTOR.BUILD.SUCCEEDED, ACTOR.BUILD.FAILED, ACTOR.BUILD.ABORTED, ACTOR.BUILD.TIMED_OUT

The default payload carries userId, createdAt, eventType, eventData, and resource. eventData gives you actorId and actorRunId, plus actorTaskId when a task started the run. resource is the full run record, which is where defaultDatasetId, defaultKeyValueStoreId, and defaultRequestQueueId live, per the run object in API v2. Read the dataset id from there instead of guessing it.

Two ceilings worth knowing before you design around webhooks: 100 webhooks per user and 100 schedules per user, both from Apify's limits page.

How many runs can fire at once?

Here Apify's own two pages disagree, and we are not going to pick a winner for you.

Plan	apify.com/pricing says	docs.apify.com/account/limits says
Free	5 concurrent runs	25 concurrent runs
Starter	32	32
Scale	128	128
Business	256	256

Both fetched 9 September 2026. The paid tiers agree; only the Free row conflicts. Safe assumption: design for 5 on the Free plan. If your automation platform fans out and starts more runs than your ceiling allows, the extra runs queue rather than fail, which shows up as a stalled Zap or scenario rather than an error you can read. Serialise the fan-out, or move up a plan.

Moving up costs less than most people assume. Starter is $19/month ^{subject to change · verified 2026-09-09} billed monthly, or $17 a month on annual billing, and it includes $19 of platform usage. The subscription is a usage credit, not an access fee, so on a light integration workload you are mostly buying the higher concurrency ceiling. The Free plan includes $5 of usage a month.

What if none of the connectors fit?

Every integration above bottoms out here. Apify API v2 runs Actors with JSON input, pages through dataset items, and manages key-value stores, request queues, and schedules.

Language	Package	Install	Latest on 9 Sep 2026
JavaScript / TypeScript	apify-client	npm install apify-client	2.25.0
Python	apify-client	pip install apify-client	3.2.0

Both clients handle retries and pagination for you. Reach for them when your "integration" is a service you host. The Apify API tutorial walks through a first run and dataset read, and the storage guide explains what a dataset is before you start paginating one.

:::tip Test the whole chain for nothing The Free plan includes $5 of platform usage a month, which is enough to run a small scrape and its delivery step end to end before you commit to a destination. Create an Apify account, run one Actor, then attach exactly one integration and watch what it adds to your usage. :::

Frequently Asked Questions

Three ways. Switch on a built-in connection from the Actor's Integrations tab in Console, add a webhook that POSTs to a URL you own, or call the REST API from your own code. Every third-party connector, including Make, n8n, and Zapier, wraps that same REST API.

Not as a listed integration. As of 9 September 2026 Google Sheets appears on neither apify.com/integrations nor docs.apify.com/integrations, and the old docs URL redirects to a 404. The community Actor lukaskrivka/google-sheets still works and is actively used: 4,669 total users, 764 in the previous 30 days, last modified 29 July 2026.

It depends on the mechanism. Built-in connections and webhooks add nothing. Integration Actors such as Pinecone or Airtable start a second Actor run and bill compute units at your plan's rate, $0.20 per CU on Free and Starter as of 9 September 2026.

Up to 11 times with exponential backoff, the first retry after roughly one minute and the eleventh after roughly 32 hours, after which it stops. Your endpoint must return a 2XX status within a 2-minute timeout, so acknowledge first and do the slow work afterwards.

Apify's own pages disagree. apify.com/pricing says 5 and docs.apify.com/account/limits says 25, both checked 9 September 2026. Design for 5 until Apify reconciles the two. Runs above the ceiling queue instead of failing, which looks like a stalled automation rather than an error.

No. It is a hosted endpoint at https://mcp.apify.com using streamable HTTP, authenticated with OAuth or a bearer token. Four read-only tools work anonymously; running an Actor or reading storage requires auth. The legacy SSE transport was removed on 1 April 2026.

Make for visual branching and JSON mapping, Zapier when your destination is only in its 10,000+ app catalogue, n8n when you self-host and want Git-backed workflows. All three call the same run-and-read-dataset primitives, so the decision is hosting and catalogue, not capability.

Write it yourself with the AWS SDK. The official apify/s3-uploader Actor still runs, but it was last modified on 27 March 2025 and had 55 total users when checked on 9 September 2026. For a warehouse rather than a bucket, use the Airbyte or Keboola connector instead.

Airbyte and Keboola both document an Apify dataset source, and their scheduler pulls from your dataset rather than Apify pushing to them. Snowflake users have a third option: Apify publishes a Snowflake Native App that runs Actors and imports results from inside the Snowflake UI.

They serve different purposes. On 9 September 2026 the marketing directory listed 101 named entries across 16 categories and the docs site listed 25. The marketing page tells you a tile exists; the docs site tells you whether a setup guide exists. Check the docs site before you design around a tile.