Skip to main content

Workflows

About Workflows

Workflows allow you to automate manual actions that are triggered by an event and based on a set of if / then conditions. Workflows can be set up in the Persona DashboardPlease see below for a couple examples of commonly used Workflows.

Example 1

You could set up a Workflow that is triggered when an inquiry is completed (an event), where the inquiry would be automatically declined (an automated action) if the inquiry's IP address matches an IP address on a specified List (a condition).

Example 2

Let's say you'd like to mark inquiries for review where the individual who completed the inquiry is under 18. You could set up a Workflow that is triggered when an inquiry is completed (an event), where the inquiry would be automatically marked for review (an automated action) if the individual who completed the inquiry submitted an ID with a birthday that makes them under 18 years of age (a condition).

The use case for Workflows

Workflows are a great way to automate manual decisions and decrease the amount of time spent in manual reviews. Workflows can also be combined with Lists to automate actions / decisions for inquiries automatically flagged as matching those on a list. They can also help you test various configurations within your template.

Example: You may want to test how often a certain verification check is triggered for the government ID verification. If you want to test this out, you could create a workflow that is triggered on the event inquiry.complete, where the inquiry is marked for review (an automated action), and a specific verification check failed (a condition).

Creating your Workflows

You can create a Workflow by going to the Workflows section of your Dashboard.

  1. On the top right side of the Workflows page, click the button "Add new workflow."
  2. Name your Workflow.
  3. Select an event that will trigger the Workflow.
  4. Add a new route (each route is an if/then condition) and name your new route.
  5. Select "If inquiry" and add one or more IF condition(s) (e.g. list_match contains). If you do select more than one IF condition in the same route, please note that all conditions will have to be met in order for the route to be matched.
  6. Select "Then" and add your desired action (e.g. decline).
  7. If needed, add additional routes (repeat steps 4-6).
  8. Check that the route "Everything else" matches your expected behavior for any inquiries that don't match any of the other routes.
  9. Save draft and publish your Workflow. A published Workflow is not yet active but allows your teammates to check and edit the Workflow.
  10. When you're ready to start running your Workflow, press the play icon.

Events, conditions, and actions that are supported by Workflows

The following is a list of events, conditions and actions we currently support. Since Workflows have broad potential application, we will continue to expand the list of support events, conditions and actions based on your feedback. Please note that we're adding new conditions to our Workflows frequently. It's possible that this list is not exhaustive with respect to the conditions that Workflows offer. Please reach out to us at support@withpersona.com if you'd like to request a new condition be added to Workflows, we'd be happy to work with you!

Supported events

These event types include inquiry events, report events, and case events (learn more about Cases).

  • inquiry.completed
  • inquiry.expired
  • inquiry.failed
  • report/adverse-media.matched
  • report/adverse-media.ready
  • report/comply-advantage-search.ready
  • report/email-address.ready
  • report/phone-number.ready
  • report/profile.ready
  • report/sec-action-lookup.ready
  • report/social-media.ready
  • report/synthetic.ready
  • report/watchlist.matched
  • report/watchlist.ready
  • case.resolved
  • case.created

Supported actions

These are a list of actions that you can take on the inquiry associated with the relevant event. 

  • Add tag (on inquiry)
  • Add tag on account
  • Decline (inquiry)
  • Approve (inquiry)
  • Do nothing (to inquiry status)
  • Mark (inquiry) for review
  • Remove tag (on inquiry)
  • Remove tag on account
  • Create and resolve case
  • Create case

Supported criteria

