Integrations
What connects, and exactly what flows.
Email, calendar and portal enquiries are included. CRMs and property data are connected as custom builds, scoped around how your team actually works. Open any connection to see what it reads, writes and who can see it.
Email & calendar
Each member connects their own account. Nobody else reads it.
GmailIncludedActionable inbox sync for teams on Google Workspace or Gmail.
- What connects
- Each member connects their own Gmail account via Google OAuth.
- What data flows
- Agentiv reads incoming mail to surface actionable items and parse portal enquiries. Replies you approve are sent through your own account.
- Direction
- Read incoming mail; send only what you explicitly send.
- Who can see it
- Only the member who connected the account. Leaders cannot read another member's inbox.
- Disconnect
- Revoke from your Google account settings or disconnect in Agentiv. Sync stops immediately.
Microsoft 365 / OutlookIncludedThe same actionable inbox for teams on Microsoft 365.
- What connects
- Each member connects their own Outlook mailbox.
- What data flows
- Incoming mail is read to surface actionable items and parse REA and Domain enquiry emails into structured leads.
- Direction
- Read incoming mail.
- Who can see it
- Only the member who connected the account.
- Disconnect
- Disconnect in Agentiv; sync stops immediately.
Google CalendarIncludedTwo-way appointment sync.
- What connects
- Each member connects their own Google Calendar via OAuth.
- What data flows
- Events sync in both directions: appointments created in Agentiv appear in your calendar, and calendar events appear in Agentiv's schedule.
- Direction
- Two-way.
- Who can see it
- Only the member who connected the calendar.
- Disconnect
- Revoke from Google or disconnect in Agentiv.
Messaging
Client and buyer conversations, flagged for follow-up.
iMessageIncludedUnanswered client and buyer threads, flagged for follow-up.
- What connects
- A Mac signed into the member's own Messages account, set up during onboarding.
- What data flows
- Message threads are scanned locally to flag unanswered conversations. Suggested replies are drafts; sending is always a human action.
- Direction
- Read threads; drafts only.
- Who can see it
- Only the member whose Messages account it is.
- Disconnect
- Remove the connection during or after onboarding; scanning stops.
Portal enquiries
Buyer enquiries from the major portals, turned into structured leads.
realestate.com.au & DomainIncludedPortal enquiries parsed into structured leads.
- What connects
- Nothing extra. Enquiry emails from the portals already arrive in your connected inbox.
- What data flows
- Agentiv parses those enquiry emails into structured leads: buyer name, property, and enquiry detail. There is no portal API connection, and no partnership with either portal is implied.
- Direction
- Read, from your own inbox.
- Who can see it
- The member whose inbox received the enquiry; leads they log flow into shared pipeline per your team's permissions.
- Disconnect
- Disconnect the inbox and parsing stops with it.
Forms & contracts
REIQ Form 6 tracking is built into Agentiv — a product capability, not a connection. Your team records agreement and contract details against Form 6 fields so dates and obligations stay in one place. It tracks the paperwork; it isn't e-signing and isn't legal advice. Where you use REIQ's own forms platform, it can be connected as a custom build.
RealworksCustom buildREIQ's forms and contracts platform, connected as a custom build.
- What's possible
- Pulling agreement and contract data into Agentiv's tracking so Form 6 fields stay in step with what's in Realworks.
- How it's scoped
- Scoped as part of a custom build. We map your team's actual Realworks workflow before anything is connected.
Data & CRM
CRM and property-data connections are scoped as part of a custom build. We map how your team actually uses the system first, then design a two-way connection around your process — not a generic import.
CoreLogic (RP Data)Custom buildProperty data, comparables and valuations.
- What's possible
- Pulling suburb sales, comparables and property attributes into Agentiv's Market and appraisal workflows.
- How it's scoped
- Configured per team as part of a custom build, using your existing CoreLogic access.
AgentboxCustom buildTwo-way sync with one of Australia's leading agency CRMs.
- What's possible
- Two-way sync of contacts, listings and pipeline so Agentiv and Agentbox stay in step.
- How it's scoped
- We map how your team actually uses Agentbox before connecting, so the sync fits your process rather than forcing a generic mapping.
VaultRECustom buildTwo-way sync with the VaultRE CRM.
- What's possible
- Contacts, listings and activity kept in step between VaultRE and Agentiv.
- How it's scoped
- Scoped and built around your team's VaultRE setup.
RexCustom buildTwo-way sync with the Rex CRM.
- What's possible
- Contacts, listings and pipeline synced between Rex and Agentiv.
- How it's scoped
- Built as a custom connection around how your office runs Rex.
Your CRMCustom buildRunning something else? Most CRMs can be connected.
- What's possible
- If your CRM has an API, a two-way connection can usually be built. Tell us what you run.
- How it's scoped
- We assess your CRM during the demo and scope the connection as part of your custom build.
Running a CRM we haven't listed?
Most systems with an API can be connected as part of a custom build. Tell us what you run and we'll scope it in the demo.