Node reference
Choose the right node and understand its inputs, outputs, and execution behavior.
Choose a workflow node
Each node performs one operation. Start with the smallest set needed for your workflow, then connect the execution paths and name the results that later steps will use.
2 min readFunction node
Use a Function node to validate input, transform JSON, calculate a value, or prepare the final API response. Cloudgate executes the node's Python script and stores its returned result under the node name.
2 min readHTTP Request node
Use an HTTP Request node to call an external service from a workflow. Configure the method, URL, headers, and input body, then pass the named result to later nodes.
2 min readCondition and Decision nodes
Use a Condition for one boolean choice and a Decision for ordered routing rules. Both change which path executes, so test every outcome with representative input.
2 min readDatabase node
A Database node executes SQL against its configured database and makes the result available to later workflow steps. Choose the environment binding and query contract before adding it to a live path.
2 min readSchedule node and scheduled jobs
Use a normal schedule when timing and inputs are known in advance. Use a Schedule node when another workflow must determine those inputs at runtime.
2 min readSelector node
A Selector node writes a value to a stored Key Selector while a workflow executes. Its main use is a dedicated scheduled refresh flow that keeps a shared service token current.
2 min readWebSockets and workflow messages
Use a WebSocket resource and node to push workflow events to connected clients. This is useful for progress updates, live dashboards, and notifications that should arrive without polling.
2 min readIdentity nodes
Identity nodes let a workflow authorize an app user and perform supported identity operations. Put authorization before business reads or writes and use its result as the trusted user identity.
2 min readIntegration and specialized nodes
The node library includes configured service integrations as well as core workflow nodes. A library entry provides a starting configuration; its account, input, and external behavior still need review.
2 min read