NEW / 1.4A clearer view of every handoff →

Docs / Getting started

Your first workflow,
in five steps.

Use customer onboarding to learn the shape of a clear handoff. You can explore the sample without connecting any accounts.

Before you begin: choose a recurring process with a clear starting signal and one useful outcome. This guide uses fictional Northstar Studio data.
  1. 01

    Name the outcome.

    “A confirmed customer kickoff” is a stronger target than “onboarding.” It tells the receiving team what completion means.

  2. 02

    Describe the starting signal.

    For the sample recipe, a signed contract is the signal. In the static demo this is a descriptive field, not a live event listener.

  3. 03

    Choose the required context.

    Ask for the company name, primary contact, source contract, and the customer’s first goal. Keep optional notes separate.

  4. 04

    Name the next owner.

    Avery reviews the intake and assigns the delivery owner. Choose a backup for exceptions and agree on an acknowledgment.

  5. 05

    Test the exception path.

    Use a fictional request with missing information. Confirm that someone is responsible for resolving the gap before it moves forward.

A sample definition.

Workflow: Customer onboarding
Trigger: A signed contract is ready for review
Required context: Company, contact, contract link, goal
Owner: Avery Chen
Normal path: Review → assign kickoff → notify → acknowledge
Exception: Missing information → manual review
Done: Delivery owner confirms the kickoff brief

Ready to explore?

Open the sample record, then change one detail that makes the handoff more useful for your own team. Keep the sample fictional while you are testing.

Open the sample workspace ↗Read the complete recipe