Environment variables
Stable configuration like host, tenant, default token, or global Metadata.
Chain Replay Turn multi-step gRPC calls
Turn multi-step gRPC calls
into replayable chains
Save login, query, create, and verification calls as a chain, then pass token, userId, traceId, and other runtime context automatically.
01Logintoken -> session.token
02GetProfileuser.id -> session.userId
03ListOrdersuses token + userId
Example chain
Login -> GetProfile -> ListOrders
Login
extract body.token -> session.token
extract body.user.id -> session.userId
GetProfile
metadata.authorization = Bearer {{session.token}}
body.userId = {{session.userId}}
ListOrders
metadata.authorization = Bearer {{session.token}}
body.userId = {{session.userId}}
What it solves
Stop copying token, userId, and traceId manually
1
Steps reference saved requestsRun a request in APIs first, save it, then compose it inside Chains.
2
Extractors write runtime variablesSources include Body, Metadata, Trailers, and Status; targets can be dot paths like session.token.
3
Reports are redacted by defaultChain runs can produce Markdown reports while masking authorization, token, password, secret, and api key fields.
Runtime model
Variable precedence during a chain run
Runtime variables move upstream response data into downstream requests, so teams stop copying token, userId, and traceId by hand.
Saved request values
Each saved request keeps its own Payload, Metadata, Auth, and transport config.
Extracted values
session.* values extracted from upstream steps are resolved before downstream sends.
Run result
Step status, duration, failure reason, observed variables, and report preview stay in the chain workbench.