Apify

Apify + Konnectify

Apify Integration with Konnectify

Connect Apify to Konnectify to automate web scraping, data extraction, Actor runs, datasets, storage, schedules, builds, and webhook-driven operations across your data and AI workflows.

Actors Runs Builds Tasks Datasets Request Queues Key-Value Stores Schedules 11 Triggers 104 Actions

ON THIS PAGE

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

What is Apify?

Apify is a cloud platform for web scraping, browser automation, data extraction, and running serverless automation programs called Actors. It provides storage primitives such as datasets, key-value stores, and request queues, along with schedules, builds, logs, and webhooks for production-grade automation.

By integrating Apify with Konnectify, teams can trigger downstream workflows when Actor runs or builds change, start scraping jobs from business events, move extracted data into other tools, and orchestrate data, developer, and AI workflows without writing glue code.

New to Apify?

Create an Apify account to build, run, and manage web automation Actors.

Visit Apify →

New to Konnectify?

Use Konnectify to connect Apify with your CRM, database, support, marketing, and analytics apps.

What you can automate

• Start Actor or task runs from events in other apps

• Capture successful, failed, aborted, timed-out, and resurrected runs

• Store, retrieve, and enrich dataset items

• Manage request queues and queue locks for crawling workloads

• Create and maintain Actors, builds, versions, and environment variables

• Coordinate schedules, logs, key-value records, and storage metadata

API & Authentication

Authentication method: API Token authentication

This connector uses an Apify API token. In Konnectify, paste your token into the API Token field when creating the Apify connection. The token is used to authenticate requests to Apify’s API for the resources your Apify account can access.

The Apify API capabilities available in this connector cover:

Actors, Actor versions, environment variables, builds, OpenAPI definitions, and logs
Actor runs, task runs, synchronous and asynchronous execution, abort, resurrect, reboot, and metamorph operations
Datasets, dataset items, dataset statistics, request queues, queue requests, locks, and queue heads
Key-value stores, records, schedules, schedule logs, and webhook events for Actor runs and builds

Note: Available operations may depend on your Apify plan, token permissions, storage ownership, and Apify API rate limits. If an action fails with an authorization or limit error, verify your token, plan, and resource access in Apify.

For details about Apify endpoints and API behavior, 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, storage, schedules, and webhooks you want to automate
A Konnectify workspace with permission to create or edit workflows

Add Apify to a Workflow

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

Authorize via API Token authentication

Click Connect account.
Enter your Apify API token in the API Token field.
Save the connection and confirm that Konnectify can authenticate successfully.

Configure the Trigger or Action

Select the Apify trigger or action you want to use.
Map fields such as Actor ID, task ID, run ID, dataset ID, queue ID, store ID, request ID, or JSON input.

Important: For run and storage actions, make sure you pass the correct resource identifier. Apify often distinguishes between Actor IDs, task IDs, run IDs, build IDs, storage IDs, and named storage.

Test the Workflow

Run a test to verify that Konnectify receives sample data or performs the selected Apify action.
Review the output, logs, and field mappings before going live.

Activate the Workflow

Turn on the workflow when your test is successful.
Monitor early runs to confirm expected timing, usage, and output data.

Triggers 11

Apify provides 11 webhook triggers in Konnectify. These triggers fire per event when matching Actor run or Actor build events occur in Apify.

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 104

Use Apify actions in Konnectify to list, create, update, run, retrieve, store, abort, delete, and manage Apify resources across Actors, tasks, storage, schedules, builds, and runs.

Actor Tasks14 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

Get task runs

List runs for a task

Get task input

Get the input configuration for a task

Update task input

Update the task input

Run task (async)

Start an asynchronous task run

Run task sync (GET)

Run task synchronously without input

Run task sync (POST)

Run task synchronously with input

Run task sync + dataset (GET)

Run task synchronously and return dataset items

Run task sync + dataset (POST)

Run task synchronously with input and return dataset items

Get last task run

Get the most recent run of a task

Request Queues & Requests15 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

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 an existing Actor

Delete Actor

Delete an Actor

Validate Actor input

Validate Actor input against its schema

Versions & Environment Variables11 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

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

Actor Builds12 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

