Skip to main content
A Monitor is an always-on provider event feed. Most supported Monitor sources push events into Deepline. A Monitor receives supported upstream events, applies the configured scope, and writes accepted event rows to the Database. A published Play can then react to those rows. A Monitor does not contain your business logic and does not run a Play by itself. It is the durable event-ingestion part of the system.

​
The event path

For a Monitor-driven workflow, the event moves through five distinct steps:
  1. A supported external source sends an event to Deepline.
  2. The Monitor validates the event against its configured scope.
  3. Deepline writes the accepted event to a Database stream.
  4. A published Play with a matching SQL listener starts for that row.
  5. The Play runs its code and can enrich the record, send an alert, or update a downstream system.
A Play subscribes to a tool and stream, not to a Monitor key. One Monitor can therefore supply a shared stream to more than one Play, query, dashboard, or export. Do not deploy a separate Monitor for each Play unless its upstream scope genuinely differs.

​
What a Monitor is—and is not

A Monitor is not a polling job, a private table for one Play, or a replacement for a Play’s row-level logic. The Monitor scope controls what Deepline accepts; the SQL-listener filter selects which accepted rows start a Play; the Play body makes the business decision.

​
Scope comes before Play logic

It is tempting to accept a broad feed and filter it later in code. That is the wrong boundary for an event-priced Monitor: filtering only in a Play does not stop the Monitor from accepting the event. Narrow the Monitor payload when you need to reduce accepted event volume.

​
Lifecycle and dependencies

A Monitor definition describes the source, scope, and output stream. Deploying, updating, reactivating, or deleting one can change an upstream provider resource and affect every consumer of its Database rows. Inspect its dependent Plays and shared stream before making a lifecycle change. Monitor pricing depends on the feed: it can apply at deployment or reactivation, per accepted event, or at renewal. Deepline shows Deepline credits, not provider spend.

Set up a Monitor

Validate, preview, deploy, and inspect a scoped event feed safely.

How Plays work

Understand the code that reacts to Monitor events.

Where data lives

Decide when an event belongs in the Database and when an outcome belongs in a CRM.

Monitor contract reference

Inspect supported Monitor payloads, streams, outputs, and update semantics.