Skip to main content
A Deepline Tracker is an always-on watcher for a single kind of event — a new job post, an email reply, a funding round, an intent signal. When the event happens, the Tracker writes it into your Deepline warehouse as a typed row. No run to kick off, no polling, no dashboard to check.

​
Start with one signal

Track one event type first. Pick the destination before you automate it.
On its own a Tracker just captures events. It becomes useful when you pair it with a play that reacts to each new row.

​
Trackers + plays: signal in, action out

Tracker

The feed. It watches for one kind of event and writes each new occurrence into your warehouse as it arrives.

Play

The reaction. It runs automatically every time a new event lands — enrich, qualify, route, alert.
Together they form a hands-off loop: event happens → play runs → outcome in your CRM / Slack / inbox. You describe the outcome you want in plain language and Deepline builds the Tracker and the play, picks the providers, and wires the trigger.

​
Two ways to automate a play

A play doesn’t have to be run by hand. There are two ways to make one run on its own; which one fits depends on whether you’re reacting to a moment or working on a cadence.

Realtime (Tracker-backed)

The play fires the instant a Tracker captures a new event — a new job post, a reply, a funding round. Use it when the timing of the signal is what matters.

Scheduled (cron)

The play runs on a schedule you set — every morning, hourly, weekly — and acts on whatever’s new since last time. Use it for steady, recurring work.
You don’t pick the mechanism explicitly. Say “the moment X happens…” and Deepline sets up a Tracker; say “every morning…” or “once a week…” and it sets up a scheduled play.

​
A concrete example (realtime)

“Watch for new VP of Sales or Head of Revenue job postings at the accounts in my target-accounts.csv. When one appears, enrich the company, find the hiring manager’s email, and post it to our #signals Slack channel.”
From that one sentence to the agent, Deepline sets up a Tracker for those job postings and a play that fires on each new one:
1

A target account posts the role

The Tracker detects the new posting and streams it into your warehouse within seconds — no run, no polling.
2

The play fires automatically

Bound to that feed, the play runs the moment the row lands: it enriches the company and finds the hiring manager’s verified email.
3

You get the outcome where you work

The play posts the enriched signal to #signals. You reach out while the role is still open and the buying trigger is fresh.

​
What can I track?

​
Example prompts

Trackers and scheduled plays are built the same way as any Deepline play — you describe the goal to the agent (Claude Code or Codex) and it does the rest. Copy one of these as a starting point and swap in your own accounts, roles, and destinations.

Realtime · Hiring signal → alert

“Watch for new RevOps or GTM Engineer job postings at the companies in icp.csv. The moment one appears, enrich the company, pull the likely hiring manager’s email, and DM me in Slack with a one-line why-now.”

Realtime · Reply capture → qualify & route

“Capture every reply to my Instantly campaigns. When someone replies with interest, enrich the person, score them against my ICP, and create a task for the account owner in Attio.”

Realtime · Funding signal → campaign + draft

“Watch my ICP for new funding rounds. When a company raises a Series A or B, add it to my ‘Recently Funded’ Salesforce campaign and draft a tailored congrats-and-intro email for me to review.”

Scheduled · Weekly list refresh

“Every Monday morning, re-scan the accounts in accounts.csv for any new decision-makers in Sales or RevOps, enrich their emails, and add the new ones to my sequence.”
Describe the outcome and the destination (“…post it to Slack” / “…create a task in Attio”), not the steps. The agent selects providers, wires the trigger, and handles the enrichment path for you.

​
How do I set one up?

1

Describe the signal (or schedule) and the action

Tell the agent what to watch for — or how often to run — and what to do when it happens, in one plain-language prompt like the examples above.
2

Review the plan before it goes live

Deepline shows you exactly what it will set up — the signal it will watch and the Deepline-credit cost — before anything is deployed. Nothing runs until you confirm.
3

Let it run

Once live, the play reacts to each event (or fires on schedule) automatically. There’s nothing to babysit.

​
A little about how it works

You don’t need this to use Trackers, but if you’re curious: a Tracker provisions a managed feed with the source and points it at a private, per-workspace table in your Deepline warehouse. Every event is written there as a typed row the moment it arrives. A Tracker-backed play subscribes to that table and runs inline whenever a matching row is written — so “react to a signal” is just “a new row appeared.” A scheduled play uses the same machinery on a timer instead of an event. Your data stays in your warehouse; the play is the only thing that touches it.

Explore plays next

Trackers and schedules decide when a play runs. See the full library of plays for what they can do.