Skip to main content
Actions do the actual work in a workflow: API calls, transformations, notifications, flow control, and integrations. Use this action when your workflow needs to perform an operation, call an external service, or transform data for downstream nodes.

​
When To Use

  • Run remote diagnostics on an external appliance.
  • Execute controlled remediation commands during incidents.

​
Configuration Checklist

  1. Set SSH host, port, auth method, and command list.
  2. Inject context values carefully into commands.
  3. Capture stdout/stderr and evaluate command exit behavior.
  4. Branch to rollback/escalation steps when command execution fails.

​
Inputs

  • Required node.data metadata: uiId, componentId, and operation (for actions that define an operation).
  • Action-specific configuration fields from the node editor.
  • Upstream context values from triggers or previous nodes (for example trigger.* or prior action outputs).

​
Outputs

  • Adds action result data to the workflow context for downstream nodes.
  • May produce external side effects (API updates, notifications, scripts, SSH commands, etc.).
  • Can emit structured values consumed by conditions or subsequent actions.

​
Failure Modes

  • Missing required configuration or invalid parameter values.
  • Missing/invalid context variable references from upstream nodes.
  • External dependency failures (HTTP errors, auth failures, timeouts, rate limits).
  • Payload validation/parsing errors during request or response handling.

​
Best Practices

  • Treat SSH commands as high-risk side effects and test on non-prod first.