Integration Templates

ApifyForge Integration Template Generator

ApifyForge Integration Template Generator is a free tool that creates ready-to-import workflow templates for n8n (6-node JSON workflow) and Make.com (4-module setup instructions) that connect to any of 320+ Apify actors. Each template uses 3 endpoints from the Apify REST API v2: start a run, poll status, and fetch dataset results as JSON. Templates support 3 extension patterns — Google Sheets export, Slack alerts, and Apify webhook triggers. Setup takes under 1 minute for n8n (direct JSON import) and 5-10 minutes for Make.com (manual module configuration).

Last updated March 2026. Templates follow Apify REST API v2 specification.

Generate a template

1. Select an actor

2. Choose platform

Select an actor above to generate a workflow template

n8n vs Make.com vs Direct API for Apify Integrations

All three approaches connect to Apify actors via the REST API v2. ApifyForge generates templates for n8n and Make.com — choose based on your deployment preference, budget, and technical level.

Feature	n8n	Make.com	Direct API (cURL/SDK)
ApifyForge template format	JSON workflow file (6 nodes, direct import via paste or file upload)	Text-based setup instructions (4 HTTP modules, 5-10 min manual config)	N/A — write your own HTTP calls using 3 API endpoints
Setup time	Under 1 minute (import JSON)	5-10 minutes (manual config)	15-60 minutes (code + error handling)
Self-hosted option	Yes (open source, MIT license, Docker/npm)	No (cloud only, EU hosted)	Yes (any server, any language)
Platform cost	Free self-hosted; cloud from $20/mo (2,500 executions)	From $9/mo (10,000 operations)	Free (server/hosting costs only)
Webhook support	Built-in Webhook node (auto-generates URL, handles POST payloads)	Built-in Webhook module (custom URL, JSON parsing)	Any HTTP server endpoint (Express, Flask, Lambda, Workers)
Google Sheets export	Native Google Sheets node with OAuth2 auth and append mode	Native Google Sheets module with row-level mapping	Google Sheets API v4 (requires OAuth2 setup and code)
Slack notifications	Native Slack node with channel picker and message formatting	Native Slack module with Block Kit support	Slack Incoming Webhook URL (single POST request)
Apify connector	Community Apify node available; ApifyForge templates use HTTP Request nodes for reliability	No native connector — HTTP modules with pre-configured endpoints	Official JS/Python client libraries with type safety
Error handling	Error workflow + retry nodes (configurable delay, max retries)	Error handler + router modules (break/resume/commit)	Custom try/catch with exponential backoff (full control)
Technical skill required	Low (visual workflow editor)	Low (visual scenario builder)	High (JavaScript/Python/cURL proficiency)

Common Integration Patterns

Extend your ApifyForge-generated workflow with these 3 patterns. Each works with both n8n and Make.com and follows the Apify integrations documentation.

Google Sheets Export

Both

After fetching dataset items, append each row to a Google Sheet. Use the Google Sheets module (Make.com) or Google Sheets node (n8n) to map fields to columns.

1Connect the output of 'Get Dataset Items' to a Google Sheets node
2Authenticate with your Google account
3Select the target spreadsheet and sheet
4Map actor output fields to columns (e.g., name, email, url)
5Enable 'Append' mode so new runs add rows instead of overwriting

Slack Notification on Completion

Both

Send a Slack message when the actor run finishes. Include the run status, item count, and a direct link to the dataset in Apify Console.

1Add a Slack node/module after the status check resolves to SUCCEEDED
2Authenticate with your Slack workspace
3Select the target channel
4Compose a message template with run metadata:
5 - Actor name, run ID, status, duration
6 - Item count from the dataset
7 - Link: https://console.apify.com/actors/runs/{runId}
8Add a separate error path for FAILED runs with alert formatting

Webhook Trigger

Both

Instead of polling, use Apify webhooks to trigger your workflow when a run finishes. This is more efficient and near-instant.

1In your automation platform, create a Webhook trigger node/module
2Copy the webhook URL it generates
3In Apify Console, go to your actor > Integrations > Webhooks
4Add a webhook with event type: ACTOR.RUN.SUCCEEDED
5Paste the webhook URL as the target
6The webhook payload includes runId, actorId, datasetId — use these to fetch results
7Remove the polling loop from your workflow since webhooks replace it

How ApifyForge Integration Templates Work

Every ApifyForge template follows the same 4-step pattern using the Apify REST API v2. The n8n template uses 6 nodes; the Make.com template uses 4 HTTP modules.

Start a Run

POST to the Apify REST API v2 with your actor ID and input parameters. The API returns a run object containing the run ID.

Wait

Actors take 10 seconds to 30+ minutes depending on scope. Wait 30 seconds before the first poll.

Poll Status

GET the run status. If still RUNNING, wait 10 seconds and retry. When SUCCEEDED, proceed to fetch results.

Fetch Results

GET the dataset items as JSON. Pipe them into Google Sheets, databases, Slack, CRMs, or your own API endpoint.

Frequently Asked Questions

How do I connect an Apify actor to n8n?

ApifyForge generates a ready-to-import n8n JSON workflow for any of 320+ Apify actors. The workflow uses 6 nodes: HTTP Request to start the run via the Apify REST API v2, Wait (30 seconds), Check Status, If condition, Retry Wait, and Get Dataset Items. Import the JSON file directly into n8n — no manual node configuration required.

How do I connect an Apify actor to Make.com?

ApifyForge generates step-by-step Make.com setup instructions for any actor. The workflow uses 4 HTTP modules: Start Run (POST), Sleep (30 seconds), Check Status (GET with repeater), and Get Dataset Items (GET). Each module includes the exact URL, headers, and body to configure. The Apify REST API v2 documentation (docs.apify.com/api/v2) covers all available endpoints.

