> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Deepline Monitors

> Deepline Monitors watch for events in real time or run checks on a schedule, then trigger a play that acts on what changed.

A **Deepline Monitor** watches for a change and acts when it happens. It can
listen to a real-time event stream, such as a new job posting or an email reply,
or run a play on a schedule to check any source Deepline can access.

The monitor decides **when** work starts. A play decides **what happens next**.

## Monitors + plays: signal in, action out

<CardGroup cols={2}>
  <Card title="Monitor" icon="satellite-dish">
    The trigger. It listens for an event or checks for changes on a schedule.
  </Card>

  <Card title="Play" icon="bolt">
    The reaction. It can enrich, qualify, research, update a CRM, send an alert,
    or run any other available Deepline action.
  </Card>
</CardGroup>

Together they form a hands-off loop: **change happens → play runs → outcome
lands in your CRM, Slack, warehouse, or inbox**.

## Pricing

We charge for monitor events. The cost of an event depends on the monitor you
use, so check the full rate card for the exact price.

Deepline shows the monitor configuration and estimated Deepline-credit cost
before deployment. Provider spend is never exposed.

<Card title="See the full Monitors rate card" icon="coins" href="/_generated/pricing-schedule#monitors">
  Compare every Deepline Monitor rate, including Deepline Native job posts,
  promotions, mentions, job changes, social activity, and industry signals.
</Card>

See the [full Monitors rate card](/_generated/pricing-schedule#monitors).

## Two ways to monitor

<CardGroup cols={2}>
  <Card title="Real time" icon="bolt">
    A provider sends an event the moment something changes. Deepline writes the
    accepted event to your warehouse and starts the bound play.
  </Card>

  <Card title="Scheduled" icon="clock">
    A play runs hourly, daily, weekly, or on another cron schedule. It can call
    any available action, compare the result with prior data, and act on
    changes.
  </Card>
</CardGroup>

|                  | Real-time monitor                        | Scheduled monitor                                         |
| ---------------- | ---------------------------------------- | --------------------------------------------------------- |
| **Triggered by** | An upstream event                        | A schedule you choose                                     |
| **Latency**      | Seconds after the event                  | At the next scheduled run                                 |
| **Best for**     | Replies, job posts, funding, CRM changes | Any recurring search, enrichment, comparison, or workflow |
| **Pricing**      | Per event, recurring, or included        | Actions used by each run                                  |

<Tip>
  Describe the timing you need. Say *"the moment X happens"* for real-time
  monitoring. Say *"every morning"* or *"once a week"* for a scheduled monitor.
</Tip>

## A concrete real-time example

> "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."

<Steps>
  <Step title="A target account posts the role">
    The monitor detects the posting and writes the accepted event to your
    warehouse.
  </Step>

  <Step title="The play starts">
    The bound play enriches the company and finds the hiring manager's verified
    email.
  </Step>

  <Step title="The outcome reaches your team">
    The play posts the enriched signal to Slack while the role is still open.
  </Step>
</Steps>

## What can I monitor? (Some examples)

Anything an available Deepline action can observe can become a scheduled
monitor. Real-time monitoring is available when the source provides an event
stream. The examples below are starting points, not a fixed list of supported
use cases.

| Goal                                                               | Recommended mode | Example source or action                |
| ------------------------------------------------------------------ | ---------------- | --------------------------------------- |
| React to new job postings                                          | Real time        | Deepline Native                         |
| Catch promotions, new hires, funding, mentions, or social activity | Real time        | Deepline Native                         |
| Qualify replies from outbound campaigns                            | Real time        | Instantly, Lemlist, HeyReach, Smartlead |
| React to CRM record changes                                        | Real time        | Attio                                   |
| Re-run a search and detect new results                             | Scheduled        | Any search or research action           |
| Refresh enrichment and compare fields                              | Scheduled        | Any enrichment action                   |
| Check websites, news, ads, technologies, or market changes         | Scheduled        | Any web, data, or AI action             |
| Update a CRM, sequence, sheet, Slack channel, or warehouse         | Either           | Any supported destination action        |

## Example prompts

<CardGroup cols={1}>
  <Card title="Real time · Hiring signal → alert" icon="briefcase">
    "Watch for new **RevOps** or **GTM Engineer** job postings at the companies
    in `icp.csv`. When one appears, enrich the company, find the likely hiring
    manager, and send me a Slack summary."
  </Card>

  <Card title="Real time · Reply → qualify and route" icon="reply">
    "Capture replies to my **Instantly** campaigns. When someone is interested,
    enrich the person, score the account, and create an Attio task for the
    owner."
  </Card>

  <Card title="Scheduled · Any action" icon="clock">
    "Every Monday, check the companies in `accounts.csv` for new
    decision-makers, product launches, pricing changes, and relevant news.
    Compare with last week's results and send only the changes to Slack."
  </Card>
</CardGroup>

## How do I set one up?

<Steps>
  <Step title="Describe what to watch and what should happen">
    Give the agent the signal or schedule, the accounts or records in scope, and
    the destination for the result.
  </Step>

  <Step title="Review the plan and price">
    Deepline shows the monitor, play, destination, and estimated Deepline-credit
    cost before anything is deployed.
  </Step>

  <Step title="Confirm deployment">
    Once live, the play reacts to each accepted event or runs on its schedule.
  </Step>
</Steps>

<Accordion title="A little about how it works" icon="code">
  You don't need this to use Deepline Monitors. A real-time monitor provisions a
  managed feed and points it at a private, per-workspace table in your Deepline
  warehouse. Every accepted event is written as a typed row. A bound play
  subscribes to that table and runs inline when a matching row appears.

  A scheduled monitor uses the same play machinery on a timer instead of an
  event. Your data stays in your warehouse; the play is the only thing that acts
  on it.
</Accordion>

<Card title="Explore plays next" icon="bolt" href="/plays/plays-overview">
  Monitors decide when a play runs. See the play library for what it can do.
</Card>