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

# Signal playbooks

> Ask your agent to turn a supported signal into a reviewable next action.

[Agent guide: CLI and SDK instructions →](/docs/plays/signal-playbooks)

## 1. Have your context ready

Define the signal, target accounts or contacts, evidence requirements, and allowed response.

## 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 Design a Deepline signal workflow for the event I describe. Check whether a supported Monitor exists; otherwise explain the available polling or scheduled approach. Preserve source event identity and evidence, resolve the intended account or person, and apply my qualification rules. Return a proposed next action or a reason to hold. Show one controlled pilot before activating ongoing work or outbound actions.
```

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 signal is linked to the right entity and a stated rule. The workflow distinguishes an observed event from an inferred intent to buy.

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 a scheduled query become a provider Monitor merely because it runs repeatedly?

> **Show the answer**
>
> No. A schedule starts code. A Monitor owns a supported incoming event feed and
> accepted rows.

## Related guides

* [Monitor Contract Reference](/docs/_generated/monitor-contract-reference)
* [Hiring signals](/docs/human/plays/signal-hiring)
* [Champion tracking](/docs/human/plays/signal-champion-tracking)
* [Fundraising signals](/docs/human/plays/signal-fundraising)


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