Blend Integration Guide

What is Blend and why teams use it

Blend is a mortgage Point of Sale system that lets borrowers complete their loan application online in a guided, step by step experience. Borrowers can enter personal information, property details, and financial data in one place instead of sending documents back and forth over email.
When Blend is integrated with Shape CRM, your team gets a connected workflow from lead to full application.

Sales and Loan Officer benefits

• Send application invites directly from the CRM
• Less manual data entry since borrower information syncs back automatically
• Visibility into where the borrower is in the application process
• A smoother borrower experience that helps increase completion rates

Operations and Admin benefits

• Automatic record creation and updates between systems
• Reduced data errors from double entry
• Real time application and borrower updates through webhooks
• Clear alignment between the CRM record and the POS application

This integration helps your team move from “we sent them a link” to “we can actually see what they’ve completed and what’s left.”

Connecting Blend to Shape

1. Go to Settings → API Integrations

1. Under the Blend section, click Connect

A popup will appear. Enter:

• Client ID
• Client Secret
• Tenant ID

These credentials come from your Blend environment and allow Shape to securely communicate with Blend.
Two sync modes are available:

• Only Sync Matched Users
• Sync All

How Data Syncs Back to Shape

Blend uses webhook event notifications.
We must:

• Provide Blend with our webhook endpoint
• Subscription is configured by Blend
• Webhook URL appears in the Connect popup

Each webhook event requires a follow-up GET call to retrieve full application data.

User Assignment Mapping

A Blend User ID field is added to user profiles in Shape.
This ID:

• Maps Shape users to Blend users
• Can be entered manually
• Can also be matched via the API by email when available

Blend roles:

• PRIMARY_ASSIGNEE = Loan Originator
• ASSIGNEE = Additional assigned users

On Manage Departments, admins select which department represents the Primary Assignee (Loan Officer).

Configuring Blend Users Manually

If you need to link a specific Shape user to their Blend user:

1. Open the user’s Profile

1. Go to LOS Integration Details.

1. Enter the Blend User ID (GUID) in the Blend User ID field

This ensures applications created from Shape are tied to the correct loan officer inside Blend.

Setting Up Automation to Create Blend Applications

Automation is what turns a CRM record into a live Blend application.

1. Go to Settings → Automation Actions (Triggers)

1. Click Create New Automation Action

Configure:

• Trigger Type Choose the condition that should start the process, usually a status change.
• Trigger Event Select the event, such as a record moving into a working status.
• Automation Type Select Create Application POS Only.
• Action Schedule Choose Immediately or set a delay if needed.
• Name Use a clear name like Create Blend Application when Actively Working.

Trigger option: Create Application in POS
When triggered:

• Shape creates a Blend application
• Only borrower first and last name are required
• Shape Lead ID is stored in crmId
• Borrower email is included
• sendEmailInvite = true
• applicationSource is set to Shape

Borrower receives an email to start their Blend application.

Creating the Record That Triggers Blend

Before automation runs, the record must have minimum borrower details.
Create or update a record in Shape with:

• First Name
• Last Name
• Email Address
• Purpose

Blend User Assignment is optional. The record can be manually assigned or assigned later when Blend sends data back.
Once required fields are filled in, move the record to the status tied to your automation.
When the record hits this status, Shape will:

• Create the application in the Blend portal
• Send the borrower an email invitation link

What the Borrower Experiences

The borrower receives an email invitation. They click Activate Loan Hub, which takes them to the Blend portal.
There they:

• Complete their application
• Follow a task list
• Enter information and upload documents

Blend guides them step by step, reducing confusion and drop off.

How Data Syncs Back to Shape

As the borrower works in Blend, Shape receives webhook updates.
Here is how Shape handles that data:

• Shape checks whether the POS Application ID already exists
• If it exists, the existing record is updated
• If it does not exist, a new record is created

This keeps Shape aligned with the live application.

Blend Field Mappings

