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

  • Lookup site owner/team before sending alerts.
  • Fetch site state before policy or WAN changes.

​
Configuration Checklist

  1. Set site ID from trigger payload or upstream node output.
  2. Execute action to fetch full site metadata.
  3. Map returned fields into conditions or notifications.
  4. Use data to enrich downstream decisions.

​
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

  • Prefer small, composable actions over one large action with many responsibilities.