Build First Action

Use this quick path to create your first Action.

This guide is optimized for a first successful result, not for building a perfect Action Flow on day one.

1) Create the Action

• Open Studio.
• Create a new Action.
• Give it a clear name and short description.

Naming tip:

• Prefer outcome-oriented names, for example Extract Invoice Header instead of Test Action 1.

2) Add Initial Steps

• Add a first step to process your input.
• Add one follow-up step to produce a final result.
• Keep the initial Action Flow small.

Good starting pattern:

1. Input processing step (parse/read/normalize).
2. Core reasoning step (LLM general or agent).
3. Optional formatting/validation step.

3) Configure Inputs and Tools

• Add required input types.
• Attach only the tools needed for the first use case.

Avoid adding every possible tool early. Fewer dependencies make debugging easier.

4) Run a Test Run

• Run the Action manually.
• Verify output and inspect run logs.

When reviewing the run, focus on:

• whether output format matches your target,
• where uncertainty or errors appear,
• and whether each step has a clear, useful output.

5) Iterate

• Adjust prompts and settings.
• Re-run with varied inputs.
• Add branching and validation only when needed.

First-Week Checklist

• Action has a clear purpose and owner.
• Step names are understandable without extra context.
• Sample runs include both successful and edge-case inputs.
• Known limitations are documented in the Action description.

A small, dependable Action is a better starting point than a large, fragile one.

---