Blend Field	Shape Field
id	pointOfsaleId
loanPurposeType	loanPurposeType
loanAmount	LoanAmount
purchasePrice	borpurchasePrice
party.type == “BORROWER”
firstName	firstname
lastName	lastname
middleName	bormiddlename
suffixName	borsuffix
maritalStatus	bormaritalstatusdetails
veteranStatus	leadveteran
phoneNumber	phone
Mailing Address
streetAddressLine1 + line2	boMailStreetAddress
city	boMailCity
state	boMailState
zipCode	boMailZipCode
Current Address
streetAddress	boraddress
city	borcity
state	borstate
zipCode	borzip
Former Address
streetAddress	borformeraddress
city	borformercity
state	borformerstate
zipCode	borformerzip
party.type == “COBORROWER”
firstName	cbiFirstName
lastName	cbiLastName
middleName	cbiMiddleName
suffixName	cbiSuffix
maritalStatus	qkappcbimaritalstatus
phoneNumber	cbiHomePhone
Mailing
streetAddress	cbiMailStreetAddress
city	cbiMailCity
state	cbiMailState
zipCode	cbiMailZipCode
Current Address
streetAddress	cbiPresentStreetAddress
city	cbiPresentCity
state	cbiPresentState
zipCode	cbiPresentZipCode
party.type == “REAL_ESTATE_AGENT”
firstName	relagentName
lastName	relagentLastName
email	relagentEmail
phoneNumber	relagentPhone
Property Fields
address->city	prCity
address->state	prState
address->countyName	prCounty
type	qkapppropertyType
usageType	propropertyUse
value	qkappestAppraisalVal
Income Tables
type	tblOtherIncomeInfo.type
yearlyIncome	tblOtherIncomeInfo.amount
Coborrower Income
type	tblcoborrowerEmploymentInfo.type
yearlyIncome	tblcoborrowerEmploymentInfo.amount.type
assignees	User assignment

What Information Shape Receives from Blend

When a borrower progresses through the application, Blend sends structured application data back to Shape. This gives your team visibility without needing to constantly check Blend.

Application level details

• Application ID
• Application status
• Loan purpose such as Purchase
• Loan amount
• Purchase price
• Property value
• Property type and occupancy
• Created date
• Source showing the application originated from Shape

This allows your team to see the type and size of the deal and its progress.

Borrower and Co Borrower information

For each party on the file, Shape can receive:

• Role type such as Borrower or CoBorrower
• Full name
• Email address
• Phone numbers
• Marital status
• Veteran status
• Status in the application such as Invited or In Application

This ensures the CRM record reflects everyone tied to the loan and their role.

Address history

Blend provides structured address details:

• Mailing address
• Current address
• Former addresses
• Move in dates

This reduces the need to re collect address history later.

Income information

If entered by the borrower, Shape can receive:

• Income type such as Base or Overtime
• Yearly income amounts

This gives early financial insight for the file.

Property details

Shape can receive:

• Property address
• Property type
• Occupancy type
• Estimated value

This keeps the CRM aligned with the subject property automatically.

When and How Shape Receives Data from Blend

Technical Overview
The Blend integration supports:

1. Sending records from Shape to Blend

1. Receiving records from Blend to Shape

1. Application status updates

1. Milestone updates

Event Subscriptions

All Blend integrations subscribe to Process Completed application events. These fire each time a borrower completes a major section such as:

• Getting Started
• Getting to Know You
• Assets
• Income

Some clients subscribe only to these core events, others subscribe to all available events, including:

• Party Events (loans created directly in Blend)
• Milestone events

High Level Workflow

1. Shape creates an application in Blend

1. Borrower enters data in Blend

1. Blend sends an event notification

1. Shape receives the webhook

1. Shape performs a GET call to Blend to retrieve full application data

1. Shape updates the CRM record

1. Borrower submits the application

1. Shape receives updated status events

Record Creation and Update Logic

If crmId exists

• Record updates the existing Shape lead

If crmId does not exist

• Duplicate management runs
• Record may merge or create new Lead

Source handling

• If created in Blend, source is Blend
• Record type is Leads

LOS Coordination

In some setups, Blend replaces LOS integration. In others, it runs alongside.
To prevent duplicates:

• LOS GUID from Blend must be stored
• Must align with existing LOS logic

Summary

With Blend integrated into Shape, your team can:

• Send application invites directly from the CRM
• Track borrower progress without chasing emails
• Reduce manual entry and errors
• Keep sales, operations, and borrowers aligned in one connected workflow

The goal is a smoother borrower experience and better visibility for your team, all while keeping Shape as your central system of record.