Real Estate CRM Lead Sync

skill

Read and write leads, notes, and stages in Follow Up Boss/kvCORE-class CRMs via an org Integration row.

Download .md

Real Estate CRM Lead Sync

Read and write leads, notes, and pipeline stages in Follow Up Boss/kvCORE-class CRM (customer relationship management) systems through an org Integration row.

When to use

  • A new lead needs to be created or updated in the real estate CRM after an inquiry, showing, or open house.
  • A stage change (e.g., New Lead -> Contacted -> Under Contract) needs to be reflected in the CRM pipeline.
  • A note, call summary, or follow-up detail needs to be attached to an existing lead record.
  • Lead details need to be pulled from the CRM to check status before outreach or reporting.

Tools

  • http-get
  • http-post
  • http-request

Playbook

  1. Confirm the org's Integration row for the target CRM host (e.g. Follow Up Boss, kvCORE) is active before making any call. If missing or expired, stop and hand off to a human via send-message naming the service and required scopes.
  2. To look up an existing lead, use http-get against the CRM's people/leads endpoint (e.g. GET https://api.followupboss.com/v1/people?email=lead@example.com). Auth is injected automatically by the Integration row — never ask for, echo, or hardcode credentials.
  3. To create a new lead after an inquiry or showing, use http-post with the lead's name, contact details, and source (e.g. POST https://api.followupboss.com/v1/people).
  4. To attach a note or call summary to an existing lead, use http-post against the notes/events endpoint (e.g. POST https://api.followupboss.com/v1/notes) with the lead's CRM ID.
  5. To move a lead to a new pipeline stage, use http-request with a PATCH/PUT call to the lead or deal record (e.g. PATCH https://api.followupboss.com/v1/people/{id} with the new stage field).
  6. To remove a duplicate or invalid lead record, use http-request with a DELETE call against the lead endpoint, only after confirming duplication with a human.
  7. Before finalizing any pricing or offer terms tied to a lead's record, route those details to a human for approval — never write unapproved pricing or offer terms into the CRM.
  8. If a requested action falls outside these endpoints (e.g. bulk import, custom field schema change), stop and hand off to a human via send-message rather than guessing at an unsupported call.

Failure modes

  • The Integration row is missing, expired, or lacks the required scope — you receive a 401/403 response. Stop immediately and message a human naming the CRM service and the scopes needed; never retry with guessed credentials.
  • The lead lookup returns multiple matches (e.g. shared email address) — do not merge or update blindly; surface the ambiguity to a human before writing changes.
  • A stage or field name does not match the CRM's schema (each CRM's pipeline stages are configured differently per brokerage) — verify the exact field name via a http-get schema/config call before attempting the update.
  • Research into a lead's public listing history or portal activity must stay limited to public real estate portals; do not scrape or access non-public data sources.

Done when

  • The lead record in the CRM reflects the correct contact details, stage, and attached notes.
  • Any pricing, offer, or contract term changes were routed to and approved by a human before being written.
  • No credentials were requested, echoed, or hardcoded at any point in the sync.