Skip to main content
Use this guide to turn a Warmly Website Visit Contact event into a reviewed outbound lead. Warmly pushes the visitor event to your webhook. The Play normalizes it, applies your rules, and stops before any external activation until a human approves it.

Warmly sends the visitor event. The Play either records a reason to stop or sends a qualified lead to human review.

​
Prerequisites

  • A Warmly source that can send Website Visit Contact events.
  • A reviewer and a review destination, such as a Slack queue or CRM review field.
  • ICP, suppression, deduplication, and approval rules that the Play can apply.
  • A connected Deepline workspace and a local project folder for the Play file.

​
Create the Play

Give your coding agent this request:
Use the source system’s supported webhook verification method when it provides one. Keep the webhook URL and any signing secret out of source control.

​
Validate it without deploying or spending credits

Check the local Play before it is published or receives an event:
plays check validates the local artifact. It does not publish the Play, create a run, or call an enrichment provider.

​
Publish and configure Warmly

After you review the checked source, publish it:
Copy triggerMetadata.webhookUrl from the JSON response. Treat the full URL as a secret.

The Webhook node is the entry point for each Warmly event.

In Warmly:
  • On the free tier, open Settings > Webhooks, paste the full URL, and save.
  • On a paid tier, use Orchestrator: choose Website Visit Contact, add Send Contact to Webhook, paste the full URL, and activate the orchestration.
Use Send Company to Webhook only when your Play is designed for company-level events. See Warmly’s webhook guide for its current setup and payload details.

​
Map the event fields

Keep the raw event available for debugging, but write the normalized fields your logic needs. Do not assume all visitor events identify a person; a company-only event should stop with its recorded reason.

​
Test one event and inspect the result

Send one controlled Warmly test event. Then inspect the newest run:
Check that the event is normalized, deduplicated, and either stopped with a miss_reason or routed to the designated human reviewer. Confirm that no CRM, campaign, or email action ran before approval.

​
Next step

For webhook authentication and other trigger patterns, read Webhooks and schedules. For the research that supports a reviewed outbound action, read Research accounts before outreach.