Integrations · Data

Connect Apify to Well

Materialise Apify record, owner, and timestamp into your workspace, queryable in conversation and through agents.

What Well pulls from Apify

Apify feeds record, owner, timestamp into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Apify’s access.

From Apify	In Well	Relation
Record	Graph node	Becomes
Owner	Team member	Resolves to
Timestamp	Audit entry	Anchors

Sync mode: MCP hybrid
Refresh: live + reconciliation reads
Direction: Apify → Well

What Well does with your Apify connection

Connect

Connect Apify over OAuth (MCP DCR): Well registers a client through Apify's OAuth Dynamic Client Registration and you approve on Apify's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Well brings record, owner, and timestamp in from Apify through live reads, backed by a periodic reconciliation pass. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each Apify entity into graph node, team member, and audit entry, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Apify lands in the workspace as graph node, team member, and audit entry you can search, chart, and automate.

Questions Apify unlocks

Ask in plain language. Well answers from your connected Apify connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Apify connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Apify connection…

1 agent skill runs on Apify.

Well lists Apify in the connection check every skill runs before it answers. No skill reads it for a figure yet.

Connects and checks Apify

Check your connections

See what is connected, what is syncing, and what is missing.

Browse all skills

Connect Apify in three steps

01
Authorise Apify via MCP
From Well's Connections panel, search for Apify and click Connect. Well discovers Apify's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Apify's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
02
Map your entities
Well's MCP client discovers record, owner, and timestamp from Apify that Apify's MCP server exposes and brings them into your workspace using the canonical mappings defined in Well's data-views layer. You can inspect the workspace data model from Settings > Data Model.
- Mappingpreconfigured by Well
03
Use the data
Ask questions in conversation, build records tables, or let agents act on Apify records. Because Apify ships through MCP, Well treats every entity it exposes as queryable graph state alongside the rest of your connected tools.
- First syncstarts as soon as connect completes

MCP handshake typically completes under a minute on warm connections. Resource enumeration runs immediately after; full backfill of historical Apify records happens in the background.

How Apify stays secure with Well

Well connects to Apify's MCP server via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Apify secret. Tokens are scoped to the record, owner, and timestamp Apify exposes and refreshed server-side. Reads only, Well cannot modify or delete Apify records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requests

Read Apify records
Resources the Apify MCP server exposes, scoped by your OAuth approval.
granted
Resolve record, owner, and timestamp across your stack
Match identifiers in Apify against the same entities your other connected tools expose, so each record carries cross-tool context.
granted
Modify or delete Apify records
Not granted; Apify is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Store Apify passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
refused

Disconnect any time from Well settings or Apify’s admin panel.

Frequently asked questions about Apify and Well

How do I connect Apify to Well, and how long does it take?

From Well, open Connections, find Apify, and click Connect. Well discovers the OAuth metadata from Apify's MCP server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Apify's side. No client_id or client_secret to paste; the handshake takes roughly a minute.

What does Well pull into the workspace from Apify?

Well brings in record, owner, and timestamp from Apify and reshapes each entity into your workspace: record becomes graph node; owner becomes team member. Every record arrives with the source identifier preserved, so Apify stays the source of truth while Well lets you query the data alongside the rest of your stack.

How does Well materialise Apify data into your workspace?

Well materialises selected tables or queries from Apify into your workspace. New rows flow in incrementally on a cadence you set; downstream agents and dashboards see the same canonical entities as the rest of your workspace, with the Apify source link preserved.

What happens when Apify updates a record that Well already pulled in?

Well watches for updates to records and applies them on the next sync, preserving the original workspace identifier so anything downstream (records tables, conversation history, agent runs) keeps pointing at the right graph node. Edits flow in incrementally; nothing is duplicated, and the Apify source identifier is retained on every revision.

How often does Apify sync with Well, and what triggers a refresh?

Well combines live Apify events with periodic reconciliation reads of record, owner, and timestamp. New rows appear within seconds when Apify pushes them; periodic reads catch anything a push missed. The first connect backfills history from Apify in the background.

Can I disconnect Apify and what happens to the data Well already pulled?

Open Connections > Apify in Well and click Disconnect. Well calls Apify's token revocation endpoint and stops calling Apify immediately on its side; provider-side propagation to Apify's admin panel varies by provider. The record, owner, and timestamp Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.

How does Well protect what it pulls in from Apify?

The Apify records Well holds are encrypted at rest and handled in line with GDPR. See /privacy for the current data-handling policy.