Integrations · Data & enrichment

Apify

Native

The master pipeline. Any actor becomes a source — or a signal — with no code.

Request a free sample
What it unlocks

What you actually get

This is the one that unlocks the rest. A data source is declared in a YAML file: point it at an Apify actor and it becomes either an input feed or a live radar watching for signals. Adding a source your competitors would scope as a project is, for us, a configuration change during onboarding.

We run it. Live today.

How it runs

The flow, end to end

  1. You name the source you want watched (a directory, a marketplace, a social feed).
  2. We point a data hub at the matching actor and declare the field mapping in YAML.
  3. The hub runs on a schedule and normalises what it returns into the same shape as every other source.
  4. Rules decide what counts as a signal — a new listing, a hiring post, a change in a profile.
  5. The signal enters the outbound motion like any other. No separate tooling, no second dashboard.

Powers: Outbound systemContent engine

Capabilities

What we can do with it

Read

Any actor becomes an input feed once it is declared.

  • Company profiles and directory records
  • Posts, listings and reviews
  • Whatever the actor returns, normalised to one shape

Watch

The same actor can run on a schedule and emit signals instead of just data.

  • A new listing appears
  • A profile or page changes
  • A post matches the topic you sell into
  • Re-runs on a schedule, with dedup against what we already saw
In practice

Flows we actually run

Not what the API could theoretically do — what the motion does with it, end to end, while you are doing something else.

1

Turn a directory into a lead source

TriggerYou name a directory, marketplace or public listing where your buyers appear
  1. We point a data hub at the matching actor and declare the field mapping in YAML.
  2. The hub runs on a schedule and normalises what it returns.
  3. Rules decide which records qualify as accounts worth pursuing.
  4. Qualified accounts enter the outbound motion with the source attached.
ResultA source your competitors would scope as a development project becomes a feed, live in days.
2

Watch a source for change, not just content

TriggerSomething on a page changes — a new listing, a new role, an updated profile
  1. The actor re-runs on a schedule and the result is compared against the last snapshot.
  2. Only what changed becomes a signal; the rest is ignored.
  3. The signal attaches to the company record with the date it was detected.
  4. The message references the change specifically, not the company generally.
ResultThe reason to write is a real event with a date, which is the difference between relevance and noise.
Technical detail

Objects, direction and honest limits

Objects touchedDeclared per source in YAML — actor id, field mapping, schedule, dedup key
Direction← In: whatever the actor returns — company profiles, posts, listings, reviews, directory records. Nothing leaves through this path.

What it cannot do yet

What it does not do

Questions

Frequent questions

Do we need our own Apify account?

No. The actors run on our side and the cost sits with us. You describe the source you want watched; what comes back arrives normalised alongside every other feed.

What if the source changes and the actor breaks?

Fixing the mapping is on us — it is part of operating the motion, not a change request you get billed for. You find out because the signal keeps arriving, not because a dashboard turned red.

Is this legal?

We collect what a source publishes publicly, we do not bypass a site's terms, and we do not log in on your behalf. If a source requires an account to see the data, it is out of scope.

Run Apify? Let's show you, not tell you.

We will send you real outbound emails and a content read for your business in 24 hours — before any commitment, and with no call required.

Request a free sample

← All integrations