This list may not be exhaustive, as we're constantly adding new criteria to our Workflows. These criteria are related to the inquiry, inquiries associated with the account, and reports that are run.

  • Country: the country of residence of the individual, as determined by the information provided during the inquiry.
  • Selected country: the country of residence of the individual, as reported by the individual.
  • Country from device - the country the individual's device is located in.
  • Country comparison - whether the device is in the user's country of residence, as determined by the information provided during the inquiry.
  • US state description - the state of residence of an individual in the US, as determined by the information provided during the inquiry.
  • Selfie similarity score - score representing similarity between the submitted selfie and the face on the ID.
  • Selfie liveness score - score representing confidence in the liveness of the submitted selfie.
  • Government ID confidence score - score representing confidence in the validity of the submitted ID.
  • Liveness confidence score - same as selfie liveness score.
  • Number of failed verification attempts - within the inquiry, the number of failed verification attempts.
  • Filled properties - properties that were filled on this inquiry. Eg. name_first, name_last, etc
  • List matches - lists the individual has matched against.
  • Age - age of the individual.
  • Completed at - completion time of the inquiry.
  • Created at - creation time of the inquiry.
  • Template - the template that the inquiry is from.
  • Government ID expired - whether or not an expired ID was submitted.
  • Government ID type - the type of government ID submitted, for example, driver license, as collected from information provided during the inquiry.
  • Inquiry has documents - whether or not the inquiry has supplementary documents submitted.
  • Inquiry has started - whether or not the inquiry has been started.
  • Account property matches - account properties the inquiry has matched against.
  • Account tags - tags on the related account.
  • Failed verification checks - checks the inquiry has failed.
  • Government ID tags - tagged properties on government ID.
  • Account name matches - checks if the names on an account are found among the names collected from the inquiry.
  • Capture method - matches on the capture methods used by the individual during the inquiry.
  • Social security number digit count - the number of digits in the social security number collected from the inquiry.
  • Threat level - threat rating of the individual's device.
  • Proxy detected - whether the individual used a proxy while completing the inquiry.
  • Tor detected - whether the individual used Tor while completing the inquiry.
  • Last two verifications geolocation delta - distance in meters between the locations of the last two verifications during the inquiry.
  • Geolocation to residency delta - distance in meters from the individual's residence to the device's location.
  • Device count- number of unique devices associated with the inquiry.
  • Session count - number of unique sessions associated with the inquiry.
  • Browser count - number of unique browsers associated with the inquiry.
  • IP address count - number of unique IP addresses associated with the inquiry.
  • Inquiry field value - value of a field on the inquiry.
  • Random sample - randomly selects a percentage of items.
  • Passed database verification count - number of passed database verifications on the inquiry.
  • Failed database verification count - number of failed database verifications on the inquiry.
  • Abuse score - the score of an account with synthetic or other first party fraud.
  • First party synthetic score - the score of an account with a true name and DOB but a fictitious SSN.
  • Third party synthetic score - the score of an account that consists of a name, DOB, and SSN that describe a fictitious person.
  • Match found - whether or not there was a match on a watchlist.
  • Phone type - inferred type of phone according to phone records.
  • Phone carrier - inferred phone carrier according to phone records.
  • Phone number risk score - risk score of phone number based on properties of device and of use.
  • Phone number risk recommendation - risk recommendation of phone number based on properties of device and of use.
  • Countries - countries recorded on the adverse media report report.
  • Adverse media types - adverse media types on this report.
  • Adverse media relevance types - relevance types on this report.
  • Email address reputation - reputation of an email address associated with email risk report.
  • Email address domain reputation - reputation of an email address domain associated with email risk report.
  • Email address first seen - the number of days since the email address was first seen according to the email risk report.
  • Email address last seen - the number of days since the email address was last seen according to the email risk report.
  • Email address domain created - the number of days since the email domain was created according to the email risk report.
  • Email address reference count - the number of references the email address has according to the email risk report.
  • Email address domain exists - whether or not the email address domain exists according to the email risk report.
  • Email address blacklisted - whether or not the email address is blacklisted according to the email risk report.
  • Email address deliverable - whether or not the email address is deliverable according to the email risk report.
  • Email address disposable - whether or not the email address is disposable according to the email risk report.
  • Email address free provider - whether or not the email address is a free provider according to the email risk report.
  • Email address spam - whether or not the email address is spam according to the email risk report.
  • Email address suspicious - whether or not the email address is suspicious according to the email risk report.
  • Email address valid mx- whether or not the email address has a valid MX record according to the email risk report.
  • Email address domain - the email address domain according to the email risk report.
  • Related inquiry account property matches - account properties the related inquiry has matched against.
  • Related inquiry age - age recorded on the related inquiry.
  • Related inquiry browser count - number of unique browsers associated with the related inquiry.
  • Related inquiry capture method - matches on the capture methods used by the individual during the related inquiry.
  • Related inquiry country - country recorded on the inquiry.
  • Related inquiry country comparison - whether the device is in the user's country of residence, as determined by the information provided during the related inquiry.
  • Related inquiry country from device - the country the individual's device is located in.
  • Related inquiry document similarity score -score representing similarity between the submitted selfie and the face on the ID on the related inquiry.
  • Related inquiry failed verification checks - checks the related inquiry has failed.
  • Related inquiry failed verification attempts - number of failed verification attempts on the related inquiry.
  • Related inquiry field value - value of a field on the related inquiry.
  • Related inquiry filled properties - properties that were filled on the related inquiry. Eg. name_first, name_last, etc
  • Related inquiry's geolocation to residency delta - distance in meters from the individual's residence to the device's location as determined in the related inquiry.
  • Related inquiry government ID expired - whether or not an expired ID was submitted on the related inquiry.
  • Related inquiry government ID tags - tagged properties on the related inquiry's government ID.
  • Related inquiry ID classes - the type of government ID submitted, for example, driver license, as collected from information provided during the inquiry.
  • Related inquiry IP address count - number of unique IP addresses associated with the related inquiry.
  • Related inquiry last two verifications geolocation delta - distance in meters between the locations of the last two verifications during the related inquiry.
  • Related inquiry list matches - list matches on the related inquiry.
  • Related inquiry proxy detected - whether the individual used a proxy while completing the related inquiry.
  • Related inquiry selected country - the country of residence of the individual, as reported by the individual, on the inquiry related to this report.
  • Related inquiry device count - number of unique devices associated with the related inquiry.
  • Related inquiry session count - number of unique sessions associated with the related inquiry.
  • Related inquiry social security number digit count - the number of digits in the social security number collected from the related inquiry.
  • Related inquiry status - status of the inquiry related to this report.
  • Related inquiry template - the template that the related inquiry is from.
  • Related inquiry threat level - threat rating of the individual's device.
  • Related inquiry Tor detected - whether the individual used Tor while completing the related inquiry.
  • Related inquiry US state - US state recorded on the inquiry related to this report.
  • Related account tags - tags associated with the related account.
  • Case template - case template associated with this case.
  • Case resolution - resolution of this case.

