Both directions
An endpoint either receives submissions from another website, or sends events to another system. Choose which when you create it.
What can be sent
- A contact is created — from any source, including your own forms
- A contact moves stage — with the stage it came from and the one it moved to
- A contact changes agent
- A task is completed
These are the moments another system can act on. Sending on every small edit produces noise, and noise is how an integration ends up switched off.
What this is for
A firm of any size runs a transaction platform, an accounting system or a back office it is not going to replace. Sending events keeps those in step without anyone re-typing anything. It also means anything Zapier, Make or n8n can reach is reachable from MLS Genie, without a purpose-built integration for each one.
How much is sent
By default the whole record goes, which is what most tools expect and what automation platforms need to be useful. There is a switch to send only the record number and what changed instead — no names, email addresses or phone numbers leave the site. Use it when the receiving system only needs to know that something happened, or when the firm would rather personal details stayed put.
When the other end is down
A failed delivery is retried five times over about two hours. After that it is marked failed and left alone, and you can see it in the Activity Log. An address that fails twenty deliveries in a row is switched off automatically, so a permanently broken integration cannot keep queueing work.
Checking it works
Every sending endpoint has a Send test button. Nobody should have to wait for a real lead to find out whether the address was typed correctly.
