Skip to main content
Deepline is the execution layer for GTM work done by coding agents. You state the outcome. Your agent selects or writes a Play. Deepline runs the Play and keeps the inputs, outputs, and history for every run. Use Deepline to enrich people or companies, research accounts, react to provider events, and update connected business systems.

​
Start with the interface you use

Coding agent

Install Deepline in Claude Code, Codex, Cursor, or another agent that can use a shell. Then run one GTM request.

Claude plugin

Add the Deepline plugin if Claude Code or Claude Cowork is where you work.

MCP client

Connect Deepline to ChatGPT Work, Claude Desktop, or another MCP client.

SDK

Inspect, pilot, and scale a versioned workflow from your codebase.

​
The three primitives

Skills give an agent the operating instructions to use these primitives.

​
Plays

A Play is versioned code for repeatable GTM work. It runs inside Deepline. Your agent writes or chooses the Play. Deepline records every run. Learn how Plays work.

​
Customer DB

Customer DB is your workspace’s PostgreSQL database for customer records and supported event tables. Its records persist across Play runs. Learn how to query Customer DB.

​
Monitors

A Monitor pushes events from a supported external source into Deepline. It writes accepted events to Customer DB. A connected Play can then enrich a record, update a CRM, or alert a team. Learn how Monitors work. Plays execute code. Monitors ingest external events. Customer DB stores the records they use. That is the whole system: receive a change, keep the data, run code, and send the result where it belongs.

​
How the system fits together

An agent can run a Play directly. A schedule, webhook, or Monitor event can start a Play.
Deepline architecture: external sources push events through Monitors into Customer DB; Plays execute code inside Deepline; and Plays send actions to downstream systems.

How agents, data, events, and downstream systems connect.

Run your first Play.