Actor Runs22 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 user runs list

List all runs for the authenticated user

Abort run

Abort a running Actor run

Metamorph run

Transform an existing run into a run of a different Actor

Resurrect run

Resurrect a finished Actor run

Get run (global)

Get run by global run ID

Update run

Update run metadata

Delete run

Delete a run

Abort run (global)

Abort run by global run ID

Metamorph run (global)

Metamorph run by global run ID

Reboot run

Reboot a running Actor run

Resurrect Actor run (global)

Resurrect run by global run ID

Charge events in run

Charge for event-based billing within a run

Get run log

Get the log for a specific run

Get log

Get log for a build or run by ID

Run Actor sync (with input)

Run Actor synchronously with JSON input; wait up to 300s

Run Actor sync (no input)

Run Actor synchronously without input

Datasets8 actions

Get list of datasets

List all accessible Apify datasets with optional pagination, sorting, unnamed storage, and ownership filters.

Create dataset

Create a new named dataset

Get dataset

Get dataset metadata

Update dataset

Update dataset metadata

Delete dataset

Delete a dataset

Get dataset items

Retrieve dataset items (supports multiple formats)

Store items

Push new items into a dataset

Get dataset statistics

Get statistics about a dataset

Key-Value Stores & Records10 actions

Get list of stores

List all key-value stores

Create store

Create a new key-value store

Get store

Get key-value store metadata

Update store

Update store metadata

Delete store

Delete a key-value store

Get list of keys

List all record keys from an Apify key-value store.

Check if record exists

Check existence of a record without downloading

Store record

Create or replace a record

Store record (POST)

Store record via POST override

Delete record

Delete a specific record

Popular automations

Here are common ways to use Apify with Konnectify workflows.

Send scraped data to your data stack

When an Actor finishes successfully, retrieve the dataset output and pass it to another database, spreadsheet, CRM, or AI workflow.

Actor Run Succeeded→Get dataset items→Store record

Alert your team when scraping jobs fail

Detect failed or timed-out Actor runs and automatically fetch logs so your team can troubleshoot faster.

Actor Run Failed→Get run log→Abort run

Run scraping tasks from business events

Start an Apify task or Actor whenever another app creates a lead, ticket, record, or campaign item.

Any app trigger→Run task (async)→Get last task run

Coordinate queue-based crawling

Add URLs to Apify request queues, lock queue items for exclusive processing, and unlock requests when processing completes.

Any app trigger→Add request→Run Actor (async)

FAQ

How does Apify authentication work in Konnectify?

Apify uses API Token authentication in this connector. Add your Apify API token in the Konnectify connection screen. The token determines which Actors, tasks, datasets, stores, queues, schedules, builds, and runs the workflow can access.

Which Apify plans are supported?

Konnectify can connect to Apify accounts that provide API token access. Specific capabilities, storage limits, run limits, compute usage, and access to paid Actors depend on your Apify plan and account permissions.

How do Apify triggers work?

The Apify triggers in this connector are webhook-based and fire per event. They listen for Actor run events such as created, succeeded, failed, aborted, timed out, or resurrected, and Actor build events such as created, succeeded, failed, aborted, or timed out.

How can I prevent duplicate data?

This Apify connector does not include a dedicated “upsert” action. To avoid duplicates, use stable IDs from Apify outputs such as run IDs, dataset item identifiers, request unique keys, or key-value store record keys. You can also use actions such as Check if record exists, Get request, or destination-app lookup steps before creating new records.

How are rate limits handled?

Apify API limits and usage limits depend on your account, plan, and workload. If Apify returns a rate-limit or quota error, reduce workflow frequency, paginate list actions where available, limit synchronous runs, or add branching/retry controls in your workflow design.

Can I connect multiple Apify accounts?

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

Should I use synchronous or asynchronous Actor runs?

Use asynchronous run actions for long-running scrapers or crawlers, then react to completion with webhook triggers such as Actor Run Succeeded. Use synchronous actions when you need the result immediately and the run is expected to complete within the supported wait time.

Ready to automate your Apify workflows?

Connect Apify to Konnectify and automate web scraping, Actor runs, storage, schedules, and data pipelines in minutes.

Get started free →