What is the difference between polling and webhooks for Apify actors?

Polling checks the run status on a fixed interval (every 10 seconds), which adds latency and uses API calls. Apify webhooks (docs.apify.com/platform/integrations/webhooks) push a notification to your endpoint the instant a run finishes, reducing average latency from 5-15 seconds to under 1 second. Webhooks are supported by both n8n and Make.com via their webhook trigger nodes.

Can I export Apify actor results to Google Sheets automatically?

Yes. After the Get Dataset Items step in your workflow, connect a Google Sheets node (n8n) or Google Sheets module (Make.com). Map the actor output fields to spreadsheet columns and enable append mode. ApifyForge templates include the dataset items endpoint, which returns JSON that both platforms parse automatically.

How much does it cost to run an Apify actor integration?

Apify actors use pay-per-event (PPE) pricing, typically $0.05 to $5.00 per run depending on the actor. The Apify REST API itself has no additional per-call fees — you pay only for actor compute time and events. n8n (self-hosted) is free; n8n Cloud starts at $20/month. Make.com starts at $9/month for 10,000 operations. ApifyForge generates templates at no cost.

Do ApifyForge integration templates work with any Apify actor?

Yes. ApifyForge generates templates for all 320+ actors in its catalog. Every template uses the same Apify REST API v2 endpoints — the only variable is the actor ID and input schema. Templates work with actors built by any developer on the Apify Store, not just ApifyForge actors.

How do I get Slack alerts when an Apify actor fails?

Two options: (1) Add a Slack node to your n8n or Make.com workflow that fires on the FAILED status branch. (2) Use ApifyForge Monitor (apifyforge.com/monitor), which provides real-time email and Slack failure alerts for up to 3 actors on the free plan without requiring any workflow automation setup.

What Apify API endpoints do the templates use?

ApifyForge templates use 3 Apify REST API v2 endpoints: POST /v2/acts/{actorId}/runs to start a run, GET /v2/actor-runs/{runId} to check status, and GET /v2/actor-runs/{runId}/dataset/items to fetch results. All endpoints require an Apify API token, available from Console > Settings > Integrations. Full API reference: docs.apify.com/api/v2.

Alternatives to ApifyForge Integration Templates

ApifyForge is one of several ways to connect Apify actors to automation platforms. The right choice depends on your technical level and how many actors you integrate.

Apify Native Integrations

Apify offers built-in integrations for Slack, Google Sheets, Zapier, Make, and webhooks directly from the Apify Console. These require no code and work with any actor on the platform, not just ApifyForge catalog actors.

Best for: users who want zero-code setup for a single actor with standard output destinations.

Zapier + Apify

Zapier has an official Apify integration that triggers Zaps when actor runs complete. It supports 2,000+ destination apps. Pricing starts at $19.99/month for 750 tasks.

Best for: non-technical users who need Apify connected to CRMs, email marketing, or project management tools.

Direct Apify REST API

The Apify REST API v2 provides full programmatic control over actor runs, datasets, key-value stores, and request queues. Any language or platform that can make HTTP requests can integrate directly.

Best for: developers building custom pipelines who need full control over retry logic, pagination, and error handling.

Apify JavaScript/Python Client

Apify provides official JavaScript and Python client libraries with type-safe methods for all API operations. These handle authentication, retries, and pagination automatically.

Best for: developers building production applications in Node.js or Python who prefer typed SDKs over raw HTTP.

Manual n8n / Make.com Configuration

You can build the same 4-step workflow (start run, wait, poll status, fetch results) manually in n8n or Make.com using their HTTP request nodes. ApifyForge templates automate this setup, but the underlying pattern is the same.

Best for: users who already have complex n8n or Make.com workflows and prefer to configure each node manually.

Each approach has trade-offs in setup time, flexibility, and maintenance. ApifyForge templates reduce initial setup from 15-30 minutes to under 1 minute by pre-configuring the API endpoints and node connections, but manual configuration provides more control over retry logic and error handling.

Limitations

ApifyForge Integration Templates have the following constraints.

•Generic input schemas — Templates use placeholder input fields (startUrls, maxItems). Each actor has its own input schema, so you need to replace the placeholder body with the actor's actual required fields.
•No error recovery logic — Generated templates poll until SUCCEEDED or FAILED but do not include automatic retry-on-failure logic. For production workflows, add error handling and retry nodes manually.
•n8n and Make.com only — Templates are generated for n8n and Make.com. Other platforms (Zapier, Tray.io, Pipedream, Activepieces) are not currently supported, though the same Apify REST API v2 endpoints work on any platform that supports HTTP requests.
•Fixed polling interval — Templates use a 30-second initial wait and 10-second retry interval. For actors that run for 10+ minutes, this results in unnecessary API calls. Use Apify webhooks instead for long-running actors.
•No Make.com direct import — Make.com does not support JSON workflow import the way n8n does. Make.com templates are text-based setup instructions that require manual module configuration (typically 5-10 minutes).

When to Use ApifyForge Integration Templates

ApifyForge integration templates are most useful when:

•You need to connect an Apify actor to n8n or Make.com and want a working template in under 1 minute instead of 15-30 minutes of manual node configuration
•You are testing multiple Apify actors and need quick workflow scaffolding for each one before committing to a production setup
•You are not familiar with the Apify REST API v2 endpoint structure and want pre-configured URLs, headers, and body parameters
•You want to extend a basic Apify workflow with Google Sheets export, Slack notifications, or webhook triggers and need step-by-step guidance for each pattern
•You are evaluating n8n vs Make.com for Apify automation and want to compare the workflow structure side-by-side before choosing a platform

Need help building a custom Apify integration?

Request a custom actor Browse Apify integration guides