Integrations: what actually connects
Integrations is where your brokerage stores credentials for outside systems. Two of them feed leads into REHL today. It is worth knowing which.
The two that are wired end to end
- Facebook Lead Ads, an inbound lane for forms you run yourself on Meta. REHL receives the submissions, it does not buy or run the ads. Save your Page ID, a long-lived Page access token, the campaign IDs you want, and the disclosure text Meta requires.
- Google Lead Form Extensions, the same inbound arrangement on Google. Pick a bearer token, list your campaign IDs, add your disclosure text, then paste the webhook address and that same token into the campaign's form delivery settings.
For both, only campaigns you list are accepted. That is what tells REHL which brokerage an incoming lead belongs to.
The rest of the tiles
The page also has tiles for an MLS feed, Postmark inbound, Plaid, intent data, and address-change data. Those tiles save what you type, but nothing in REHL reads those particular rows yet, so saving one does not switch anything on.
Connecting your MLS is the clearest example. Your live IDX feed is set up with REHL directly against your data license agreement, not by pasting credentials into this page. See Connect your MLS feed. Feed health is where you check that it is working.
Are my secrets visible to my agents?
Only an Admin seat can open this page, and secrets are masked when they are read back. You can retype a value but you cannot read one out again.
What is the difference between this and Sources?
Integrations stores credentials for a named system. Sources is where you name a lead channel, get a webhook for it, record what you spend, and see what it returns. A Facebook campaign can sensibly exist in both.
Connecting your own Gmail, Calendar, and Drive is separate and lives in Inbox settings, not here.
Need more help? Contact support.