Create your first automation

An automation combines a signal with a sequence of steps. Start with a manual test and a Log action so no external service is required.

Build the example

1. Create a test project and add an automation in the Automations workspace.
2. Give it a clear name, such as Hello world.
3. Select a Timer signal, leave Enabled off, and add a Log action to its sequence. You will start this example with Test, so the timer does not need to run live.
4. Set the message to Hello world!.
5. Select File → Save (Ctrl+S) to apply the definition to Core and write the test project.
6. Open Test Data if you want a controlled event payload, then select Test.
7. Inspect Logs and the corresponding entry in Runs.
8. Save again after any further edits. Leave Enabled off until you intend to use the live signal.

Understand the result

Test runs the definition already applied in Core with your selected test data. It does not apply the sequence currently waiting in the Editor's draft. After changing the Log message, save before testing that change.

The selected run completed successfully, and Logs contains Hello world!. A later edit does not replace this run's captured definition.

Testing an automation is separate from enabling it for live signals. Configure and enable the real signal only after the controlled test behaves as expected.

If the result is missing

Check the Core connection, validation errors and pending edits. Select the correct run in Runs and inspect the step result. A failed or skipped step is different from a signal that never started a run.

Read Editing, Apply and Save before building a longer sequence.