Build workflows
Design routes, connect nodes, work with data, and release changes with confidence.
Controllers, actions, and routes
A controller gives related APIs a shared path. Each action adds a route, an HTTP method, and a workflow. Together they determine which graph handles a request.
2 min readWork in the Flow Builder
The Flow Builder shows the nodes and connections behind an action. Use it to make the execution path easy to read, test, and maintain.
2 min readHow a workflow executes
Cloudgate resolves the incoming route, performs gateway access checks, and starts execution at the action's entry node. The graph's connections determine what happens next.
2 min readRead request data safely
Route values, query parameters, headers, and the request body enter the workflow as execution data. Validate them before using them to select records, construct requests, or change state.
2 min readKey Selectors and session values
Selectors let you reference named values using ${name}. Use stored selectors for reusable configuration and named node outputs for data that belongs to one workflow run.
2 min readSandbox and production
Cloudgate uses sandbox for development and production for released APIs. The environment selects workflow and resource configuration, but each integration still needs a deliberate isolation plan.
2 min readReview and release workflows
Workflow releases separate editable drafts from the versions clients use. Review the full behavior change, test it in sandbox, and publish the intended version through the release lifecycle.
2 min read