The problem with integrations in real estate software
Most platforms treat integrations as a logo wall. The list is long, the depth is shallow, and the connection that actually matters to your brokerage, your accounting, your lead sources, the channel your team talks in, turns out to be an export you run by hand on Friday.
The second problem is direction. A platform that can be written to but not read from leaves your data in one more place nobody else can reach.
Every connection, and the one word that says whether it works
The Apps page groups every connection by what it is for and walks you through it. Lead generation, accounting, CRM sync, marketing, scheduling, productivity, communication: each entry says what it does, what events it sends, and what setting it up involves before you start. Each one also carries its status, and the status means the same thing everywhere Raven states it.
Live. Connect it from Settings and it works today.
Built, awaiting partner access. Raven's side is finished. It turns on the day the partner grants API access; until then it shows as awaiting access in Settings.
- Live: Gmail, Microsoft Outlook, Google Calendar, Outlook Calendar, Slack, Microsoft Teams, Zapier, Mailchimp, ActiveCampaign, Constant Contact, HubSpot, Follow Up Boss, QuickBooks, Xero, Google Sheets, Notion, Trello, Calendly, Inbound lead webhook, Zillow / Realtor.com / portal leads, Facebook Lead Ads, Google Ads Lead Forms, CallRail, Ylopo, Typeform / web forms, Spark / Flexmls, Instagram, Facebook Pages, LinkedIn, X (Twitter), TikTok, Google Business Profile, Google Analytics 4, Microsoft Clarity, Bing UET, Claude and ChatGPT, Lone Wolf Transact, Authentisign, SkySlope, Follow Up Boss direct connection, BoldTrail (kvCORE), Lofty
- Built, awaiting partner access: MLS Grid, Trestle (Cotality), YouTube, zipForm, TransactionDesk, SkySlope DigiSign
Each one a guided setup: pick the events, connect, send a test. Not a project.
Transaction events, as readable messages
New leads, new contacts, new transactions, stage changes, document approvals and completed signings are published as events. In Slack or Teams they arrive as a sentence a person can read, not a raw payload, because the delivery format is part of the connection rather than something you build on the other side.
- Six event types, versioned, with a documented payload
- Slack and Teams get rendered messages; everything else gets raw JSON
- Deliveries are logged, retried with backoff, and an endpoint that keeps failing is paused with a visible reason
The rendering is part of the connection, not something you build on the far side of it.
An API and signed webhooks for everything else
When no listed connection fits, the same record is reachable directly. Org API keys are scoped and hashed, shown once at mint and never again; outbound webhooks are signed with an HMAC so the receiver can verify that a delivery came from Raven and has not been altered.
- Org-scoped API keys with a fixed scope vocabulary
- Read and write contacts, leads and transactions over /api/v1
- Signed outbound webhooks, Stripe-convention signature header
- Per-key rate limiting, and every write goes through the same de-duplication the app uses
An org API key and HMAC-signed webhooks, so the receiver can prove a delivery came from Raven and was not altered on the way.
Frequently asked questions
Do I need a developer to connect anything?
No. Every connection in the directory is a guided setup: you pick the events you want, paste a destination URL or authorize an account, and send a sample to confirm it arrived. The API and the webhooks are there for the cases a listed connection does not cover, not as the way in.
What if the tool I use is not listed?
If it has a Zapier connector, it connects through Zapier with no code. If it does not, an org API key and signed webhooks let a developer read and write the same records the platform does, which is how anything else gets connected.
Can I see what has been delivered?
Yes. Deliveries are logged with their outcome, failures are retried with backoff, and an endpoint that fails repeatedly is disabled with the reason shown rather than failing quietly. You can send a test delivery at any time.
Can I connect my own AI assistant?
Yes. Paste Raven's connector URL into Claude or ChatGPT and sign in to Raven. The assistant can answer from your people, your transactions, your tasks and your cap progress, seeing only what you can already see and never MLS listing data. If you allow it, it can also send a document for signature or file a combined package onto the checklist, each only after you confirm a preview. A team or brokerage owner decides whether these connections are allowed.
Does connecting a tool mean my data leaves Raven?
Only what that connection is configured to send. You choose the events per endpoint, and the record stays in Raven; a webhook delivers a notification about it rather than moving it.