How to Create Partner Journey Automation Workflow Triggers

Purpose

In this article, Allbound Administrator will learn about the elements and how to properly set up a Partner Journey Automation (PJA) Trigger. Please scroll to the end of this article to view some Trigger examples.

Introduction

Partner Journey Automation (PJA) is a reactive automation engine that smoothly onboards and educates new partners into the Allbound platform. Simple-to-use and powered by triggers and actions, PJA makes collaboration... Allbound easy. A PJA workflow consists of one trigger and can have multiple actions.

*Note: only Allbound Administrator users with the System Settings permission enabled can create new PJA workflows

What is a PJA Trigger?

As you create PJA workflows, Triggers will be especially important. A Trigger defines the action that your partner user does (or does not do) in your portal that “Triggers” your workflow action.

With Triggers, you can also add an optional filter(s) to a workflow. Applying Trigger filters allow you to focus your workflow to specific audiences or event attributes. Multiple filters can be applied to your Trigger and you can define if the filters have an “and” or “or” relationship. The list of filters is dependent on the event and therefore will differ slightly. Examples include: partner company name, specifying the name of a piece of content, Learning Track, etc., the name of a Group, etc.

Creating PJA Workflow Triggers

Setting a Trigger Definition

The first step is to set the presence or absence of an action, i.e., User has or User has not. Click on the field to expose the values and select your Trigger definition.

Setting an Event

Click the Event field to select the appropriate system action from the drop-down menu. Below is a list of events and their definition.

*Note: you may not see all of the options below in your portal as the list is based on available features and/or features in use

Registered: A user registered/created a new user account in the Allbound platform. This is only available when “User Has” is selected
Submitted a form: A user submitted a form in the portal (Example: submitted a quiz in a Learning Track)
Updated profile: A user updated a field(s) on the My Profile page and the user clicked Submit
Logged in
Registered a Company: If your portal is not CRM integrated, Allbound Administrator users can manually add a company to the portal
Registered a deal: A user registered a new deal from the Allbound portal
Updated a deal: A user made an update to an existing deal in the Allbound portal
Created MDF request: A user submitted a new MDF request from the Allbound portal
Updated MDF request: A user made an update to an existing MDF request in the Allbound portal
Completed a Learning Track: A user completed all steps related to a Learning Track
Created a Prospect Page: A user created a new Prospect Page
Passed a Quiz: A user passed a quiz based on pass/fail criteria
Co-branded content: A user downloaded a resource that was co-branded in the Allbound platform
Completed a Certification: A user completed a Learning Track with a Certification attached

Adding Filters

A Trigger requires a definition and at least one event. Adding a filter is optional and will allow you to focus your Actions on specific audiences or event attributes. The filter properties will not populate until an event is selected. The list of filters is dependent on the event and therefore will differ slightly. Filters can include values based on the user profile fields, Company Admin form fields, Deal Registration form fields, MDF Request fields, Learning Track attributes, etc.

Once you select the property, you will be able to add details specific to that property that you wish to filter by. Select Equal or Not Equals when applying exact matches or select Contains or Does not contain for a looser rule.

As an example, refer to the image above where the User Primary Company, Company Name has been selected.

Equals Kiwano: The company name is exactly Kiwano and will include only users that belong to Kiwano as their primary company
Not Equals Kiwano: Will exclude all users with a primary company that is not Kiwano
Contains Kiwano: Will include users that belong to a primary company with Kiwano in the name. For example, if I have three Kiwano companies - Kiwano North, Kiwano West, Kiwano South - this filter will include users from all three companies.
Does not contains: Will exclude users that belong to a primary company with Kiwano in the name.

Multiple filters can be applied to your Trigger and you can define if the filters have an “AND” or “OR” relationship. Click the "+" icon below your first property. You will be prompted to select the relationship indicator.

If you choose “OR,” the system will encase your filters in a gray box to illustrate the filter relationship.

If you need to change the relationship indicator, you can adjust the indicator at any time by clicking on the correct option. Continue to click the "+" icon to add more filters until you have created your Trigger. You can also delete a filter by clicking the gray "X" to the right of the filter.

To clear out all of the Trigger selections, click “Clear” at the top of the Trigger box.

NOTE: To view form fields, the field must have an API key.

Example Triggers

JOURNEY: New Partner Welcome

WORKFLOW #1: Reseller partners located in the Americas region

WORKFLOW #2: Reseller partners located in the Europe region

JOURNEY: Partner Training and Onboarding

WORKFLOW #1: Silver tier partners that have completed the first Learning Track in their onboarding curriculum.

WORKFLOW #2: Platinum tier partners that have completed the first Learning Track in their onboarding curriculum.

If you still have questions, please reach out to your Customer Success Manager or Open a Support Ticket.

Also, please refer to these articles to further learn about Partner Journey Automation:

How can we help?

How to Create Partner Journey Automation Workflow Triggers

Purpose

Introduction

What is a PJA Trigger?