Salesforce Integration

Connect Glide to your Salesforce org so new members flow into Salesforce automatically the moment they're approved.

Overview

Glide can push new member data directly into Salesforce Financial Services Cloud (FSC). When a membership is approved in Glide, Glide instantly creates or updates a Person Account in Salesforce with the member's identity, contact, address, membership, and origination details.

A few things worth knowing up front:

• It's real-time. The record appears in Salesforce as soon as the application is approved in Glide, not on a nightly batch. Your team gets same-day visibility of new members.

• It's one-way. Data flows from Glide into Salesforce. Glide does not read from or change anything else in your Salesforce org.

• It doesn't replace your existing sync. If you already sync core account and product data from your core system into Salesforce, that continues unchanged. Glide only adds the new member record at the point of onboarding, including members who enter the flow but aren't yet funded.

• Setup is self-service. A Salesforce admin connects the two systems from the Glide dashboard, then chooses which fields to send. No engineering work or custom development required on your side.

You'll do a one-time setup in Salesforce (create a connected app, turn on Person Accounts, add a couple of custom fields), then connect and map your fields in Glide.

What gets synced

When a personal membership is approved in Glide, Glide creates or updates a single Person Account in Salesforce. You control exactly which fields are sent during setup. Available fields include:

• Identity: first, middle, last name, suffix, date of birth, SSN/Tax ID

• Contact: primary email, phone

• Address: residential and mailing street, city, state, postal code, country

• Membership and application: membership/member number, application channel (e.g., member-facing flow vs. staff dashboard), and a link back to the application in Glide

• Staff attribution: the branch and staff member who originated the application, so you can distinguish assisted from online applications

If Glide collects a data point you don't see here, your Glide team can add it to the mapping. Glide identifies records using a unique Glide application ID.

Prerequisites

Before you start, make sure you have:

• A Salesforce admin login for the org you want to connect (use a sandbox first if you want to test).

• Permission to create apps and enable features in Salesforce Setup.

• Access to Configure → Integrations in your Glide dashboard.

Before going live, plan to connect your Salesforce sandbox environment to Glide's staging environment.

Step 1: Create a connected app in Salesforce

This is what lets Glide securely connect to your Salesforce org over OAuth.

1. Log in to your Salesforce org (sandbox or production, matching your Glide environment).

2. Go to Setup → Apps → App Manager.

3. Click New External Client App.

4. Fill in Basic Information:

   • External Client App Name: e.g. Glide Integration

   • API Name: leave the default

   • Contact Email: your admin email

   • Distribution State: Local

5. Open the API (Enable OAuth Settings) section.

Callback URL

Add the callback URL for your Glide dashboard environment:

https://<your-glide-dashboard-host>/api/integrations/salesforce/callback

The callback must match exactly what Glide sends, with no trailing slash. If you're unsure of your dashboard host, your Glide contact can confirm it.

OAuth scopes

Move these two scopes into the Selected OAuth Scopes list:

Leave all other scopes unselected.

Settings

Set the following:

6. Click Save.

7. Open the app, go to Settings → OAuth Settings (or Manage Consumer Details), and copy the Consumer Key and Consumer Secret. You'll provide these when connecting in Glide.

If users can't authorize

If a user is blocked when trying to log in from Glide, open the app's Policies:

• Permitted Users: allow the users who will connect from Glide (often "All users may self-authorize," per your security policy).

• IP Relaxation: relax only if required for server-side OAuth, and coordinate with your security team if your org is locked down.

Step 2: Add custom fields in Salesforce

Much of the member data maps to standard Person Account fields that already exist in Salesforce once Person Accounts are enabled (FirstName, LastName, PersonEmail, PersonMailingStreet, and so on). For everything else, you create a custom field on the Account object (not Contact) and map it in Glide.

If Glide collects a piece of data, Glide can expose it to Salesforce. The list below isn't a hard limit. To send something Glide captures that isn't listed, create a matching custom field and ask your Glide team to expose it to the mapping.

Custom fields to create on Account

Create these on the Account object. Salesforce adds the __c suffix automatically, so type the field name without it. Suggested API names are shown; you can use different names as long as the Salesforce field and the Glide mapping match.

Notes:

• Match key (row 1) must be marked External ID and Unique. This is how Glide upserts records without creating duplicates. If it isn't mapped, Glide falls back to matching on PersonEmail.

• Opt-in syncing. Most of these fields appear in Glide's Account fields tab but don't sync until an admin turns them on (the Enable sync option in the row's ⋯ menu) and saves. This lets you create the Salesforce fields first and switch on syncing only once they exist, without breaking anything.

• SSN is sensitive PII. Use Encrypted Text in Salesforce and enable it only if your security policy allows.

• Grant Read + Edit on every custom field you create to the profile of the user who connects Glide.

Standard fields (already exist in Salesforce)

These exist as soon as Person Accounts are enabled. You map them in Glide; you don't create them.

Residential and shipping addresses are also supported as optional fields (PersonOther* and Shipping* respectively) if you want to send them in addition to the mailing address.

A note on State and Country picklists

If your Salesforce org uses State and Country/Territory Picklists, map your country fields to the *CountryCode versions (PersonMailingCountryCode, etc.). Glide sends ISO codes (US, not United States) and handles the state/country code conversion automatically. Don't map country to the legacy text fields (PersonMailingCountry, ShippingCountry) on a picklist-enabled org, as those writes will fail.

Step 3: Connect and map fields in the Glide dashboard

1. In the Glide dashboard, go to Configure → Integrations → Salesforce.

2.Domain: enter your Salesforce org hostname (e.g. acme or acme.my.salesforce.com) and click Submit.

• Use your org login domain (*.my.salesforce.com), not a Lightning-only URL.

• The field locks once submitted. Click Edit to change it. Saving a new domain disconnects OAuth and you'll need to log in again.

3. Click Log in, approve the request in Salesforce, and you'll return to Glide showing Connected.

4. Person Account record type ID: Paste the specific person type to associate with records. This can be different per membership type or role.

5. Open the Account fields tab and map your fields to the Salesforce API names:

• Standard fields: legal name, date of birth, email, phone, mailing address (FirstName, LastName, PersonBirthdate, PersonEmail, Phone, PersonMailing*).

• Glide Application ID → your external-ID field (e.g. Glide_Application_Id__c).

• Glide Application link → your link field.

• If your org uses State and Country/Territory picklists, map Mailing country to PersonMailingCountryCode (ISO code, e.g. US).

6. Click Save. You can save once all required fields are mapped.

You can Reauthorize or Disconnect at any time from the integration header.

Troubleshooting

FAQ

Does this replace our existing core-to-Salesforce sync? No. Glide only adds the new member record at onboarding. Your existing sync for core account and product data continues unchanged.

Is the sync real-time or batched? Real-time. The record is created or updated the moment a membership is approved in Glide.

Can data flow from Salesforce back into Glide? No. This is a one-way integration from Glide into Salesforce.

Will it create duplicate records? No. Glide matches on a unique application ID, so re-approving the same applicant updates the existing Person Account.

What happens if the integration is disconnected? Approvals in Glide still succeed normally. The Salesforce record simply isn't created until the connection is restored.

Need help with setup? Contact your Glide implementation team.