Cloudgate glossary
On this page
Use this reference when moving between the Hub, workflow tools, and application development. Some API and MCP names differ from the labels shown in the interface.
Workflows and execution#
| Term | Meaning |
|---|---|
| Tenant / workspace | The Cloudgate account context containing your team's configuration and resources. |
| Controller / project | A group of actions with a common URL path. MCP tools often call it a project. |
| Action / endpoint | An HTTP method and route backed by a workflow. MCP tools often call it an endpoint. |
| Workflow | The executable graph for an action. |
| Node | One operation in that graph, such as a Function, HTTP Request, or Database step. |
| Entry node | The first node executed for an action. |
| Session | The execution context for one workflow run. |
| Session key | A value available during execution, including named node results. |
| Key Selector | A named value referenced with ${name}. Stored selectors can have sandbox and production values. |
| Action Log | A record of a gateway request, not an action definition. |
| HTTP Request log | A record of an outbound request made during execution. |
Environments and releases#
Sandbox uses /sbx/ routes for development. Production uses /prod/ routes and released workflow configuration. A draft is editable work. A version is a saved workflow snapshot. A release records a candidate's review and publication lifecycle.
A schedule starts an action later with a stored body. A Schedule node creates or updates such a schedule while another workflow runs. A template is a reusable starting point; it does not automatically configure every resource in the destination workspace.
Apps and identity#
Web Builder creates pages from visual widgets. Code Editor / Web App Coder works with app source. The SDK connects a coded app to Cloudgate services and platform features.
App users sign in to your application through the Identity Provider (IdP). Account users administer the Cloudgate workspace. Their roles and permissions are managed separately.
CORS controls which browser origins can call gateway APIs. Origin Validator controls country and IP access. API credentials identify an integration; an IdP bearer token identifies an app-user session.
Need to investigate a problem? Start with troubleshooting