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.).
• Add one or more Time Delays to run actions after a certain time or at regular intervals (e.g. send an email to a borrower 10 days after the application reaches a specific status).
• 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!

📘

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.

---

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 is discussed 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 workflow status you select here.

---

Triggers (Data Change)

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

👍

Please note that triggers related to data changes will only run when applications are updated - not when applications are initially created. If you want to run automation when an application is created, use the status trigger type.

---

Triggers (Task Status Change)

The third trigger type is "When a task is moved to a status." Automations with this trigger type will run when tasks reach the status you select from the dropdown list.

Additionally, you can activate the "Only run this automation for tasks with specific labels" toggle. The automation will then only run when the task reaches a specific status and has a set of labels assigned.

---

Triggers (Application Creation)

The fourth trigger type is "When an application is created." Automations with this trigger type will run when an application is created on the platform.

---

Triggers (Document Upload)

The fifth trigger type is "When an application document is uploaded." Automations with this trigger will run when a document is uploaded to an application.

Additionally, you can activate the "Only run this automation for documents with specific labels" toggle. The automation will then only run when the document has a set of labels assigned.

---

Time Delays (For Actions)

Time delays allow you to schedule specific actions to run automatically after a certain time or at regular intervals. Users can choose the length of the delay in minutes, hours, days, weeks and months.

Time delays should be added before any actions you want to delay.

📘

For Example

If an application reaches a certain point in the process and is still stuck without moving forward, you can set up an automation to send reminder emails at regular intervals.

• Trigger: When an application is moved to Review status
• Automation Steps:
  1. Time Delay: Wait 5 Day(s)
  2. Action: Send Email (Reminder)
  3. Time Delay: Wait 5 Day(s)
  4. Action: Send Email (Reminder)

---

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.

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.

---

Actions (Create Task)

The "Create Task" action type lets you automatically generate application 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:

• The title of the task.
• The labels assigned to the task.
• The status of the task (i.e. "Not Done", "In Progress", "In Review", "Done", "Canceled" or "Failed").
• The internal instructions for the team members to complete.
• The external instructions for the borrowers/intermediary to complete.
• To whom the task is assigned (your team members and/or borrowers/intermediary).
• The task's due date and due time, which lets assignees understand when it should be completed.
• Variables (i.e. data fields) that are related to the task and are displayed within it.
• Documents that have been associated with the task.
• Comments have been made regarding the task.

📘

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 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.
• Only run this action if the application is in a selected workflow status, which lets you execute actions based on the application's current workflow status.
• Task Title, which is the title of the task.
• Internal Assignee(s), which lets you select the team members assigned to the task.
• Internal Instructions, which will explain the task to the relevant internal assignees.
• External Assignee, which lets you select the borrower/intermediary assigned to the task.
• External Instructions, which will explain the task to the relevant external assignee.
• Automatically email the external assignee to notify them, which will send an email to the external assignee that describes the task and provides a link to upload a file.
• Days Until Due, which lets you set a due date for the task (using days from the moment the task is automatically created).
• Due Time allows to set due time in addition to days until due.
• Task Label(s), which lets you select the task labels.
• Stop applications from entering statuses if the task isn't in the Done status, 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.
• Automatically update this task's status to Done if a condition passes, if a condition passes, which will be checked every time the application is updated. This condition must return “true” (string) or TRUE (boolean) to pass.

---

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.
• Only run this action if the application is in a selected workflow status, which lets you execute actions based on the application's current workflow status.
• 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.

---

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.
• Only run this action if the application is in a selected workflow status, which lets you execute actions based on the application's current workflow status.
• Integration Name, which is the integration that will run.

---

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.
• Only run this action if the application is in a selected workflow status, which lets you execute actions based on the application's current workflow status.
• 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 name and 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 & Fields In Emails!

Variables

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!

System Fields