FAQs

What happens if I set up a Workflow with multiple if / then conditions?

The Workflow will process each IF / THEN condition sequentially. For example, if you want to create a Workflow that will first decline all inquiries that match the List: Blocked IP Addresses, then approve all inquires that match the List: Allowed IP Addresses, and then approve all other inquiries that don't match the lists, you'd want to build each route separately, in the following order:

  • Decline all inquiries that match the List: Blocked IP Addresses; and
  • Approve all inquiries that match the List: Allowed IP Addresses; and
  • Approve all other inquiries

Let's say you'd like the second rule to override the first in the event the IP address appears on both lists. In this example, you will want to set up the Workflow to first Approve all inquiries on the Allowed list before Declining inquiries on the Blocked list. If one route is hit, the consequent routes will not continue to run, so you need to make sure your workflow routes are set up in order of priority based on your rules. 

Are Workflows retroactive?

Workflows are not retroactive for inquiries created before the Workflow was started. Workflows will only impact inquiries created after the Workflow starts running.

Can I have multiple Workflows that are triggered on the same event?

Yes, you can have multiple workflows that are triggered on the same event. However, your use case is important to how you should most effectively set up your workflows. 

Let's say you have two different templates that your organization uses for two different reasons. You may want to build one Workflow that is only associated with one template. In this case, you'll specify the template in the trigger criteria section of the Workflow creation, after you specify the trigger event.

helpcenter_workflows.png

What this will do is ensure that the Workflow you've just built, is associated with only the trigger event for inquiries that are associated with the designated template. You can then build a separate Workflow triggered off of the same event, but associate it with your other template. This set up will ensure that your Workflows are running on the same trigger event, but different templates. You may have different reasons for decline, mark for review, or approval based on the use case of the template and the above set up will allow for this.

In the event that you want the Workflows you're building to run on all templates that your organization is using, we recommend creating only one Workflow per event to ensure that the Workflows run efficiently and that your rules are prioritized properly within a single Workflow's routing structure. 

Let's say you have three templates. For all three templates, you know that you have a set of rules that apply, regardless of the use case of the template. You know you want to first decline individuals who are under 18, then you want to mark individuals for review who have an ID that is inside of the US, and then you want to approve individuals who do not meet any of the above criteria. You'd set up your Workflow in the following way: 

  1. Name your Workflow
  2. Select the inquiry.completed trigger event
  3. Leave the trigger criteria section blank, since you're not associating it to a specific template and these rules apply to all of the templates
  4. Build the first route for if under 18 (a criteria) then decline (an action
  5. Build a second route for if country is US (a criteria) then mark for review (an action)
  6. Then ensure the else clause is if none of these apply, then approve (an action)
  7. Then activate the Workflow by toggling the activate button on
  8. Finally, be sure to save the workflow in the upper right hand corner of your page
Last updated: