Last Updated: July 20, 2026

💡 The Yardi (Senior) integration keeps your lead, sales, and engagement data in sync between your CRM and the platform. Once it's set up, prospect records, tours, notes, phone calls, messages, and other activity flow automatically between the two systems — so your sales counselors always see an up-to-date picture of every lead, without re-keying anything by hand.

The integration is highly configurable, so its behavior can be tailored to match how your organization already works in Yardi. Each connection is saved as a named profile that can be enabled or disabled on its own, and you can designate one profile as your default.

Dashboard Configuration and Set-Up

What we'll need to connect

To establish a secure connection to your Yardi environment, we set up a credential set that typically includes:

• Username and password for your Yardi environment

• Your Yardi service URL

• Database name and database server

• Platform and interface identifiers

• A default lead source name and default web lead activity

These are provided during onboarding and stored securely. They will not be exposed to end users.

Please see below for fields and their respective definitions, which are required to get started with Further's Yardi integration.

Username and Password: Basic Auth Credentials. URL: Your Yardi service URL. Platform: Typically 'SQL'. Activity: The initial activity for a new lead, typically 'Web Lead'. Database Name and Server: Obtained during onboarding from Yardi. Lead Source Name: A default source name for Further leads.

Lead Management and Data Hygiene

• Inactive lead check — identify and handle leads that have gone quiet.

This setting will prevent SMS activities from re-opening a lead. To stop email or survey activities from reopening leads, use 'Closed lead activity exclusions' below.

• Do not contact — honor leads who have asked for no further outreach.

This setting prevents nurture campaigns (SMS, Email) from contacting a lead if they have opted out or specified during their submission that they would not like to be communicated with.

• Closed lead activity exclusions — name the activities that should not reopen or affect a closed lead.

Specify activity names so that those activities won't re-open closed leads.

• Email opt-in — when a lead opts in to email, optionally set the matching mass-mail permission in Yardi using a configurable opt-in field.

• Lead scoring — map lead score values to Yardi lead statuses.

On the left, a numerical value generated by Further for a lead and their actions — this denotes the lowest possible score that the associated value on the right may be sent. Example: 0–29 will send 'Cold'. On the right, the value sent to Yardi. These values must exist in Yardi before use; sending a non-existent value will trigger an error.

• Deposit activities — map deposit events to their corresponding Yardi activities.

Custom Fields

Up to six user-defined label and value pairs are available for passing extra data into Yardi, so you can capture organization-specific information alongside the standard fields.

[Image unavailable: custom_fields]

Record Matching

Where your Yardi setup calls for it, records can be matched using a region identifier as the external reference.

[Image unavailable: record_matching]

Lead Submission

Lead and Prospect Sync

Lead creation. Leads captured on the platform are pushed into Yardi as records. You choose whether they're created as Prospects or Contacts, and you can optionally treat every contact as a prospect.

Lead sources. You can set the lead source name applied to synced leads, with a separate source name reserved for web-form leads, and additional secondary source names as needed. You can either keep the platform's own source names or map them to your Yardi values.

Source mapping rules. Ordered rules control how incoming lead sources are translated into Yardi. Rules run top to bottom and can be reordered to set precedence. Alongside them you maintain a list of lead sources (by CRM ID and name), and each source can be flagged for nurture or archive handling.

Care type and "looking for" mapping. Map the levels of care your community offers to their matching Yardi values, and set a default care type for leads that don't specify one. A separate mapping aligns each lead's "looking for" selection with the corresponding Yardi value.

Duplicate handling. You can automatically close duplicate leads so your team never works the same prospect twice.

Activities

Activity Logging

The integration records engagement back to Yardi as activities, so every touchpoint appears on the lead's timeline. Activity types and categories are configurable, and most activities can be attributed to a specific sales counselor. Supported activity types include:

• Notes

• Tours

• Phone calls (inbound and outbound)

• Text messages and emails

• Event RSVPs

• Post-tour surveys

• Analytics activities

Auto-completion. Many activities can be logged as already completed rather than left open as tasks. This is set independently for notes, event RSVPs, post-tour surveys, inbound and outbound phone calls, call transcript summaries, and inbound and outbound SMS and email — so each can match your team's workflow.

Notes

• Notes sync with a configurable note type, category, and tag.

• A character limit keeps long notes within Yardi's field constraints; anything longer is trimmed to fit.

• Notes can be attributed to a sales counselor, and additional user information can be appended to them.

Tours

• Tours scheduled or completed on the platform sync to Yardi with a configurable type and category.

• Tour status mapping lets you match each Yardi tour result type to the corresponding platform tour status, keeping outcomes consistent across both systems.

• An enhanced option is available for pulling tour data from Yardi.

Phone Calls

• Inbound and outbound calls are logged with their own configurable types and categories.

• Call transcript summaries can be pushed into Yardi and, where enabled, logged automatically.

SMS and Email

Inbound and outbound text messages and emails sync as activities, each with its own configurable type, category, and sales counselor. Auto-completion is available separately for each direction and channel.

Events and Surveys

• Event RSVPs sync as activities with a configurable type and category.

• Post-tour surveys can be logged as activities and, optionally, auto-completed.

Analytics Activities

Analytics-driven activities can be logged with their own type, category, and sales counselor attribution.

Bi-Directional Capabilities (Move-Ins)

Move-Ins

Move-in sync can be enabled so that residents who move in are reflected in Yardi.