Apify integration

Web Search & Scraping · 7 actions · Bearer token auth

Web scraping, automation, and data extraction platform via the Apify REST API

Put Apify to work View Apify integration docs

Overview

The ModuleX Apify integration lets a ModuleX agent operate Apify on your behalf — working across actors, tasks and dataset items — directly from a plain-English request, using your organization's own Apify credentials. No pre-built workflow is required: the agent picks the right Apify action for the task.

Apify is a web search & scraping platform. ModuleX adds the agent layer: ask for an outcome and it selects and runs the right Apify action — or, when you want a repeatable process, the composer assembles a Apify workflow for you, streaming the nodes onto the canvas as it builds.

Ask the assistant

Drive Apify in plain English

Type what you want. A ModuleX agent picks the right Apify action — or chains several — and runs it. No workflow to build.

Create or update a record in an Apify key-value store
resolves toset_key_value_store_record
Show me the dataset items that match what I describe
resolves toget_dataset_items

Use cases

What you can automate with Apify

Run an actor from a plain-English requestrun_actor
Look up a dataset item on demandget_dataset_items
Set a key value store record without opening the dashboardset_key_value_store_record

At a glance

Apify integration at a glance

VendorApify

CategoryWeb Search & Scraping

Actions available7

AuthenticationBearer token

Uses your own credentialsYes

Works with the assistantYes

Works in the composerYes

Multi-step / tool-chainingYes

Technical referenceView docs

Integration version1.0.0

Last updatedJun 2026

Reference

All 7 Apify actions

Actors1

run_actor

Run an Apify Actor and return the run metadata

Tasks2

run_task

Start an Apify task and return its run metadata

run_task_synchronously

Run an Apify task synchronously and return its dataset items

Dataset Items1

get_dataset_items

Retrieve items from an Apify dataset

Kvs Records1

get_kvs_record

Get a record from an Apify key-value store

Single Urls1

scrape_single_url

Scrape a single URL using Apify's Web Content Crawler and return its content

Key Value Store Records1

set_key_value_store_record

Create or update a record in an Apify key-value store

See full parameters and response schemas in the Apify integration docs

Two ways

Two ways to use Apify in ModuleX

Ask the assistantType what you want done and a ModuleX agent picks the right Apify action and runs it — no workflow to build.

Compose a workflowNeed it to happen every time? Describe the process and the composer wires Apify into a repeatable workflow you can run on a schedule, from chat, or as an API.

Security

Connecting Apify

Bearer tokenApify uses bearer-token authentication. You provide a Apify access token; ModuleX encrypts it and scopes it to your organization so the whole team can use Apify.

Step-by-step setup in the Apify docs

Pairs well with Apify

Agents often chain Apify with these — connect them once and the agent can use all of them in a single task.

Tavily Search3 actions

Airweave1 action

FAQ

Apify + ModuleX FAQ

A ModuleX agent can run any of Apify's 7 actions — across actors, tasks, dataset items and kvs records — from a plain-English request, using your organization's own Apify credentials.

No. The agent selects the right Apify action from your prompt. A workflow is only needed when you want a repeatable process — and the composer builds that for you from a description.

With your own Apify access token, stored encrypted and scoped to your organization.

7, spanning actors, tasks, dataset items and kvs records.

Apify runs on your own credentials, so any Apify usage is billed by Apify directly. ModuleX meters the agent run — and if you connect your own model keys, there's no ModuleX markup on model usage.

Put Apify to work in ModuleX.

Connect Apify once with your own credentials and let your agent run all 7 actions on demand.

Put Apify to work View technical docs

Last updated: Jun 2026Browse all 175 integrations →