Contact SalesStart Free

Get started with Lookout

Create a draft Motion from a template, configure its action, and run a controlled signal test.

Last updated: July 14, 2026

This guide takes you from an empty Lookout workspace to a draft Motion that is ready for a controlled test. Start with a draft, confirm the action and approval behavior, and activate it only after review.

Before you start

Prepare the following:
  • A Sanka account with access to the target workspace.
  • Permission to create workflows and developer tokens in that workspace.
  • A clear test case, such as funding-trigger outreach for one test company.
  • A signal source. You can connect Clay later; it is not required to explore templates and prepare a draft.

Open Lookout

  1. Open Lookout and sign in with your Sanka account.
  2. Select the workspace you want to use.
  3. Open Motions from the sidebar.
Lookout prepares the managed workspace data plane automatically. If Health still shows an error after reloading, confirm your workspace access and contact Sanka support before activating a Motion.

Create a Motion from a template

  1. Filter or search the Motion templates.
  2. Choose a template that matches the signal you want to test.
  3. Click Build this Motion.
  4. Wait for Lookout to open the newly created Motion under My Motions.
The Motion opens as a draft. Creating the same template again returns the existing Motion instead of creating another active copy.

Review the flow

The editor shows a Signal → Action flow.
  1. Select the Signal node and choose the Trigger event, such as Funding event.
  2. If needed, add filters under Narrow the audience for funding stage, industry, country, or another incoming value.
  3. Select the Action node and choose the Sanka workflow action that should run.
  4. Click Save graph.
The trigger event is the change reported by your connected source. For example, Funding event starts this Motion only when the source reports a funding event. Connect the source under Data streams, then send one test event that matches the selected trigger. Most users do not need to enter an event key. Use Advanced: custom event key only when you control a custom source. In that case, the value must exactly match the event name sent by that source, such as funding or website_visit. Keep the Motion in Draft while testing the setup. Choose Active only when the action, permissions, approvals, and target data are ready. Use Paused when you want to stop new runs without deleting the Motion.

Send a controlled test

Connect a signal source and send one test event with a unique test company or contact. For Clay, follow Connect Clay to Lookout. After sending the signal:
  1. Open Runs, approvals & outcomes.
  2. Confirm the Motion name and signal type.
  3. Review the run status, approval status, outcome, or error.
  4. Check the related Sanka workflow before sending more rows.

Fix common issues

  • The template does not create a new Motion: the same template may already exist under Open my motions.
  • The Motion cannot be activated: configure at least one workflow action and save the graph first.
  • The signal is ignored: confirm that the source reports the selected trigger event and that all optional filters pass.
  • The run fails: open the related Sanka workflow and confirm permissions, required fields, and action configuration.
PreviousLookout docsNextConnect Clay to Lookout