When you use the Test Trigger option in a Workflow, it helps you get into the workflow and past the trigger node. From then on, the workflow treats you as a regular user.
Helpful Tip: If you have filters that check for data fields on the user's profile (using the Contact Property category) be sure those fields exist on your own user profile.
There are two main ways to test a workflow.
Testing While Workflow is Enabled
If you want a larger number of "test users" within your company to test the workflow, or if you want to use your email address to test the workflow to be triggered as it would if it was live, follow the steps below:
Add a filter after the green Trigger Node that checks for whatever field separates the test users from the regular users. If you're testing within your company, you could look at the domain of your email addresses.
The filter in the node would ensure only internal email addresses will go through the subsequent steps in the workflow (replace "@companyname.com" with your company's email domain):
Then, you can turn the workflow "On" if it's not already on:
Testing While Workflow is Disabled
If you want to test the workflow without turning it on, you can use the "Send Test Trigger" button. This will also work when the workflow is enabled.
If the trigger node, which is always green, requires certain fields in a user's profile or triggering event for the workflow to trigger, you'll need to enter those fields into the JSON editor before sending the actual trigger:
For example, if a trigger node was for users who made a large purchase, the trigger node would look like this:
Note that if the custom event has name "X" and the event data field name is "X.Y", you do not need to repeat "X" in the trigger event data field JSON - just "Y" will suffice.
Then, when entering data for the "Send Test Trigger" button, you would need to fill in the appropriate fields in text editor:
Note that you only need to enter the dataFields value from the track request. Email, eventName and createdAt will automatically be provided for you.
The fields you include in the JSON box do not get added to your user profile, they only exist as part of the test trigger.
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.