Apify

Apify + Konnectify

Apify Integration with Konnectify

Connect Apify to Konnectify to automate web scraping, browser automation, Actors, Actor tasks, request queues, schedules, builds, runs, and webhook-driven workflows.

Actor Runs Actor Builds Tasks Request Queues Requests Schedules Actors Versions Environment Variables Builds Runs 11 Triggers 63 Actions

ON THIS PAGE

→ What is Apify? → API & authentication → How to connect → Triggers (11) → Actions (63) → Popular automations → FAQ

What is Apify?

Apify is a cloud platform for web scraping, data extraction, browser automation, and serverless jobs called Actors. Teams use Apify to run crawlers, manage datasets and request queues, schedule automation jobs, and react to Actor run or build events.

By integrating Apify with Konnectify, you can trigger workflows when Actors run or builds complete, start Actors from other apps, manage tasks and schedules, and route extracted data into your business systems automatically.

New to Apify?

Create an Apify account to build, run, and monitor Actors for scraping and automation.

Visit Apify →

New to Konnectify?

Build no-code workflows that connect Apify with CRMs, databases, spreadsheets, support tools, and more.

What you can automate

• Start Actor runs asynchronously or synchronously

• Trigger workflows from Actor run and build webhooks

• Create and update Actor tasks

• Manage request queues, requests, and locks

• Create schedules and review schedule logs

• Manage Actors, versions, env vars, builds, and run metadata

API & Authentication

Authentication method: API Token authentication

This connector uses an Apify API token. In Konnectify, enter your token in the API Token field when creating the connection. API tokens are typically generated and managed from your Apify account settings.

Run, inspect, and manage Actors and Actor tasks.
Work with Actor builds, versions, OpenAPI definitions, and environment variables.
List and manage Actor runs, request queues, queue requests, locks, and schedules.
Receive webhook events for Actor run and Actor build lifecycle changes.

Important: Available Apify API features, concurrency, compute units, storage limits, and rate limits can vary by Apify plan, account permissions, and workspace configuration. If a workflow fails with permission or quota errors, check your Apify token permissions and plan limits.

For endpoint-level details, see the official Apify API documentation.

How to connect Apify to Konnectify

Prerequisites

An active Apify account.
An Apify API token with access to the Actors, tasks, queues, schedules, builds, and runs you want to automate.
A Konnectify account with permission to create or edit workflows.
For webhook triggers, your Apify account must be able to create webhooks for the selected Actor or build events.

Add Apify to a Workflow

Open Konnectify and create a new workflow or edit an existing workflow.
Choose Apify as the trigger app or action app.

Authorize via API Token authentication

Select Add new connection.
Paste your Apify API token into the API Token field.
Save the connection.

Configure the Trigger or Action

Choose the Apify event or operation you want to use.
Map Actor IDs, task IDs, queue IDs, run IDs, request IDs, input JSON, or filters as required by the selected step.

For run and build operations, verify that IDs and default storages are correct before activating the workflow. Incorrect IDs can start the wrong Actor, update the wrong task, or delete resources.

Test the Workflow

Run a test in Konnectify.
Confirm that Apify returns the expected run, build, task, queue, or schedule response.

Activate the Workflow

Turn on the workflow when tests pass.
Monitor early executions to confirm webhook delivery, run timing, and API usage.

Triggers 11

Apify provides 11 webhook triggers in Konnectify. These triggers fire per event when Actor runs or Actor builds are created or reach specific lifecycle states.

Actor Runs 6 triggers

Actor Run Created

Triggers when a new Actor run is created.

Actor Run Succeeded

Triggers when an Actor run succeeds.

Actor Run Failed

Triggers when an Actor run fails.

Actor Run Aborted

Triggers when an Actor run is aborted.

Actor Run Timed Out

Triggers when an Actor run times out.

Actor Run Resurrected

Triggers when an Actor run is resurrected.

Actor Builds 5 triggers

Actor Build Created

Triggers when a new Actor build is created.

Actor Build Succeeded

Triggers when an Actor build succeeds.

Actor Build Failed

Triggers when an Actor build fails.

Actor Build Aborted

Triggers when an Actor build is aborted.

Actor Build Timed Out

Triggers when an Actor build times out.

Actions 63

Use Apify actions to create, retrieve, update, delete, start, abort, validate, list, and inspect Apify resources directly from Konnectify workflows.

Actor Tasks5 actions

Get list of tasks

List all Actor tasks

Create task

Create a new Actor task

Get task

Get a specific Actor task

Update task

Update task configuration

Delete task

Delete an Actor task

Request Queues5 actions

Get list of queues

List all request queues

Create queue

Create a new request queue

Get queue

Get request queue metadata

Update queue

Update queue metadata

Delete queue

Delete a request queue

Queue Requests & Locks10 actions

List requests

List requests in an Apify request queue.

Add request

Add a single request to the queue

Get request

Get a specific request

