Create Workflow
Create a workflow that combines HTTP calls and on-chain operations

Unique identifier for this workflow (lowercase, hyphens only)

Input Variables
Define the parameters this workflow accepts

Input Variables

Define the inputs that AI agents will provide when calling this workflow

No variables defined. Click "Add Variable" to define workflow inputs.
Usage: Reference variables in steps using $.input.variableName
Workflow Steps
Define the sequence of HTTP calls and on-chain operations
1

Key to store step result under $.steps.*

Use an existing API proxy

Map input variables to request body. Use $.input.varName for substitution.

Output Mapping
Map step outputs to workflow result fields

Output Mapping

Define what data to return when the workflow completes

No outputs defined. Add output mappings to specify what the workflow returns.
=

Expression Reference:

  • $.input.varName - Input variable
  • $.steps.stepId.output - Step output
  • $.steps.stepId.output.field - Nested field
  • $.wallet - User's wallet address
  • $.chainId - Current chain ID
Scope Configuration
Configure allowed contract addresses for dynamic targets in your workflow

Dynamic Target Contracts

When your workflow calls contracts with addresses resolved at runtime (like DEX aggregators from an API), you must specify which contract addresses are allowed. These addresses will be included in the session key permissions.

Add DEX aggregator, router, or other contract addresses that your workflow may call

No allowed addresses configured. Add addresses for any dynamic contract calls.