Why it matters
A workflow is not live as soon as you create or edit it. Testing confirms that steps receive and return the expected data, while publishing creates the version Whippy uses for future runs. Version history lets you improve an automation without changing the live version until the draft is ready.
Key Concepts
Test: Runs an individual trigger or step with sample data so you can review its input and output.
Draft Version: An editable version that is not currently used for live workflow runs.
Published Version: A saved, read-only version that can be used for workflow execution.
Current Version: The published version Whippy uses for new runs.
Validation: Checks performed before publishing to find missing or incomplete configuration.
Test Run: A workflow run started manually from a selected version.
Rollback: Making an earlier published version current again.
Test Individual Steps
Test the workflow from the beginning because later steps often depend on output from earlier steps.
Step-by-Step: Test a Step
Open Workflows and select the workflow.
Click Edit workflow if the current published version is displayed.
Open the trigger or step you want to test.
Complete the required Setup and Configure fields.
Open Test.
Run the available test.
Review the input, output, response, console output, and errors shown.
Save the step after the test returns the expected result.
Test the next step using data from the earlier step.
Testing an action can perform a real operation in the connected system. Use safe test records, channels, and recipients.
Validate Before Publishing
Whippy validates the workflow when you publish it. An incomplete trigger, missing required field, invalid branch, or unfinished step can prevent publishing.
Step-by-Step: Fix Validation Issues
Click Publish.
Read the validation message.
Find the highlighted step on the canvas.
Open the step and complete its missing configuration.
Save the step.
Repeat for every highlighted step.
Click Publish again.
Passing validation confirms that required configuration is present. It does not guarantee that credentials, external systems, or live data will always return a successful result.
Publish a Workflow
Step-by-Step: Publish a Draft
Confirm the trigger and all required steps are configured.
Test important steps with realistic sample data.
Review recipients and any steps that create, send, update, or delete data.
Click Publish.
Resolve any validation issues.
Confirm the workflow shows a published current version.
Create a controlled trigger event when practical.
Open Runs and confirm the live run completes successfully.
Publishing makes the selected draft the current version. New executions use that version; existing in-progress runs continue with the version on which they started.
Edit a Published Workflow
Published versions are preserved so their configuration can be reviewed later. Create a draft before making changes.
Step-by-Step: Create a Draft
Open the workflow.
Click Versions.
Find the published version you want to use as the starting point.
Open its actions menu.
Select Create Draft.
Confirm the draft creation.
Edit and test the draft.
Publish it when it is ready.
Only one draft can exist for a workflow at a time. If a draft already exists, Whippy may ask whether you want to replace it.
Test a Complete Version
Step-by-Step: Run a Version Test
Open Versions.
Open the actions menu for the version.
Select Test Run.
Open Runs after the test begins.
Review the run status.
Open Run Details and inspect each step.
Correct the draft and repeat if the results are not as expected.
A test run may still call external services or create data. Choose safe inputs before starting it.
Restore an Earlier Version
Step-by-Step: Make a Previous Version Current
Open Versions.
Find the published version you want to restore.
Review its date and configuration.
Open its actions menu.
Select Use this version.
Confirm the change.
Review the next workflow runs to confirm the restored behavior.
Making a version current affects future runs. It does not rewrite the history of completed runs.
Unpublish a Workflow
Open the Workflows list.
Find the workflow.
Turn off its Status toggle.
Confirm the workflow is no longer published.
Unpublishing prevents new trigger events from starting the workflow. Review any runs already in progress separately.
Tips and Best Practices
Test from left to right so later steps receive usable sample data.
Use test contacts, records, inboxes, and Slack channels.
Review every step that sends messages or changes external records.
Keep a stable published version while editing a draft.
Check Runs immediately after publishing a meaningful change.
Record the reason for major changes in the workflow name, description, or your internal change process.
Export workflow JSON before large structural changes when an additional backup is useful.
Troubleshooting
Issue | Possible Cause | Fix |
Publish is blocked | A required trigger, field, branch, or step is incomplete | Open every highlighted step, complete its configuration, and publish again |
A step test succeeds but the live run fails | Live data, credentials, or permissions differ from the test | Compare the test data with the failed run input and reconnect the account if needed |
Variables are unavailable during testing | An earlier step has no sample output | Test the earlier step first, then reopen the variable picker |
Create Draft is unavailable | A draft may already exist | Open the existing draft or replace it only after confirming it is no longer needed |
The wrong behavior is live | The incorrect published version is current | Open Versions and use Use this version on the intended published version |
New trigger events do not start runs | The workflow may be unpublished | Confirm the workflow status and publish the intended version |