After you create a Workflow, you can test it, launch it, run it by hand on a list of records, check each time it ran, and A/B test it.
Test a Workflow
Before you set it live, we recommend testing it for a single customer - usually yourself or a coworker. We'll add another filter:
- Locate the Test workflow button.
- Choose an active customer to start the test on. Click start test. This kicks off the workflow and performs all action steps. If you do not want the actions be applied on a real customer use a test customer or your own account.
- The workflow will show the runs tab, including what happened to the test run. You can also check the customers page to validate that the new customer record looks as expected. If you have access to the test user's account you can also login to the Subscription Manager.
- Launch the Workflow
Test executions honor the filters setup on the trigger. So a user's account must match the filter criteria to perform the actions. If you want to test the actions alone you can temporarily remove filters.
For a Workflow that uses Manual Execution, test by running it on a single record with raw input before you run the full list. For bulk cancellations, test only on a subscription you own, because cancellation emails still send.
Run a Workflow manually
Some Workflows use the Manual Execution trigger. They run once, on records you provide, when you click Execute. Use them for one-off bulk changes, like moving a batch of order dates or cancelling a group of subscriptions.
Recipes that use Manual Execution run against records you supply. There are two ways to provide them:
- Raw input — paste records directly into the Workflow. Best for a handful of records.
- CSV upload — upload a file. Best for larger changes, up to 1,000 records.
Either way, your column header has to exactly match one of the record types Ordergroove recognizes: order, subscription, item, customer, product, payment, or shipping address. Use order, not order ID — a header that doesn't match won't link.
Which header you need depends on the action the recipe takes. If the action operates on a subscription, provide subscription records; if it operates on an order, provide order records. Workflows links your data to the action automatically when the header matches. If it can't, the action node will prompt you to connect a node that provides the record type it needs, and you can connect it yourself.
You'll still pull the IDs themselves from your reports in Ordergroove before you build the Workflow.
Monitor Workflow executions
Each time a Workflow runs, it records an execution. Open the Workflow and go to the Runs tab to see which record it ran on and whether each action succeeded. Use the filters to find any that failed. The Workflow also shows real-time reporting counts in the Activity tab.
A/B test a Workflow
Split subscribers between two versions of a Workflow to see which works better, such as a free gift against a discount. Each subscriber stays in one branch. Results show cancellations within 24 hours and overall, next-order retention, orders retained, revenue and LTR per subscriber.
While an A/B test is running, Workflow and step names are locked.
Edit, rename, pause or delete a Workflow
To change a live Workflow, navigate to the Build tab and make your edits. Hit Save & Publish to push the changes live. To pause a workflow click on the Live button and select 'Pause'. Workflows can be renamed in the workflow canvas header. To delete a workflow choose the more menu in the top right of the canvas and select 'Delete'.