Automation Builder

How to automate a wide range of actions using DigiFi’s automation builder.

Overview Of Automation Builder

DigiFi’s automation builder is a powerful tool that lets you eliminate manual work by implementing triggers and actions to automate decisions, tasks, emails, status changes and more.

Each automation you create will let you:

  • Define a Trigger to start an automated process, based on application status changes and/or data changes.
  • Add one or more Actions that will run when the automation is triggered (e.g. run decision, send email, create task, assign team member, add label, assign values etc.).
  • Combine actions within a single automation flow to enable synchronous, multi-step processing.

You can create multiple automations that run at the same or different times to automate a wide range of previously-manual work!

1213

📘

For Example

Every time an application is submitted, you want to automatically run an integration to pull the applicant's credit report, review their data against credit requirements, calculate pricing and send an offer/no-offer email. This could be implemented using the automation builder, by adding an automation with the following details:

  • Trigger: Run the automation whenever an application enters the "New Application" status.
  • Actions:
    1. Run Integration (credit bureau)
    2. Run Decision (credit requirements)
    3. Run Decision (pricing)
    4. Send Email (offer or no offer)

How To Add An Automation

To add an automation:

  • Navigate to the "Automation Builder" section of your Loan Product.
  • Click the “Add Automation” button.
  • Provide a name for the automation.

After you have created the automation, you can begin editing it.

930

How To Edit An Automation

Triggers (General)

Each automation includes a "Trigger", which determines when the automation will run. Every time an application is updated, this trigger is checked and the automation begins if it is met.

To edit the trigger, open the automation and click the "Edit Trigger" button. A popup will appear in which you can choose a "Trigger Type", which isdiscussed below.

👍

For each trigger type, you can also add a logical condition, and the automation will only run if that condition passes. Conditions are created using DigiFi's Formula Language and must return TRUE (boolean) or "true" (string) to pass.


Triggers (Status Change)

The first trigger type is "When an application is moved to a status". Automations with this trigger type will run when applications reach the the workflow status you select here.

785

Triggers (Data Change)

The second trigger type is "When application data is updated". These automations run when applications have a specific variable updated, which you'll select while editing the automation.

1105

👍

Triggers related to data changes will only run when applications are updated - not when they're first created. If you want to run an automation when an application is created, use the status trigger type (#1 above).


Actions (General)

Actions are the automated processes that run when the trigger passes. Below is a description of each action type available in the automation builder.

Action TypeDescription
Create TaskLets you automatically generate Tasks for applications.
Run DecisionLets you automatically trigger decisions using Decision Strategies.
Run IntegrationLets you automatically trigger integrations using Data Integrations.
Send EmailLets you automatically trigger emails to your team members, a borrower or the intermediary. Emails will be sent using your SendGrid integration and Company Branding, both of which must be set up to use this feature.
Change Application StatusLets you automatically move applications to another step in the application process.
Assign ValuesLets you assign static values to application variables.
Assign Team MemberLets you automatically assign (or unassign) team members to applications.
Assign LabelLets you automatically assign (or unassign) labels to applications to categorize them in a simple, visual way.

Each automation can contain one or more actions, enabling you to combine multiple actions within an automation flow to enable synchronous, multi-step processing. If you have added multiple actions, you can drag and drop them to change the order of execution.

For each of the action types you can also add a logical condition, and the action will only run if that condition passes. Conditions are created using DigiFi's Formula Language and must return TRUE (boolean) or "true" (string) to pass. This advanced feature provides the powerful ability to only run certain actions under very specific circumstances!

1493

Actions (Create Task)

The "Create Task" action type lets you automatically generate standard tasks, which are helpful to:

  • Provide a clear and consistent application workflow for your team members.
  • Notify your borrowers and intermediaries about outstanding items.
  • Consolidate all relevant information about a specific piece of work in one place.

Tasks can include the following information:

  • Description of the task to be performed.
  • Who is assigned to the task (team member(s), the borrower or the intermediary).
  • Variables (i.e. data fields) related to the task.
  • Documents that are related to the task.
  • Comments that have been made regarding the task.
  • Workflow statuses that the application is blocked from entering until the task is completed.
  • Due date for the task to be completed by.

📘

For Example

If you always need to review and confirm the applicant's income in the workflow status of "Verification", you can create a standard task that will automatically be added to each application at that step. This task could include:

  • Variables such as "Borrower Stated Income" and "Borrower Verified Income".
  • Documents uploaded by the borrower to verify their income.
  • Comments from your team members or the borrower regarding the verification process.
  • Blocked workflow status of "Approved" so that applications can't be finalized until this task is complete.

To add a a Create Task action, click "Add Action" and select “Create Task” . You'll be asked to provide the following information:

  • Only create this task if a condition passes, which lets you add conditionality to task creation (in addition to the workflow status trigger). Conditions are created using DigiFi's formula language and must return TRUE (boolean) or "true" (string) to pass.
  • Description, which will explain the task to the relevant user(s).
  • Assigned To, which can be either internal team members, the borrower or the intermediary.
  • Days Until Due, which lets you set a due date for the task (using days from the moment the task is automatically created).
  • Prevent applications from entering status(es) if a task is not done, which lets you set "Blocked Statuses" that the application will not be able to enter until the task is completed.
  • Include editable application data within the task, which lets you add variables (i.e. data fields) to the task's view, to streamline user workflow when completing tasks.
1087

Actions (Run Decision)

The "Run Decision" action type lets you automatically run Decision Strategies. This functionality is recommended for lenders that want to automatically run underwriting strategies, verification logic or other decisions as applications progress through workflow statuses or have data updates.

📘

For Example

