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

# Warm outbound automation

> Ask your agent to turn a Warmly visitor event into a reviewed outbound proposal.

[Agent guide: CLI and SDK instructions →](/docs/recipes/warm-outbound-web-intent)

## 1. Have your context ready

Have a Warmly Website Visit Contact source, qualification and suppression rules, and a reviewer destination.

## 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 Deepline workflow for one Warmly Website Visit Contact event. Map the actual event fields, preserve event identity, and apply my qualification, suppression, and deduplication rules. Hold company-only or ambiguous events with reasons. Use the source’s supported verification method and keep webhook secrets private. Show the checked workflow and one controlled test before deployment. Stop at human review; do not send outreach automatically.
```

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 intended person is established and the event reaches the review destination with its evidence. A company-only event is not silently converted into a known person.

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 website visit establish consent or purchase intent for automatic outreach?

> **Show the answer**
>
> No. Treat it as an observed event. Apply the separate identity, eligibility,
> ownership, and approval policies.

## Related guides

* [Webhooks and schedules](/docs/human/sdk-v2/webhooks-and-schedules)
* [Research accounts before outreach](/docs/human/recipes/research-workflow)


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