How do I choose and configure workflow action steps?

Last updated: November 5, 2026

Action steps perform the work in a Whippy workflow after the trigger runs. Choose the simplest action type that can complete the required operation.

Before you start

  • Test the trigger or previous step so variables are available.

  • Know whether the step needs to transform data, call an API, run custom logic, or use a connected app.

  • Use safe test records, recipients, or channels for any action that can modify data or send messages.

Action types

  • Formatter: Use for supported parsing, cleaning, formatting, and normalization.

  • App Step: Use when a native integration already provides the operation.

  • HTTP Request: Use when a service has an API but no suitable app action.

  • Code Step: Use for focused custom processing that cannot be expressed another way.

Steps

  1. Add a step after the trigger or previous step.

  2. Browse Apps, Actions, or other available step categories.

  3. Select the action type you need.

  4. Choose or connect the account or credential if required.

  5. Complete the step-specific configuration.

  6. Insert variables from previous steps using the variable picker.

  7. Open Test.

  8. Run the action with safe test data.

  9. Review the response, output, console output, and errors.

  10. Save the step.

  11. Use the action output in later steps when needed.

Tips

  • Give each action a clear name describing its outcome.

  • Keep Code Steps small and use Formatter for supported transformations.

  • Prefer supported app actions over custom HTTP requests.

  • Use least-privilege credentials with access only to required records and actions.

  • Never expose secrets in step names, descriptions, logs, or sample data.

Troubleshooting

  • If an HTTP request fails, compare the method, URL, authentication, headers, and body with the API documentation.

  • If a Code Step returns no usable data, inspect inputs and return a predictable object.

  • If Formatter fails, check that the source value matches the selected preset.

  • If an app action is unauthorized, reconnect the account and confirm external permissions.

  • If a later step cannot find output data, test the action and select the field again from the variable picker.