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

# Schedule or trigger a Play

> Have your agent set up a Play to run on a schedule or an incoming event.

[Agent guide: CLI and SDK instructions →](/docs/sdk-v2/webhooks-and-schedules)

## 1. Have your context ready

Have a checked Play and decide the event, schedule, timezone, allowed inputs, and maximum intended work.

## 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 Prepare a trigger for my Deepline Play. Ask whether I need an incoming webhook or a schedule. Inspect the supported configuration. For a schedule, confirm the timezone and intended times. For a webhook, define sender authentication, delivery identity, and how event fields become inputs. Show the deployment and one bounded test before activating ongoing work.
```

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 observed event or scheduled occurrence starts the intended Play with the expected input. Check repeated deliveries and external-write behavior before enabling recurring work.

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

The same event content arrives twice. Can you assume it will only start work once?

> **Show the answer**
>
> No. Ask the agent how the sender supplies a stable delivery identity and how
> the workflow handles repeated delivery.

## Related guides

* [Write Plays](/docs/human/sdk-v2/plays)


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