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

# From a Monitor signal to a Play

> Ask your agent to watch target accounts for a hiring signal and run a Play for each new posting.

[Agent guide: CLI and SDK instructions →](https://deepline.com/docs/guides/monitor-to-play.md)

## 1. Have your context ready

Choose the accounts to watch, the roles that count as a signal, and what should
happen for each posting, such as finding the leader of the hiring team. You
need enough Deepline credits for the Monitor and each Play run.

## 2. Ask your agent

Paste this into your agent, then provide your accounts and roles when it asks:

```deepline-prompt theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
/deepline-gtm Set up a Deepline Native company radar for job openings at my target accounts, scoped in the Monitor payload to the roles I name. Reuse an existing Monitor that already covers the scope instead of deploying a duplicate. Write a Play with a sqlListeners trigger on the company_job_openings stream that finds the leader of the team that is hiring. Validate the Monitor and the Play, and show me the deployment price and the expected cost per run. Wait for my approval before deploying or publishing anything.
```

Complete any requested sign-in yourself. Give the agent the missing information before approving execution. Provider-backed work can incur usage.

## 3. Review the result

The Monitor is `active` with the roles you approved in its payload. The Play is
published, and its listener names the Monitor's tool and stream. A test run
returns the posting and a contact, or a reason no contact was found.

Ask your agent:

```deepline-prompt theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
/deepline-gtm Compare the result with the acceptance rule we agreed. Show the Monitor's state and scope, the Plays connected to its stream, and the runs the Monitor has started. If a run is still in progress or a response is uncertain, inspect the original saved run before proposing another request. Explain the next decision I need to make.
```

A quiet stream is not an error: an account may not have posted a matching role
yet. If the workspace runs out of credits, Deepline turns its Monitors off and
resumes them after you add credits. Events from the time they were off are not
replayed.

## Check your understanding

Does the Play's filter reduce what the Monitor charges for?

> [accordion] Show the answer
>
> No. The Monitor charges for the events it accepts. Narrow its payload to
> reduce accepted events. The Play's filter only decides which stored rows start
> a run.

## Related guides

* [Set up a Monitor](https://deepline.com/docs/human/plays/set-up-a-monitor.md)
* [Deepline Monitors](https://deepline.com/docs/plays/monitors.md)
* [Hiring signals](https://deepline.com/docs/human/plays/signal-hiring.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.