Act when the signal arrives.

Track posts and website activity from supported sources, and start a Play when an event matches your rules.

Put a signal to work

A signal becomes a run.

A Monitor stores events from a supported source. A matching workflow can then research the account, alert your team, or update your CRM.

Read the Monitors docs

1Choose a signal

deepline_native logoJob opening rule

Watch Microsoft for data engineering jobs

Company
Microsoft
Domain
microsoft.com
Trigger
A matching job appears

Watch for new data engineering roles. Keep the job link and check whether the role fits your rules.

2Choose the next steps

When Microsoft posts a data engineering jobCompleted

3Set the handoff

hubspot logoHubSpot task

Reach out to Microsoft

Hiring a Senior Data Engineer. 3 decision-makers found, intro drafted. Assigned to Jai Toor.

slack logoSlack · to Jai Toor

Microsoft is hiring a Senior Data Engineer. Your intro is ready, and the task is in HubSpot.

Decide what qualifies.

You decide what counts as a signal. Narrow it at the source, so you only collect the signals you would act on.

Read the Monitor setup docs
  1. 1

    Watch

    This sets the Monitor’s scope: what it collects. Anything outside it is never collected, so it is never billed.

    ExamplePosts by executives at your tier 1 or 2 accounts
  2. 2

    Start the Play when

    A filter on what the Monitor collected. Only the signals that pass it start your Play.

    ExampleThe post mentions AI agents
  3. 3

    Your Play decides

    Your Play applies your business logic to each signal and decides what happens next.

    ExampleTier 1 → notify the account ownerTier 2 → outbound sequence
Executives’ posts5 posts · 4 collected · 3 Plays started
  • Satya Nadella · Microsoft
    • Executive at a tier 1 accountBilled: Monitor event
    • Mentions AI agentsBilled: Play usage
    • Tier 1 routingNotify the account owner
  • Sam Altman · OpenAI
    • Not a tier 1 or 2 accountNot collected
    • Mentions AI agents
    • Routing
  • Jensen Huang · NVIDIA
    • Executive at a tier 2 accountBilled: Monitor event
    • Mentions AI agentsBilled: Play usage
    • Tier 2 routingAdd to the outbound sequence
  • Sundar Pichai · Google
    • Executive at a tier 1 accountBilled: Monitor event
    • Mentions AI agentsSaved · no Play
    • Tier 1 routing
  • Jai Toor · Deepline
    • Executive at a tier 1 accountBilled: Monitor event
    • Mentions AI agentsBilled: Play usage
    • Tier 1 routingNotify the account owner

Watch the whole market. Pay for the hits.

Monitor usage is outcome-based: it is charged when a Monitor returns the result you defined, not for the watching. Signals outside your scope are never collected, so they are never billed. A Play that runs is charged for the tools it calls, like any other run. Pay as you go has no minimum monitor spend.

See pricing

Your Play owns
the response.

A Monitor only supplies the signal. One Monitor can feed several Plays, and each picks up the same signal and does its own job.

Read where data lives
vector logoMonitor: website visitors3 connected Plays

Try it with your agent.

Paste this into Claude Code, Codex or any agent with Deepline set up.

/deepline-gtm Watch Microsoft, Google, and NVIDIA for new posts about AI infrastructure. Save matching posts with their sources and alert me.

Set up Deepline.

Paste this into your agent once. Then come back for the prompt.

Paste into your agent

+ more
Install and set up the official Deepline CLI globally from npm (package: deepline) by following https://code.deepline.com/INSTALL.md. After setup, continue my existing task if I gave one. Otherwise, present the guide's four starter choices verbatim, with each of the first three requests starting with /deepline-gtm.