Build your first workflow

A workflow is one TypeScript program. It can use ordinary variables, loops, branches, arrays, closures, and native bigint, while txcast effects create the durable boundaries where the program waits for chain data, HTTP data, people, time, notifications, or wallet transactions.

Before you begin

You need a seated organisation membership. A transaction workflow also needs an organisation execution account. The fastest authoring path is an AI agent with a newly authorised v2 credential; the browser editor remains available as an escape hatch.

1. Author and save

1. Open Workflows and create a workflow, or ask an authorised agent to call create_workflow.
2. Describe the operation, inputs, execution account, networks, transaction targets, HTTP hosts, and people who may respond.
3. Review the generated TypeScript and capability envelope.
4. Validate the source, then select Save to create the current immutable version.

Every effect call needs a stable key and a positive maxResultBytes. The capability envelope is enforced again when the run starts and whenever an effect is registered.

2. Start a run

1. Open the current revision.
2. Fill its schema-driven input form and correct validation errors.
3. Select Start run.

Run creation resolves declared references and freezes the revision, input, and execution authority in one operation.

3. Review effects and sign

The run graph shows concrete effect occurrences. Source and timer effects may resolve automatically. Human effects wait for an eligible person. Transaction effects always require an eligible person to review and interact with a wallet:

• a Safe list is proposed and executed as one atomic batch;
• an EOA list is presented one transaction at a time, in order.

txcast verifies submitted hashes and receipts. It never holds wallet keys and an MCP agent cannot answer a human effect or sign.

Next, learn about TypeScript inputs and control flow or transaction effects.