When a new application is created you may want to automatically perform automated underwriting. Once your decision strategy is set up with the appropriate logic, the decision process can be automated using this feature.

When you add a “Run Decision” action, you'll be asked to provide the following information:

  • Only run this decision strategy if a condition passes, which lets you add conditionality to the automation (in addition to the workflow status trigger). Conditions are created using DigiFi's formula language and must return TRUE (boolean) or "true" (string) to pass.
  • Strategy Name, which is the decision strategy that will run.
  • Update the application status if the decision result is Passed, which is an optional toggle that lets you select a workflow status to move the application to if the decision passes.
  • Update the application status if the decision result is Failed, which is an optional toggle that lets you select a workflow status to move the application to if the decision fails.

👍

Outputs of Run Decision actions are saved to the application and can be used for the next automation action.

918

Actions (Run Integration)

The "Run Integration" action type lets you automatically run Data Integrations. This functionality is recommended for lenders that want to automatically run integrations as applications progress through workflow statuses or have data updates.

📘

For Example

When a new application is created you may want to automatically retrieve the applicant's credit file. Once your data integration is set up with the appropriate logic, the integration can be automated using this feature.

When you add a “Run Integration” action, you'll be asked to provide the following information:

  • Only run this integration if a condition passes, which lets you add conditionality to the automation (in addition to the workflow status trigger). Conditions are created using DigiFi's formula language and must return TRUE (boolean) or "true" (string) to pass.
  • Integration Name, which is the integration that will run.
1182

Actions (Send Email)

The "Send Email" action type lets you automatically trigger emails to the application's assigned team members, a borrower or the intermediary. Emails will be sent using your SendGrid Email Delivery integration and Company Branding, both of which must be set up to use this feature.

📘

For Example

When an Application is created and enters the first workflow status, you may want to automatically email:

  • The assigned team member to let them know about the application.
  • The borrower to confirm to them that their application was received.

When you add a “Send Email” action, you'll be asked to provide the following information:

  • Only send this email if a condition passes, which lets you add conditionality to the email automation (in addition to the workflow status trigger). Conditions are created using DigiFi's formula language and must return TRUE (boolean) or "true" (string) to pass.
  • To, Cc and Bcc, which are who the email will be sent to. We will automatically bcc the DigiFi email tracking inbox so that automated emails are visible to day-to-day users in the "Emails" sections of the platform.
  • Subject, which is the subject of the email.
  • Body, which is the email content. You can use standard text or make emails more dynamic with variables (see below for details).
  • Add a button at the bottom of the email, which lets you include a button with a hyperlink, for example to direct the recipient to a digital lending portal (for borrowers or intermediaries) or the DigiFi platform (for your team members).

👍

Use Dynamic Variables In Emails!

You can use variables to give emails dynamic content. To reference a variable within an email, surround the variable's system name with { and }.

For Example. Here is a sample email Body.

Hi {borrower_first_name} - Your request for a {loan_amount} loan has been approved!

When this email is sent, the variables would be replaced with actual values. If the borrower's first name is John and the loan amount is $10,000. The email would look like this when sent:

Hi John - Your request for a $10,000 loan has been approved!

663

Actions (Change Status)

The "Change Application Status" action type lets you automatically move an application to another step of the application workflow.

When you add a “Change Application Status” action, you'll be asked to provide the following information:

  • Only change application status if a condition passes, which lets you add conditionality to the status change automation (in addition to the workflow status trigger). Conditions are created using DigiFi's formula language and must return TRUE (boolean) or "true" (string) to pass.
  • New Application Status, which is the status the applications will be moved to.
933

Actions (Assign Values)

The “Assign Values” action lets you assign static values to application variables.

When you add an “Assign Values” action, you’ll be asked to provide the following information:

  • Only assign values if a condition passes, which lets you add conditionality to the assign values automation (in addition to the workflow status trigger). Conditions are created using DigiFi's formula language and must return TRUE (boolean) or "true" (string) to pass.
  • Variable To Assign Value To, lets you select a variable you’d like to assign a static value to.
  • Value To Assign, lets you type a static value you’d like to assign to a variable.

You can assign static values to multiple variables per action.

1703

Actions (Assign Team Member)

Assigning team member(s) to applications lets them know what to work on next. The DigiFi platform provides the ability to automate the assignment (or un-assignment) of team members to applications.

When you add an “Assign Team Member” action, you'll be asked to provide the following information:

  • Only reassign team members if a condition passes, which lets you add conditionality to the action. Conditions are created using DigiFi's formula language and must return TRUE (boolean) or "true" (string) to pass.
  • Assignment Type, which can be either "Assign a specific team member to the application" or "Unassign all team members from the application".
  • Team Members To Assign, which lets you select specific people to assign (this only appears if the Assignment Type is "Assign a specific team member to the application").
979

Actions (Assign Label)

The "Assign Label" action type lets you automatically trigger label assignments that can be added to applications to categorize them in a simple, visual way. Labels appear as small color elements on the applications board and larger colored text elements on the application detail view.

When you add an “Assign Label” action, you'll be asked to provide the following information:

  • Only assign labels if a condition passes, which lets you add additional conditionality to the action. Conditions are created using DigiFi's formula language and must return TRUE (boolean) or "true" (string) to pass.
  • Assignment Type which can be either "Assign a specific label to the application" or "Unassign all labels from the application".
  • Labels To Assign, which lets you select specific labels to assign (this only appears if the Assignment Type is "Assign a specific label to the application").
1159

How To Delete An Automation

To delete an automation:

  • Hover on the relevant row in the table of automations.
  • Click on the 3-dots icon on the right side.
  • Select the "Delete Automation" option.