Skip to main content
Execution nodes are the building blocks that come after a workflow’s trigger: they perform actions, transform data, or control the workflow. This page lists all fifteen, grouped by purpose.
Nodes that call protected services — external APIs, messaging platforms, tracking providers, or Fail Fast itself — authenticate with credentials. You choose or create the credential inside the node’s configuration.

Picking the right node

  • Start with the most specific node available: WhatsApp over HTTP Request for WhatsApp messages, Satrack over a generic call for Satrack data.
  • Reach for HTTP Request or Integrador Transporte when no dedicated node exists for your service.
  • Use Code sparingly — only when the data shape between two nodes genuinely needs custom transformation.
  • Use Switch whenever one workflow must handle several cases; it keeps the logic on the canvas where anyone can read it.

Credentials

Set up authentication for nodes that call protected services.

Triggers

The events that start a workflow in the first place.