Workflow node types
Each workflow node has one focused responsibility. Select a node to open its configuration. Give it a unique, business-readable name because that name appears in mappings, tests, and debug traces.
| Node | Use it to | Key choices |
|---|---|---|
| Input | Expose the workflow request | Input Data Model |
| Output | Assemble the workflow response | Output mappings |
| Rule | Execute a Decision Table, Ruleset, or Workflow | HubItem and version |
| Condition | Select one branch | Ordered groups and default |
| Scorecard | Calculate a numeric score | Scorecard and version |
| Assign | Set or copy values | Target, source/value, condition |
| Coding | Calculate or transform with JavaScript | Reusable version or inline logic where available |
| Local Variables | Initialize execution-only state | Names, types, initial values |
| Foreach | Process every collection entry | Collection and per-item path |
| Find | Return the first matching entry | Conditions and sorting |
| Filter | Return all matching entries | Conditions |
| HTTP Client | Call a reusable HTTP request | Client version and request mapping |
| Salesforce Data | Query or modify Salesforce records | Connector, object, operation, payload |
| Salesforce Event Trigger | Start from a Platform Event | Connector, event topic, payload model |
| Salesforce Event Publisher | Send a Platform Event | Connector, event topic, payload mapping |
| Kafka Trigger | Start from a Kafka record | Connector, topic, offset, record mapping |
| Kafka Publisher | Publish a Kafka record | Connector, topic, key, headers, payload |
| Sticky Note | Document the graph | Explanatory text only |
A useful selection test
- If the value only moves between two nodes, use an edge mapping.
- If a value must be copied or set, use Assign.
- If several business conditions mutate data, use a Ruleset through Rule.
- If a transparent points model is needed, use Scorecard.
- If a deterministic algorithm is clearer in code, use Coding.
- If each or some collection entries must be handled, use Foreach/Find/Filter.
- If data crosses the DecisionHub boundary, use HTTP Client or a connector node.
Only nodes offered by the Workflow Elements palette for your plan are deployable. Validate the graph after importing or editing an older workflow.