Apify Integration

Run Apify Actors and tasks, manage datasets and stores, and watch for Actor run completion events. Automate Apify deploys, issues, and webhook events across engineering workflows. When Watch Run Aborted fires, automatically update documentation, notify a team, or continue with Decode and Verify Data.

Explore Documentation

3-day trialCancel anytimeUp to 10 minutes quick set up

GDPR
Data Encryption
2FA
Local Data Region

Supported triggers and actions for Apify integration

Triggers can detect changes in Apify and run actions that can create, search or modify data inside Apify automatically [3] — exactly how you set them.

Watch Run AbortedTriggers when run Aborted.
Watch Run FailedTriggers when run Failed.
Watch Run SucceededTriggers when run Succeeded.
Watch Run Timed OutTriggers when run Timed Out.
Decode and Verify DataRetrieves decode and verify data.
Download Records (Batch Export)Retrieves download records (batch export).
Get ActorReturns actor.
Get Browser InfoReturns browser info.
Get Browser Info (POST Variant)Returns browser info (post variant).
Get BuildReturns build.
Get Build (Cross-Actor)Returns build (cross-actor).
Get Build LogReturns build log.
Get Build Log (Cross-Actor)Returns build log (cross-actor).
Get DatasetReturns dataset.
Get Dataset ItemsReturns dataset items.
Get Dataset StatisticsReturns dataset statistics.
Get Default BuildReturns default build.
Get Environment VariableReturns environment variable.
Get Environment VariablesReturns environment variables.
Get Key-Value StoreReturns key-value store.
Get Last Task RunReturns last task run.
Get List of ActorsReturns list of actors.
Get List of BuildsReturns list of builds.
Get List of DatasetsReturns list of datasets.
Get List of KeysReturns list of keys.
Get List of Key-Value StoresReturns list of key-value stores.
Get List of Request QueuesReturns list of request queues.
Get List of RunsReturns list of runs.
Get List of SchedulesReturns list of schedules.
Get List of Task RunsReturns list of task runs.
Get List of TasksReturns list of tasks.
Get List of Task WebhooksReturns list of webhooks for the given actor task.
Get List of VersionsReturns list of versions.
Get List of Webhook DispatchesReturns list of webhook dispatches.
Get List of WebhooksReturns list of webhooks.
Get Monthly Usage StatisticsReturns monthly usage statistics.
Get Private User DataReturns private user data.
Get Public Actors in StoreReturns public actors in store.
Get Public User DataReturns public user data.
Get Queue Head (Next Request)Returns queue head (next request).
Get Record by KeyReturns record by key.
Get RequestReturns request.
Get Request QueueReturns request queue.
Get Resource LimitsReturns resource limits.
Get RunReturns run.
Get Run (by ID, Cross-Actor)Returns run (by id, cross-actor).
Get Run's LogReturns run's log.
Get ScheduleReturns schedule.
Get Schedule LogReturns schedule log.
Get TaskReturns task.
Get Task InputReturns task input.
Get User Builds List (All Actors)Returns user builds list (all actors).
Get User Runs List (All Actors)Returns user runs list (all actors).
Get VersionReturns version.
Get WebhookReturns webhook.
Get Webhook DispatchReturns webhook dispatch.
Get Webhooks's Dispatch HistoryReturns webhooks's dispatch history.
List RequestsRetrieves a list of requests.
Run Task Synchronously and Get Dataset ItemsRetrieves run task synchronously and get dataset items.
Add Request to QueueCreates request to queue.
Batch Add RequestsPerforms batch add requests.
Build ActorBuilds actor.
Charge Events in RunCharges events in run.
Create ActorCreates actor.
Create DatasetCreates dataset.
Create Environment VariableCreates environment variable.
Create Key-Value StoreCreates key-value store.
Create Request QueueCreates request queue.
Create ScheduleCreates schedule.
Create TaskCreates task.
Create VersionCreates version.
Delete ActorDeletes actor.
Delete Build (Abort)Aborts build.
Delete Build (Abort, Cross-Actor)Aborts build (cross-actor).
Delete DatasetDeletes dataset.
Delete Environment VariableDeletes environment variable.
Delete Key-Value StoreDeletes key-value store.
Delete RecordDeletes record.
Delete RequestDeletes request.
Delete Request QueueDeletes request queue.
Delete Run (Abort)Aborts an Actor run (DELETE semantics).
Delete Run (Abort, Cross-Actor)Aborts run (cross-actor).
Delete ScheduleDeletes schedule.
Delete TaskDeletes task.
Delete VersionDeletes version.
Delete WebhookDeletes webhook.
Encode and Sign DataEncodes and sign data.
Lock Queue HeadLocks and returns the next request from a queue head.
Lock RequestLocks request.
Make an API CallPerforms an arbitrary authorized API call.
Reboot RunReboots run.
Reboot Run (Cross-Actor)Reboots run (cross-actor).
Remove Request LockUnlocks request.
Resurrect RunResurrects run.
Resurrect Run (Cross-Actor)Resurrects run (cross-actor).
Run ActorRuns actor.
Run TaskRuns task.
Run Task SynchronouslyRuns task synchronously.
Store Items in DatasetStores items in dataset.
Store/Update RecordStores /update record.
Store/Update Record (POST Alt)Stores /update record (post alt).
Test WebhookTests webhook.
Update ActorUpdates actor.
Update DatasetUpdates dataset.
Update Environment VariableUpdates environment variable.
Update Key-Value StoreUpdates key-value store.
Update RequestUpdates request.
Update Request Lock (Prolong)Prolongs request lock.
Update Request Locks (Unlock Multiple)Unlocks multiple requests.
Update Request QueueUpdates request queue.
Update Resource LimitsUpdates resource limits.
Update RunUpdates run.
Update Run (Metamorph)Metamorphs an Actor run into another Actor or task.
Update ScheduleUpdates schedule.
Update TaskUpdates task.
Update Task InputUpdates task input.
Update VersionUpdates version.
Update WebhookUpdates webhook.
Validate Actor Input SchemaValidates actor input schema.

