This document describes ways to test a workflow:
Testing while a workflow is enabled
If you want a larger number of test users within your company to test a workflow, or if you want to use your email address to test the workflow as if it were enabled, follow these steps:
After the workflow's trigger node, add a filter node.
The filter should check for whatever field separates the test users from the regular users.
For example, if you're testing within your company, you could look at the domain of your email addresses. In this case, the filter would ensure that only internal email addresses go through the subsequent steps in the workflow (replace
@companyname.comwith your company's email domain):
Enable the workflow:
Testing while a workflow is disabled
Use the Send Test Trigger button to test a disabled workflow (this button also works for enabled workflows):
If your workflow has filter nodes that use Contact Property values to check for field's on a user's profile, make sure those fields exist on your own user profile.
Click the Send Test Trigger button to bring up a window that can be used to enter test data fields.
If the workflow's trigger node requires certain fields in a user's profile or triggering event for the workflow to trigger, enter those fields into the JSON editor before sending the trigger:
For example, a trigger node looking for users who have made a large purchase might read as follows:
If the custom event has name
customEventNameand the data field name is
customEventName.fieldName, you do not need to repeat
customEventNamein the trigger event data field JSON; just
The event data required for this test trigger would be:
You only need to enter the
dataFieldsvalue from the track request.
createdAtwill be provided automatically.
The fields you include in the JSON box do not get added to your user profile; they exist only as part of the test trigger.
Sending a test trigger for a disabled workflow will still send the campaign.
Sometimes your test trigger will go down a path that you may not expect. Remember that the filters will be checking information that lives on your profile! Check your user profile in the project you're in to ensure it has the correct content to match the filters for the desired path.
To visually see what path you're going down, add some short delays to points where your profile might otherwise exit the workflow.