How do I build my first Whippy workflow?

Last updated: November 5, 2026

Build your first Whippy workflow by planning the trigger and outcome, configuring one trigger, adding steps from left to right, testing each step, and publishing only after validation passes.

Before you start

  • Decide what event should start the workflow.

  • Define the final outcome the workflow should produce.

  • Identify what data is required to reach that outcome.

  • Identify which steps may send messages, change records, or call external services.

Steps

  1. Open Workflows.

  2. Click Add workflow.

  3. Enter a name that describes the trigger and outcome.

  4. Add a short description.

  5. Click Add to open the workflow editor.

  6. Click the empty trigger slot and choose a trigger type.

  7. Complete the trigger setup and configuration.

  8. Open Test and generate or load representative sample data.

  9. Add the next step after the trigger.

  10. Configure the step, insert variables, and test it with safe data.

  11. Continue building from left to right, testing each step before adding the next one.

  12. Add filters, paths, loops, waits, or error handling after the main path works.

  13. Review the canvas for missing configuration, incorrect paths, credentials, and test destinations.

  14. Click Publish, resolve any validation messages, then trigger a controlled live event if practical.

  15. Open Runs and confirm the run completes with the intended result.

Tips

  • Build the smallest useful workflow first.

  • Test from left to right.

  • Use clear, outcome-based workflow and step names.

  • Use Formatter before Code Step when a supported preset is sufficient.

  • Review the first live runs immediately after publishing.

Troubleshooting

  • If the expected step is unavailable, choose another location or add it outside a loop, wait, or path context.

  • If variables are missing, test earlier steps, then reopen the variable picker.

  • If publishing fails, open every highlighted step and complete its configuration.

  • If a copied branch behaves incorrectly, review and retest every copied step.