Thyme Flow
Thyme Flow runs TypeScript automation that reads blockchain or off-chain data, decides whether work is needed, and returns contract calls. Flow executes those calls through the selected account, then records the outcome, logs, and persistent state.
The public packages retain their names: @thyme-labs/sdk, @thyme-labs/cli, and the thyme command. API routes and scope names containing functions also remain unchanged.
What you can build
- Scheduled contract maintenance, reward claims, and condition-based updates.
- Webhook-driven workflows with validated arguments and idempotent invocation.
- Stateful polling with a cursor or checkpoint carried between runs.
- Release pipelines using immutable uploaded versions, management commands, and the HTTP API.
Flow supplies execution and scheduling; your task supplies the decision logic. Tasks return calls instead of receiving a transaction-signing key.
How the products fit together
| Product | Responsibility |
|---|---|
| Flow | Task execution, schedules, profiles, state, secrets, and monitoring. |
| Lift | Transaction sponsorship. Flow's Roles profiles use managed Lift integrations. |
| Gate | RPC access and routing; separate from a task's authoring and scheduling contract. |
| SDK | Task definitions, typed context, validation, lifecycle callbacks, and packaging helpers. |
| CLI | Local development, uploads, management operations, and Roles verification. |
Start here
Follow the quickstart, then read the task model, profiles, and permission manifests. For deployment automation, use the management CLI or API reference. To have a coding agent do this work, copy the Flow prompt.
This documentation describes the current implementation. A feature or chain must also be enabled on your deployment; the development rollout does not imply universal mainnet availability.