Update request

Update a specific request

Delete request

Delete a specific request

Get queue head

Get the next unprocessed request from queue head

Get head and lock

Get and lock the queue head for exclusive processing

Prolong request lock

Extend the lock duration on a request

Delete request lock

Release the lock on a request

Unlock requests

Unlock multiple locked requests

Schedules6 actions

Get list of schedules

List all schedules

Create schedule

Create a new schedule

Get schedule

Get a specific schedule

Update schedule

Update a schedule

Delete schedule

Delete a schedule

Get schedule log

Retrieve the execution log for a schedule

Actors6 actions

Get list of Actors

List all Actors owned by user

Create Actor [Beta]

Create a new Actor

Get Actor

Retrieve a specific Actor

Update Actor [Beta]

Update Actor settings

Delete Actor

Delete an Actor

Validate Actor input

Validate Actor input against its schema

Actor Versions6 actions

Get list of versions

List versions of an Actor

Create version [Beta]

Create a new Actor version

Get version

Retrieve a specific version

Update version [Beta]

Update a version

Update version (POST)

Update version via POST override

Delete version

Delete a version

Environment Variables5 actions

Get list of env vars

List env vars for a version

Create env var

Create a new env var

Get env var

Retrieve a specific env var

Update env var

Update an env var

Delete env var

Delete an env var

Builds & Build Logs12 actions

Get list of builds

List builds for an Actor

Build Actor

Trigger a new build

Get default build

Get the default build of an Actor

Get Actor OpenAPI

Get OpenAPI definition for Actor default build

Get build

Get a specific build

Abort build

Abort a running build

Get user builds list

List all builds for the current user

Get build (global)

Get build by global build ID

Delete build

Delete a build

Abort build (global)

Abort build by global build ID

Get build log

Retrieve the log of a build

Get build OpenAPI

Get OpenAPI definition for a specific build

Runs8 actions

Get list of runs

List Actor runs using offset, limit, sorting, status, and started date filters.

Run Actor (async)

Start an asynchronous Actor run

Run sync + get dataset items (with input)

Run Actor synchronously and return dataset items directly

Run sync + get dataset items (no input)

Runs an Apify Actor synchronously without input and returns dataset items.

Get last run

Get the most recent run of an Actor

Get run

Get a specific Actor run

Get task runs

List runs for a task

Get user runs list

List all runs for the authenticated user

Popular automations

Here are common Apify workflow patterns you can build in Konnectify.

Start downstream processing after a successful scrape

When an Actor completes successfully, retrieve run details and route the output to your next workflow step.

Actor Run Succeeded→Get run→Run sync + get dataset items

Retry or alert on failed Actor runs

Detect failed runs, inspect the run metadata, and start a new asynchronous run or notify your team.

Actor Run Failed→Get run→Run Actor (async)

Maintain request queues for crawling jobs

Create a queue, add URLs as requests, and lock queue items for controlled external processing.

Actor Run Created→Create queue→Add request

Monitor Actor builds and collect build logs

When builds fail or time out, retrieve build details and logs for troubleshooting or incident workflows.

Actor Build Failed→Get build→Get build log

FAQ

How does Apify authentication work in Konnectify?

Apify uses API Token authentication in this connector. Create or copy an API token from Apify, then paste it into the API Token field when adding the Apify connection in Konnectify.

Which Apify plans are supported?

Konnectify can connect to Apify accounts that provide API token access to the resources you use. Specific limits, compute usage, storage, proxy features, concurrency, and webhook availability depend on your Apify subscription and account permissions.

How do Apify triggers work?

All Apify triggers in this integration are webhook-based and fire per event. Konnectify receives events such as Actor Run Succeeded, Actor Run Failed, Actor Build Created, and Actor Build Timed Out as Apify sends them.

How can I prevent duplicate records or duplicate processing?

This connector does not include separate upsert actions. To reduce duplicates, use stable Apify identifiers such as run ID, build ID, task ID, queue ID, request unique key, or dataset item identifiers in your workflow logic before creating or updating downstream records.

How are Apify API rate limits handled?

If Apify returns rate limit, quota, or usage errors, the workflow execution may fail or retry depending on your Konnectify workflow settings. Consider adding filters, spacing high-volume runs, using pagination carefully, and monitoring Apify compute and storage usage.

Can I connect multiple Apify accounts?

Yes. Create separate Apify connections in Konnectify using different API tokens. When building a workflow, select the connection that corresponds to the Apify account or workspace you want to automate.

What is the difference between async and sync Actor run actions?

The Run Actor (async) action starts an Actor run and returns run metadata while the run continues in Apify. The sync dataset actions wait for the Actor to finish and return dataset items directly, which is useful for shorter jobs where you need the scraped results immediately.

Ready to automate your Apify workflows?

Connect Apify to Konnectify and build automated workflows for scraping, Actors, queues, builds, runs, and schedules.

Get started free →