How to integrate Apify in automation workflow?

3 simple steps to make your Apify connected with other apps in automation workflows on WEXTL. Up to 10 minutes integration set up.

STEP 1

Select Apify in workflow

Pick Apify app in the workflow builder [4] - just one click to select the app.

STEP 2

Connect Apify

When prompted, authorize access to Apify in WEXTL once. Apify credentials are encrypted and never shared with WEXTL. Authorization will be reused in any future API calls [3].

WEXTL wants to integrate with your Apify account. Approve?

STEP 3

Build a workflow

Build your workflow with Apify yourself or with WEXTL® AI Builder. Connect Apify to any available integrations [5], or use HTTP node to go beyond them.

Apify

How Apify connects and integrates with WEXTL

Save and approve your credentials once — WEXTL® stores authorization information encrypted and reuses the authentication whenever Apify app is called in workflows. That allows your developer tools automations to run without your attention, per defined schedule [7]. Explore documentation [6] for a detailed list of fields that Apify supports.

Full Apify API documentation

The following table illustrates what fields Apify integration require during authorization flow inside our workflow builder [4].

Demonstration of Apify connection step inside WEXTL Workflow Builder [4].

Field	Type	Help
API TokenRequired	password	API token from Apify Console → Integrations.

Connect Apify to popular apps on WEXTL

Enter a name of the other app you want to sync with Apify below. Click on selected app to explore integration options with Apify. If the app you search for is not available in WEXTL yet, you can use HTTP node [10] instead to integrate it directly.

Example automation with Apify integration

Select Watch Run Aborted trigger from Apify - this will be a starting point in your automation. Whenever event happens in Apify, workflow will start [7] from Watch Run Aborted node.

Search for Update Run, connect it as the next step of integration sequence. You can use filters between Watch Run Aborted and Update Run, so only important data pass from Watch Run Aborted to the next step. WEXTL gives you full control over the process of Apify automation. All parts of workflow are visible on the canvas [4].

Apify on WEXTL has 119 modules for creating developer tools automations. Explore Apify documentation for more.

Apify

Watch Run Aborted

CloudConvert

Performs action

CloudConvert

Triggers

Apify

Update Run

Demonstration of how visual Apify automation [6] looks in WEXTL.

Frequently asked questions

Common questions about automating Apify in your workflows.

Apify has 4 triggers, including "Watch Run Aborted", "Watch Run Failed", and "Watch Run Succeeded", and more. Triggers are start points of the workflow, and automations may start from them.

Integration has 115 actions, including "Decode and Verify Data", "Download Records (Batch Export)", and "Get Actor", and more. Refer to our Apify Documentation for detailed inputs and outputs.

No. Most automations are built visually on the canvas by picking triggers, actions, and mapping fields. You can add custom JavaScript with Functions when advanced logic is needed — but our customers do that in rare cases [4].

Yes. Connections are authenticated per account, credentials are encrypted at rest, and you can enforce approvals and team-level access controls on any automation.

The Apify integration on WEXTL runs directly on its vendor public API — every field name, authentication method, and rate limit is controlled by Apify official API and covered in documentation [3]. WEXTL handles the request signing and pagination for you.

Absolutely. Where Apify provides native webhooks, you can use instant triggers to eliminate polling delay. For custom webhooks, WEXTL offers Custom Webhook node, so you can start automation whenever Apify or any other service sends event to webhook URL.

WEXTL is an AI-first visual canvas. The platform allows you to describe automation in plain text — and AI will wire nodes for Apify inside the workflow builder [4]. You can also use built-in workflow nodes (AI Agent, Human in the Loop, Condition, Aggregate Results) in pair with Apify modules to craft complex integration flows with branches, filtering, and conditional logic. There are absolutely no limits of what you can build.

References

List of sources used to gather information about the Apify integration.

Apify integration source code, module specs and credentials implementation.
Internal Apify integration documentation, structured input and output parameters, scopes, and authentication methods.
Official Apify vendor API documentation — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
WEXTL® Visual Workflow Builder, anonymized data from our technical support team.
WEXTL® Apps Library
WEXTL® Apify App Documentation
WEXTL® Workflow Scheduler
WEXTL® HTTP node documentation

Apify Integration

Supported triggers and actions for Apify integration