Lookout docs

Start here to turn account and customer signals into repeatable actions with Lookout Motion.

Last updated: July 12, 2026

Lookout watches for meaningful changes, checks whether they apply to the right account or contact, and starts the next action through Motion. Use these docs to create your first Motion, connect a signal source, and review what ran.

Start here

How Motion works

Every Motion follows the same three-part flow:
  1. Detect a signal. Lookout receives a change such as funding, a new executive, hiring growth, website intent, or another event from a connected source.
  2. Check the audience and conditions. The Motion confirms whether the account, contact, or event matches its rules.
  3. Run the next action. Lookout starts the connected Sanka workflow and records the result.
Lookout includes templates for signal-triggered outbound, LinkedIn and content engagement, inbound operations, ABM and ads, expansion and retention, and AI-assisted plays. Templates start as drafts so you can review the signal, conditions, and action before activation.

Main areas in Lookout

  • Motions: browse templates, edit a Motion, change its status, and review runs, approvals, and outcomes.
  • Health: confirm that Lookout can receive and process workspace data.
  • Data streams: review the sources and destinations that feed Lookout.
  • Settings: manage setup details, Sanka Tag, allowed origins, and related workspace configuration.

Testing and plan requirements

You can explore the Lookout interface and prepare a draft Motion without connecting Clay. Lookout availability and production pricing can depend on your workspace and rollout scope; review Lookout pricing before production use. Clay's current Free and Launch plans do not include HTTP API integrations. To complete the Clay-to-Lookout test in this guide, use a Clay Growth or Enterprise plan, or an eligible Clay trial. Confirm current availability on Clay's pricing page before you begin.