In addition to variables, you can also reference certain standard system fields in emails. The following fields can be accessed (using the $field_name lexicon provided): $application_id, $application_display_id, $application_product_id, $application_rejected_date, $application_approved_date, $application_created_date, $application_status_id, $application_borrower_id, $application_borrower_type, $application_intermediary_id, $application_decline_reasons, $application_coborrower_ids and $application_coborrower_types

---

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.
• Only run this action if the application is in a selected workflow status, which lets you execute actions based on the application's current workflow status.
• New Application Status, which is the status the applications will be moved to.

👍

Decline reasons can be set in the "Status change" action.

You can state the decline reasons automatically by selecting the final rejection application status.

---

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.
• Only run this action if the application is in a selected workflow status, which lets you execute actions based on the application's current workflow status.
• Variable To Assign Value To, lets you select a variable you’d like to assign a static value to.
• Value To Assign, lets you assign value, variable or formula results.

You can assign values to multiple variables per action.

---

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 to Application” action, you'll be asked to provide the following information:

• Only re-assign 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 offers six options for automatically assigning or unassigning team members to applications.
  • Assign a team member based on load balanced selection will assign team members with fewer assigned applications in the selected statuses. You have the option to assign either specific team members or a permission group, and select which statuses will be included in the load-balanced selection.
  • Assign a team member based on round-robin selection will assign an equal number of created applications to the team members you select (using a round-robin process).
  • Assign specific team members will assign the same team member(s) to applications.
  • Assign all members from a permission group will assign all team member(s) from a permission group to applications.
  • Assign the team member who created the application will assign the team member that completed the application form.
  • Unassign all the team members from the application will unassign all team members from the application.

---

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").

---

Actions (Generate Document)

The “Generate Document” action lets you automatically generate dynamically populated documents based on application data.

When you add a “Generate Document” action, you’ll be asked to provide the following information:

• Only generate a document if a condition passes, which lets you add conditionality to the generate document 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.
• Document Template, which lets you select a template from the list of templates created in the Lending Setup > “Document Templates” section.
• Folder To Save Document, which lets you select a folder to which a generated document will be saved. By default, it’s “Root Folder”.
• Document Label(s), which lets you select the document labels.

📘

You can click on “Edit Folders” to edit “Document Folder Structure” in the loan product configuration.

• Send this document in an email after it is generated, which offers you an option to send a generated document in an email.
  • 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.
  • Add a button at the bottom of the email, which lets you include a button with a name and 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).

---

Actions (Send Document for E-Signature)

The "Send Document for E-Signature" action lets you automatically send a document for e-signature through a DocuSign integration.

When you add a “Send Document for E-Signature” action, you’ll be asked to provide the following information:

• Only send a document for e-signature if a condition passes, which lets you add conditionality to the send document for e-signature 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.
• DocuSign Template, which lets you select a template from the list of templates imported from the DocuSign integration.
• Folder To Save Document, which lets you select a folder to which a signed document will be saved. By default, it’s “Root Folder”.
• Document Label(s), which lets you select the document labels.

📘

You can click on “Edit Folders” to edit “Document Folder Structure” in the loan product configuration.

---

Actions (Request Document Upload)

The "Request Document Upload" action lets you automatically send a document upload request to the borrower, co-borrower, or intermediary. Please note that to send automatic emails to borrowers, co-borrowers, and intermediaries, you need to have a SendGrid integration.

When you add a “Request Document Upload” action, you’ll be asked to provide the following information:

• Only request document upload if a condition passes, which lets you add conditionality to the request document upload 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.
• Subject, which is the subject of the email.
• To (Recipient), which lets you choose a recipient to whom an email with the request will be sent.
• Document Description, which is the description of the document(s) you are requesting.
• Folder To Save Document, which lets you select a folder to which a requested document will be saved. By default, it’s “Root Folder.”
• Document Label(s), which lets you select the document labels.

📘

You can click on “Edit Folders” to edit “Document Folder Structure” in the loan product configuration.

---

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.