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

# Set up a signal Monitor

> Have your agent prepare a supported external signal feed and a downstream Play.

[Agent guide: CLI and SDK instructions →](/docs/plays/set-up-a-monitor)

## 1. Have your context ready

You need Monitor access, a signal scope, and an intended workspace. Not every external event is available as a Monitor.

## 2. Ask your agent

Paste this into your agent, then provide your task and example inputs when it asks:

```deepline-prompt theme={null}
/deepline-gtm Check whether my workspace has Deepline Monitor access and whether the signal I need is supported. Inspect the current type and provider requirements. Propose the narrowest useful scope, destination stream, and a downstream Play if needed. Validate and preview the configuration without deploying it. Explain expected ongoing work, usage, and how to suspend it. Wait for approval before activation.
```

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 deployed Monitor has the intended scope and observed state. The downstream Play receives the correct event, and suspension or removal is confirmed before assuming work has stopped.

Ask your agent:

```deepline-prompt theme={null}
/deepline-gtm Compare the result with the acceptance rule we agreed. Show the evidence for accepted and rejected outcomes, unresolved questions, and recorded Deepline usage where work ran. If work is still running or a response is uncertain, inspect the original saved execution before proposing another request. Explain the next decision I need to make.
```

Approve a larger job, recurring work, or external changes only after reviewing that decision.

## Check your understanding

Does filtering unwanted rows inside the Play prevent the Monitor from accepting those events?

> **Show the answer**
>
> No. Narrow the supported Monitor payload scope. The Play filter operates after
> ingestion and may not reduce accepted-event usage.

## Related guides

* [Deepline Monitors](/docs/plays/monitors)
* [Where data lives](/docs/data-lifecycle)
* [Monitor Contract Reference](/docs/_generated/monitor-contract-reference)


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