DeedSpring

Data

Data connections sync the systems that already hold your contacts, deals, and listings into DeedSpring tables. Open Data from Settings, or switch to Data Syncs on Integrations — it is the same list of connectors.

Choose Add Data Connection. Search, pick a card, then Connect. If the source is not listed, use Request a connector — new ones can be added within a day.

Search connectors, pick a source, or request one that is not on the list yet.

Connect a source

1

Open the dialog

From Settings → Data, or from Integrations → Data Syncs, click Add Data Connection.
2

Pick the connector

Search or choose a card: Airtable, Google Sheets, Follow Up Boss, HubSpot, GoHighLevel, kvCORE (BoldTrail), Lofty, Gmail, Calendly, and others. Then Connect (or Connect with … if the source uses sign-in). Some sources ask for an API key instead.
3

Map onto existing tables

Incoming fields should land on Contacts, Properties, Deals — not a parallel copy of those tables. You will see the mapping before rows start syncing. You can also describe the source in a thread and have the assistant walk the same path with you.

What you can connect

CRMs

HubSpot, Follow Up Boss, GoHighLevel, kvCORE, Lofty, and similar. Records sync on a schedule. Choose pull-only, or write back both ways once you trust the mapping.

Sheets and files

Google Sheets is the live version. For a one-off CSV or spreadsheet, share the file in a thread — the assistant maps columns and shows you the mapping first.

Other tools on the list

Airtable, Asana, ClickUp, Calendly, Fibery, Gmail, and the rest of the dialog fill the same tables the rest of the product already uses.

Missing a connector?

Use Request a connector in the dialog — new ones can be added within 24 hours. Or ask the assistant to author a custom connector for the workspace.

After it is connected

Synced contacts behave like hand-entered ones: they can be deal members, get portal access, and show up in the Inbox. That only works if they land on the existing Contact table, not a side table with a similar name.

The Contacts directory populated with client records
Imported or synced, contacts land in the same directory with the same powers.
  • Extend, don't fork — if your CRM has a field with no home here (say, a lead score), add it to the existing table.
  • Watch for duplicates — if you connected a CRM and then import a spreadsheet, check what already synced before creating rows.
  • Clear the sample data — when real rows land, you will be offered a chance to remove matching sample records. It always asks before deleting.

Sync direction is a real decision

Pulling from your CRM is safe to start with — DeedSpring stays a live mirror. Writing back means edits here flow out to the other system. When unsure, start pull-only and upgrade later.

What this screen does not do

  • It does not let agents post to Slack or run actions in other apps. That is Agent Integrations.
  • It does not replace adding a client to a deal or closing. Membership on those records is still what fills their portal.
IntegrationsUsers