Deepline Monitors

A Deepline Monitor is an always-on provider event feed. It captures events such as new job posts or campaign replies and saves them to your Customer DB. A connected Play can then enrich the event, update your CRM, or alert your team.

Getting started

The quickest path is to tell your Deepline agent what to watch and what should happen next:

Monitor interested replies from my Instantly campaign. Save each reply, enrich the person and company, then create an Attio task for the account owner.

The agent will check access, look for an existing feed it can reuse, show the scope and Deepline-credit price, and ask for approval before it deploys or changes anything. To set up a Monitor yourself, follow this sequence.

1. Check access

deepline monitors status

Local and preview environments allow every authenticated user. Production access is limited. Contact the Deepline team to request access.

2. Choose a Monitor type

deepline monitors available
deepline monitors available instantly.campaign_events

The detailed view shows the required payload, output streams, Customer DB tables, and Deepline pricing. Use the returned tool id and payload schema; do not guess them.

3. Check for an existing feed

deepline monitors list --status all
deepline monitors get <candidate-key>

For every same-tool candidate, use get to compare its full definition and provider filters with the scope you need. Reuse it only when those match. Monitors write to shared streams, so a new Monitor does not create a private channel for one Play.

4. Define and check the Monitor

Save this example as monitor.json, replacing the campaign id:

{
  "key": "instantly-interested-leads",
  "tool": "instantly.campaign_events",
  "name": "Interested Instantly leads",
  "payload": {
    "event_type": "lead_interested",
    "campaign_id": "camp_123"
  }
}

Validate it without deploying or spending credits:

deepline monitors check --file monitor.json

5. Preview the price, then deploy

deepline monitors deploy --dry-run --file monitor.json
deepline monitors deploy --file monitor.json

The dry run shows the selected Deepline pricing and any existing Monitor that may already cover the scope. Run the second command only after the scope and price look right.

6. Verify the live Monitor

deepline monitors get instantly-interested-leads --json

Confirm that the status is active and that the definition, output streams, pricing, and connected Plays match the plan.

Connect a Play

A Monitor supplies events. A Play decides what to do with each event. For the example above, generate a Play bound to the Monitor’s event stream:

deepline plays bootstrap monitor-triggered \
  --tool instantly.campaign_events \
  --stream webhook_events \
  --out on-interested-lead.play.ts

Before publishing, edit the generated sqlListeners entry so this Play reacts only to rows covered by this Monitor:

where: {
  after: {
    event_type: { eq: 'lead_interested' },
    campaign_id: { eq: 'camp_123' },
  },
},

Use the event type and campaign id from your Monitor definition. Then validate and publish the Play:

deepline plays check on-interested-lead.play.ts
deepline plays publish on-interested-lead.play.ts

The Play can enrich the lead, filter low-quality replies, update a CRM, or send a Slack alert. Once published, it runs when a matching row reaches the stream. There is no polling job or manual Monitor run.

Plays subscribe to a tool and stream, not one Monitor key. If several Monitors write to the same stream, use a Play’s sqlListeners.where filter to select the rows that should trigger that Play.

Monitor or scheduled Play?

Use a Monitor when…	Use a scheduled Play when…
The provider sends an event when something changes.	Deepline must check for changes on a timer.
You need replies, job posts, funding, or CRM changes within seconds.	You need a daily or weekly search, enrichment, comparison, or report.
The source offers a supported event feed.	The source only offers a search or enrichment action.

Pricing and insufficient credits

Monitor pricing depends on the feed. A Monitor may charge on deployment or reactivation, for each accepted event, or on a recurring renewal. Always use the price returned by available, check, or deploy --dry-run. Deepline shows only Deepline credits, never provider spend. For event-priced Monitors, filtering after ingestion does not remove the event charge. Narrow the Monitor’s provider payload when you need to reduce accepted event volume. Deepline checks the workspace balance before each billable event or renewal. If the charge cannot be reserved, Deepline pauses the Monitor and requests upstream disablement. Callbacks may still be kept for audit, but they do not create typed Customer DB rows or run connected Plays while the Monitor is paused. Add credits under Billing, preview the reactivation charge, then reactivate:

deepline monitors reactivate instantly-interested-leads --dry-run
deepline monitors reactivate instantly-interested-leads

Monitors do not restart automatically after a top-up.

Monitors rate card

See the current Deepline-credit price and billing timing for every Monitor.

Manage a Monitor

Task	Command
List active and paused Monitors	`deepline monitors list --status all`
Inspect one Monitor	`deepline monitors get <key>`
Preview reactivation	`deepline monitors reactivate <key> --dry-run`
Preview deletion	`deepline monitors delete <key> --dry-run`
Delete and deprovision upstream	`deepline monitors delete <key>`

Before an update or deletion, inspect the Monitor’s connected Plays and shared output streams. Other SQL queries, dashboards, exports, or warehouse jobs may also read the same tables.

Troubleshooting

No access: contact the Deepline team to request access. Local and preview environments only require an authenticated user.
Validation failed: fix every reported payload path, then rerun deepline monitors check --file monitor.json.
Monitor type not found: run deepline monitors available and use an exact returned tool id.
Monitor is paused: add credits, run reactivate --dry-run, then reactivate after reviewing the price.
Another Monitor covers the same scope: reuse it and filter the connected Play instead of paying to provision a duplicate feed.

Explore plays

See what a connected or scheduled Play can do after a signal arrives.

Getting started

Tutorials

How-to guides

Explanations

Real-world examples

Reference

Deepline Monitors

Getting started

Connect a Play

Monitor or scheduled Play?

Pricing and insufficient credits

Monitors rate card

Manage a Monitor

Troubleshooting

Explore plays

​Getting started

​Connect a Play

​Monitor or scheduled Play?

​Pricing and insufficient credits

Monitors rate card

​Manage a Monitor

​Troubleshooting

Explore plays

Getting started

Connect a Play

Monitor or scheduled Play?

Pricing and insufficient credits

Manage a Monitor

Troubleshooting