Enterprise Tool

Apify

Run web scrapers and automation Actors via the Apify platform API

Apify is a web scraping and automation platform with thousands of ready-made Actors in the Apify Store — from full-site crawlers and Google SERP scrapers to social media monitors and data transformers. CipherSense Agents connects via your Apify API token, letting workflow nodes run any Actor synchronously or asynchronously, poll run status, and retrieve scraped data from datasets or key-value stores. Apify also provides an official hosted remote MCP server at https://mcp.apify.com (Streamable HTTP) that exposes any Apify Store Actor as an MCP tool with dynamic discovery.

Official documentation

Setup

Get your Apify API token

Sign in to the Apify Console, go to Settings > Integrations, and copy your API token. You can also create scoped tokens for specific resources. The token is used as Authorization: Bearer {apiToken}.

Apify Console

Find an Actor ID

Browse the Apify Store to find an Actor. The Actor ID is shown in the URL and API tab — format is username~actor-name (e.g. apify/web-scraper) or a raw hash ID. Copy it for use in your workflow nodes.

Apify Store

Add the integration in CipherSense Agents

Go to Project > Integrations > Add Integration > Apify. Paste your API token and optionally set a Default Actor ID. Click Save & Test to validate the connection.

Build your workflow

Use Run Actor (Async) for long-running scrapes — it returns immediately with a runId and defaultDatasetId. Wire those into downstream Get Dataset Items nodes to fetch results. For fast Actors (under 5 minutes), use Run Actor Sync to get results in a single node.

(Optional) Use the Apify MCP server

Apify has an official hosted remote MCP server at https://mcp.apify.com (Streamable HTTP transport). Add it as a Custom MCP integration to expose any Apify Store Actor as an MCP tool with dynamic discovery — no local install required. Note: SSE transport is deprecated; use HTTP transport.

Connection Fields

Fields required when adding this integration in your Project › Integrations.

Field	Required	Description
API Token	Required	From Apify Console > Settings > Integrations. Used as Authorization: Bearer {apiToken}.
Default Actor ID	Optional	Default Actor when no actorId is set per-node. Format: username~actor-name or raw ID.

Common Use Cases

Lead enrichment: scrape LinkedIn or company websites → extract contacts → push to HubSpot CRMCompetitive monitoring: run a price scraper Actor daily → compare with stored prices → alert via SlackContent pipelines: crawl news sites → extract articles → summarise with LLM → store in databaseSERP tracking: run Google SERP Actor on target keywords → parse rankings → store in AirtableAsync scraping: run_actor → store runId → poll get_run until SUCCEEDED → fetch get_dataset_items

Ready to connect Apify?

Add this integration from your project dashboard and wire it into a workflow.

Open Dashboard ← Back to Integrations