# Build a mission

Sydekyks user and operator guide. Check feature availability and release-specific installation requirements.

A mission is a workflow with one trigger and the steps that follow it. Design the smallest useful outcome first, then add conditions and exception handling.

## ​Choose the trigger

The trigger answers When should this mission start? Choose an event, schedule, webhook or another trigger provided by an installed gadget.

Configure its required inputs and account. Load sample data so the builder can show the fields later steps will receive. An empty sample can mean the event has not happened yet, the filter excludes it, or the app account cannot read it.

## ​Add actions

The action answers What should happen next? Add a step, choose the gadget and action, then configure the account and fields it needs. Name steps by their purpose, such as Find supplier, Prepare review message or Write bill record.

Map values from previous steps with the data selector. Enter fixed values only when the destination or rule should stay constant. Data manipulation (https://docs.sydekyks.com/flows/using-formulas) helps transform the mapped values.

## ​Add control flow

Use a router to choose different paths, a loop to process a list, or a delay/wait step when the workflow must pause. Start with branches and loops (https://docs.sydekyks.com/flows/control-flow).

The order matters. A step can use data produced earlier in its execution path. A value inside one branch is not automatically available to a different branch.

## ​Save, test and publish

Builder edits belong to a draft. Test the trigger and each important step, inspect the results, then publish (https://docs.sydekyks.com/flows/publishing-flows) the reviewed draft. Testing may perform the action in the connected app, including sending messages or changing records.

## ​A practical checklist

- The trigger matches the event you intend to handle.

- Each app action uses the intended account and resource.

- Required fields resolve to actual values.

- Branches handle both expected and exceptional inputs.

- Repeated events do not create unwanted duplicates.

- Failures leave enough information for a person to investigate.

Use your first mission (https://docs.sydekyks.com/getting-started/first-mission) for a short walkthrough.