Workflow Guides: Overview
These guides cover the building blocks you'll combine to build a CRE workflow: how to start one with a trigger, how to read and write onchain data, how to call external APIs, and how to handle supporting concerns like secrets, time, and randomness. Guides are written for both Go and TypeScript; switch languages with the selector at the top of each page.
If you haven't built a workflow yet, start with Getting Started first.
Building a confidential workflow?
The guides below all run your workflow's logic on Workflow DON nodes, the default for CRE—visible in principle to node operators. If any part of your workflow's decision logic needs to stay hidden from node operators, you want a Confidential Workflow instead: a distinct workflow type that runs inside a secure enclave.
Triggers and API calls
| Guide | What you'll learn |
|---|---|
| Triggers | Choose and configure a Cron, EVM Log, or HTTP trigger to start your workflow. |
| API Interactions | Make GET and POST requests to external APIs, submit reports over HTTP, and verify them offchain. |
| Confidential API Interactions | Make a single outbound API call with secrets injected and the request processed inside a secure enclave. |
Onchain interactions
| Guide | What you'll learn |
|---|---|
| EVM Chain Interactions | Generate contract bindings, read onchain state, and write consensus-verified reports to EVM chains. |
| Solana Chain Interactions | Generate Anchor bindings and write consensus-verified workflow results to Solana programs. |
Workflow mechanics
| Guide | What you'll learn |
|---|---|
| Secrets | Manage API keys and credentials safely, in simulation and in deployed workflows. |
| Using Time in Workflows | Get a deterministic, consensus-safe timestamp with runtime.now(). |
| Using Randomness in Workflows | Generate random numbers that stay consistent across nodes so consensus still holds. |