Integrations

Status: live

Integrations connect Realm to the outside tools you already use — your sign-in account, your calendar and email, your MLS, your marketing channels, and the places your leads come from. Some integrations are personal (in General settings → Integrations); others are org-wide (in Brokerage Settings).

The four words Realm uses for availability

Every integration Realm names, here, on the public integrations page and on the homepage, carries exactly one of four statuses. The words are defined in one place (packages/web/src/lib/marketing/integration-status.ts) and every surface reads them from there, so the Guide and the website cannot disagree about whether a connection works.

• Live — connect it from Settings and it works today.
• Built, awaiting partner access — Realm's side is finished. It turns on the day the partner grants API access; until then the card in Settings reads Awaiting API access.
• Coming soon — on the roadmap. The connection is not offered as working yet.
• Not supported — Realm does not connect to this and does not plan to.

The sections below use the same words.

Sign in with Google or Microsoft

On the sign-in page you can Continue with Google or Continue with Microsoft when your account is set up for it. This signs you in without a password. You can also add a passkey under General settings → Security for fast, password-free sign-in on your device.

Calendar & email sync — Live

Under General settings → Calendar, turn on Google or Outlook sync so your Realm appointments and transaction dates land on your personal calendar and are checked for conflicts. Connecting your mail account brings your email into Connect, so messages to and from clients live alongside the rest of the transaction. Gmail, Microsoft Outlook, Google Calendar and Outlook Calendar are all Live: the only thing they need is your own Google or Microsoft sign-in. See Calendar and the Connect overview.

MLS

The MLS tab in General settings is where you connect your MLS so Realm can pull in your own listings and power the Properties surface. Realm is launching MLS-by-MLS (Arizona first), so if yours isn't connectable yet the tab says so cleanly rather than failing. See Connecting your MLS.

• Spark / Flexmls — Live. For the boards Realm offers at signup, Connect your MLS signs you in through the MLS's own login (Spark / Flexmls OAuth) — Realm never stores your MLS password — and the listings your MLS attributes to you show up as From your MLS feed.
• MLS Grid — Built, awaiting partner access. Boards served through MLS Grid need your broker of record to sign that board's data license; Realm collects the broker's details on the MLS card and turns the feed on once MLS Grid issues access.
• Trestle (Cotality) — Built, awaiting partner access. The feed is built and turns on per board as Trestle activates the product.

Marketing channels (social OAuth)

In General settings → Integrations you can connect your marketing channels so Marketing Studio can publish on your behalf. Click Connect on a provider and authorize it in the window that opens; the panel shows each channel's status (Connected, Expired, or Error) and lets you disconnect. See Marketing Studio.

• Instagram, Facebook Pages, LinkedIn, X (Twitter), TikTok — Live. Studio publishes to each once you connect it. TikTok posts stay private until the TikTok app audit completes; the card says so.
• Google Business Profile — Live. Imports your Google reviews into Studio and, where you choose, onto your public site.
• YouTube — Coming soon. You can connect a channel today; publishing from Studio is not wired yet, so the channel is not offered as a publishing destination.

Document & transaction providers

In General settings → Integrations → Documents + transactions you can connect outside document and signature tools so your paperwork flows between Realm and the system your brokerage runs compliance in. Realm stays your system of record; pushing again sends only the documents that changed, into the same transaction on the other side.

• Lone Wolf Transact and Authentisign — Live. Realm mirrors a transaction and its documents into Transact, browses your forms libraries, attaches a form and pulls the filled PDF back, dispatches signings through Authentisign and pulls the executed copy back into the transaction. On a brokerage workspace your broker connects Transact once in Brokerage Settings and everyone is covered. On a personal workspace you request the connection from the Transact card. Your Transact and Authentisign access comes with your MLS membership, not your brokerage, so there is nothing to ask your broker for: REALM arranges the authorization with Lone Wolf and connects it for you. The card reads Requested until then.
• zipForm — Built, awaiting partner access. The same mirror and forms flows are finished for zipForm and turn on the day Lone Wolf issues its shared key; until then the zipForm edition reads **Awaiting API access** and shows the honest degraded state. zipForm's API offers no signed-document return, so the executed copy does not come back on its own there.
• TransactionDesk — Coming soon. Connecting an account works; creating a transaction and uploading documents there is not implemented yet, so it is not offered as working.

Where your documents go (solo agents)

At the top of General settings → Integrations, a solo agent picks where finished documents go: I manage compliance myself, My brokerage uses Command (KW), SkySlope, dotloop, TransactionDesk, Brokermint, or Something else. Pick one, choose or type why it changed, and save. The card then says what a send does now, whether that system is connected, and links to connect it or add your broker's email.

• I manage compliance myself: there is no broker step. A document that asks for review is marked reviewed by you when you upload it, and older documents still waiting offer Mark reviewed.
• Command (KW): documents go into Lone Wolf Transact with **Send to Transact**. In Command, you then attach each one to the Opportunity's checklist from Lone Wolf and submit it there.
• SkySlope / dotloop: Send to SkySlope or Send to dotloop puts the document into that system once it is connected.
• Everything else: Email to broker sends the file to your Broker of Record's email (set on the Profile tab).

The change applies to your next send. Documents you already sent keep their "Sent to …" record, and documents still waiting on you switch to the new button. If your broker sends something back, choose Broker sent it back from that document's menu, fix it, and send it again. Brokerages change this in Brokerage Settings, not here.

Whatever the status of a provider connection, everything else in Realm keeps working. If your brokerage reviews compliance in a system Realm is not connected to, the Send to provider export builds a provider-formatted ZIP you upload by hand. See Documents overview.

Lead-source connectors — Live

In Brokerage Settings → Lead Sources, tell Realm where your leads come from (portals, your website, ad campaigns, referrals). Each source gets its own secure webhook URL, and any portal or website that can POST a lead lands it in Realm. Combined with Routing Rules, this is how an inbound lead lands automatically with the right agent, team, or lead bucket — no manual hand-off. See Leads, sources & buckets.