Connect Lumaa to the tools your agency already uses.
CRMs, property portals and calendars — every AI call lands in your CRM, and viewings go straight into your calendar.
Launching soon for Lumaa customers. None can be connected yet.
Beta
Built to the vendor's official API documentation; live testing with the vendor is still under way.
Partner access
The vendor gives API access only by agreement.
Coming soon
Sign-in with this vendor is being enabled.
Via Custom Webhook
No public API: connect through Zapier, Make or n8n.
25 integrations
CRMs 11
BiBeta
Every AI call is logged on the Bitrix24 lead/contact with its summary, lead status follows the call outcome, callbacks become to-dos, new Bitrix24 leads can be imported for calling. (Paid Bitrix24 plan or trial.)
Imports leads
Logs every call
Creates follow-ups
Beta
Two-way contacts and deals; every call logged on the contact with its summary; callbacks become tasks; lead status follows the outcome.
Imports leads
Logs every call
Creates follow-ups
Books viewings
SaComing soon
Leads, contacts, opportunities; each call becomes a completed call Task with the summary; callbacks become tasks.
Imports leads
Logs every call
Creates follow-ups
Books viewings
Coming soon
Two-way leads and contacts (real-time); calls logged in the lead's Calls; callbacks → tasks; viewings → meetings.
Imports leads
Logs every call
Creates follow-ups
Books viewings
GHLBeta
Every call logged on the contact; the outcome is applied as a tag your workflows can trigger on; callbacks → tasks; viewings → appointments.
Imports leads
Logs every call
Creates follow-ups
Books viewings
PiBeta
Two-way people and leads; calls logged as call activities; callbacks → follow-up activities.
Imports leads
Logs every call
Creates follow-ups
Books viewings
moBeta
A monday board as your lead list: each call is posted on the item, the Status column follows the outcome. (Board chosen in Settings.)
Imports leads
Logs every call
Creates follow-ups
Real-time
D365Coming soon
Leads, contacts, opportunities; each call a completed phone call with the summary.
Imports leads
Logs every call
Creates follow-ups
Books viewings
KoBeta
Calls logged on the contact; the contact's open lead moves to the stage you map; callbacks → follow-ups.
Imports leads
Logs every call
Creates follow-ups
Books viewings
Beta
Leads and contacts; calls posted on the lead as internal notes; the lead's stage follows the outcome; callbacks → scheduled Call activities. (odoo.com Custom plan or self-hosted Odoo 14–19.)
Imports leads
Logs every call
Creates follow-ups
FrBeta
Calls logged in the contact's call log; status follows the outcome; callbacks → tasks.
Imports leads
Logs every call
Creates follow-ups
Books viewings
Real estate 5
PFBeta
New Property Finder enquiries become leads the AI calls within minutes, with the listing they asked about as call context. Also imports your listings.
Imports leads
Imports listings
BPartner access
New Bayut and dubizzle enquiries become leads the AI calls within minutes, with the listing as context. Leads reach Lumaa from your CRM, from Zapier / Make / n8n, or through Bayut's Leads API.
Real-time
ReBeta
Imports the Reelly off-plan catalogue (projects, prices, handover dates, payment plans) so the AI can talk about them.
Imports listings
GoVia Custom Webhook
Use the Custom Webhook integration (Goyzer's Zapier app or its lead-export webhook), or upload leads with a CSV link. A native connector is built on request once Goyzer issues API credentials for your account.
PrVia Custom Webhook
Use the Custom Webhook integration or a CSV upload link. Listings published to Property Finder are available through the Property Finder integration.
Calendars 8
Coming soon
The AI checks your calendar before offering viewing times and books agreed appointments into it, inviting the lead by e-mail.
Books viewings
Reads availability
Real-time
OlComing soon
The AI checks your Outlook or Microsoft 365 calendar (work and personal accounts) before offering viewing times and books agreed appointments into it.
Books viewings
Reads availability
Real-time
Beta
Offers the free times of your Cal.com event type and books viewings straight into Cal.com.
Books viewings
Reads availability
Real-time
Beta
Offers your real Calendly availability and books viewings into the chosen event type (paid Calendly plan needed for booking and real-time).
Books viewings
Reads availability
Real-time
Beta
Checks your iCloud calendar and books agreed appointments into it.
Books viewings
Reads availability
DAVBeta
Any CalDAV calendar (Fastmail, Nextcloud, Yahoo, Synology…): availability and bookings.
Books viewings
Reads availability
Coming soon
Checks your Zoho Calendar and books agreed appointments into it.
Books viewings
Reads availability
ICS
Read-only busy times from any calendar that can publish an ICS link. Cannot take bookings.
Reads availability
Other 1
{ }
Connect anything that can send or receive webhooks — Goyzer, PropSpace, website forms, in-house CRMs — through Zapier, Make, n8n or Power Automate.
Logs every call
Creates follow-ups
Books viewings
Real-time
No integration matches that search. Anything that can send a webhook connects through the Custom Webhook.
Bi
Bitrix24
Beta
Every AI call is logged on the Bitrix24 lead or contact with its summary, the lead status follows the call outcome, callbacks become to-dos, and new Bitrix24 leads can be imported for calling.
How you'll connect
Inbound webhook URL · coming soon: Sign in with Bitrix24 (Lumaa app)
In your Lumaa dashboard, once integrations open to customers:
In Bitrix24 open Applications → Developer resources (signed in as an administrator).
Go to Common use cases → Other → Inbound webhook.
Under Assign permissions tick CRM (crm), Tasks (task) and Users (user), then click Save.
Copy the webhook URL (it looks like https://yourcompany.bitrix24.com/rest/1/abc123…/) and paste it here.
The Bitrix24 REST API needs a paid plan (or the trial); the free plan answers ACCESS_DENIED.
Sign-in with Bitrix24 requires the Lumaa app to be installed from the Bitrix24 Market first; the inbound webhook works without it.
Bitrix24 in Simple CRM mode has no leads: set new people to be created as contacts.
Contacts have no status field, so outcome-based status updates apply to leads and deals only.
HubSpot
Beta
Sync contacts and deals both ways; every AI call is logged on the contact with its summary, callbacks become tasks, and lead status follows the call outcome.
How you'll connect
Private app token · coming soon: Sign in with HubSpot
In your Lumaa dashboard, once integrations open to customers:
In HubSpot open Settings → Integrations → Private Apps → Create a private app.
Name it 'Lumaa'. On the Scopes tab tick: crm.objects.contacts (read+write), crm.objects.deals (read+write), crm.objects.owners.read, crm.schemas.contacts.read.
Click Create app, then Show token → Copy, and paste it here.
Real-time updates need the Lumaa HubSpot app (OAuth). Private-app connections sync every 5 minutes.
Sa
Salesforce
Coming soon
Sync leads, contacts and opportunities with Salesforce Sales Cloud; every AI call is logged as a completed call Task with its summary, callbacks become tasks, and lead status follows the call outcome.
How you'll connect
Sign in with Salesforce is being enabled; Salesforce can be connected once it is.
Good to know
Salesforce has no built-in webhooks without Apex or Flow, so Lumaa checks for changes every 5 minutes.
Needs Enterprise, Unlimited, Performance or Developer Edition (Professional Edition only with the API add-on) and a user with the 'API Enabled' permission.
A Salesforce admin may need to install or approve the Lumaa app once before users can connect.
If your org restricts logins by IP address, the admin sets 'Relax IP restrictions' in the Lumaa app policy.
Salesforce requires a Last Name and a Company on every Lead: for an unknown caller Lumaa writes 'Unknown' and the 'Company for new leads' setting (default 'Individual'). Existing records are never overwritten with these placeholders.
Contacts have no Status field: the call outcome is on the call Task unless you choose a Contact status field in the settings.
Lead assignment rules run only when Lumaa creates a lead without an owner; updates never re-assign a lead.
Call type, duration and result fields are filled when your org has the Task call fields (Salesforce CRM Call Center); otherwise they are in the task description.
Notes are saved as Salesforce Notes when Notes are enabled, otherwise as classic Notes on the first related record.
Default lead statuses use the classic values ('Working - Contacted', 'Closed - Not Converted'); check the status mapping if your org uses different ones.
Zoho CRM
Coming soon
Sync Zoho CRM leads and contacts both ways; every AI call is logged in the lead's Calls with its summary, callbacks become tasks, viewings become meetings, and Lead Status follows the call outcome. Works with every Zoho region, including the UAE and Saudi data centers.
How you'll connect
Sign in with Zoho is being enabled; Zoho CRM can be connected once it is.
Good to know
Real-time updates use Zoho Notifications for Leads and Contacts (renewed every 6 days). Zoho does not sign notifications; Lumaa checks a per-channel token and a 10-minute freshness window. Polling every 10 minutes is the safety net.
Every poll and search spends Zoho API credits (Free edition: 5,000 per day).
Zoho Contacts have no standard status field: set 'Contact status field' to move contacts; otherwise status updates apply to Leads (Lead Status) and Deals (Stage) only.
An optional value Zoho rejects (Lead Source not in your picklist, an unknown owner, a deal's contact that is really a lead) is dropped instead of failing the whole sync.
Task due dates are date-only in Zoho; the exact callback time is written in the description.
GHL
GoHighLevel
Beta
Every AI call is logged on the GoHighLevel contact with its summary, the call outcome is applied as a tag your workflows can trigger on, callbacks become tasks, agreed viewings are booked in your GHL calendar and qualified leads can open opportunities.
How you'll connect
Private Integration token · coming soon: Sign in with GoHighLevel
In your Lumaa dashboard, once integrations open to customers:
In GoHighLevel, switch to the sub-account you want to connect and open Settings → Private Integrations (if you don't see it, ask your agency admin to turn it on in Labs).
Click 'Create new Integration', name it 'Lumaa', and allow: View/Edit Contacts, View/Edit Opportunities, View Calendars, Edit Calendar Events, View Locations and View Custom Fields (contacts.readonly, contacts.write, opportunities.readonly, opportunities.write, calendars.readonly, calendars/events.write, locations.readonly, locations/customFields.readonly).
Click Create, copy the token and paste it here.
Copy your browser's address bar (it contains /location/<your ID>/) and paste it into Location ID — we keep just the ID.
GoHighLevel contacts have no status field: the call outcome is applied as a tag (lumaa-qualified, lumaa-no-answer …) and the previous Lumaa outcome tag is removed.
Real-time updates need the Lumaa marketplace app (Sign in with GoHighLevel). Private Integration connections sync every 5 minutes.
Pi
Pipedrive
Beta
Sync people and leads both ways; every AI call is logged as a call activity on the person or lead with its summary, callbacks become follow-up call activities, viewings become meetings, and the outcome can set a lead label or a person field.
How you'll connect
Personal API token · coming soon: Sign in with Pipedrive
In your Lumaa dashboard, once integrations open to customers:
Log in to Pipedrive as an admin (or as the user whose people and leads should sync) and click your name in the top-right corner.
Choose Company settings → Personal preferences → API (or open app.pipedrive.com/settings/api).
Copy 'Your personal API token', paste it here and click Connect.
The API token acts as the Pipedrive user who created it: the integration sees and writes exactly what that user can. Use an admin's token (or Sign in with Pipedrive as an admin) for full coverage.
Call outcomes: on leads, set your status map to lead label names (e.g. Hot / Warm / Cold); on people, choose a person field in the settings first. Nothing is written until you map outcomes.
Real-time updates use Pipedrive webhooks (up to 40 per user); Sign in with Pipedrive needs the app's admin scope for them, otherwise the connection syncs every 5 minutes.
Every request spends Pipedrive's daily API token budget, shared with your other integrations.
mo
monday.com
Beta
Use a monday.com board as your lead list: every AI call is posted on the lead's item with its summary, the Status column follows the call outcome, callbacks become updates that notify the owner, and new or changed leads flow into Lumaa.
How you'll connect
Personal API token · coming soon: Sign in with monday.com
In your Lumaa dashboard, once integrations open to customers:
In monday.com click your profile picture (top right) and choose Developers — the Developer Center opens in a new tab. (Admins can also use Administration → Connections → Personal API token.)
Click 'API token', then 'Show', copy the token and paste it here. Lumaa acts as you, so use an account that can edit your leads board.
After connecting, open your leads board, copy the link from your browser's address bar (it contains /boards/ and a number) and paste it into 'Leads board' in the settings.
That's it — we find the Phone, Email, Status and Person columns automatically. Pick columns yourself only if the board has several of the same kind.
Pick your leads board in the settings after connecting. Real-time updates are registered when the connection is set up — if you choose the board later, reconnect once (until then changes sync every 10 minutes).
Status labels are specific to each board, so there is no default outcome→status mapping: choose the label for each call outcome in the status settings.
Calls, notes and callback tasks are posted as updates on the lead's item (tasks @mention the owner). Subitems are not used: on multi-level boards the first subitem clears the lead's rollup column values.
monday.com limits API calls per day (1,000 on Standard/Basic, 10,000 on Pro, 25,000 on Enterprise). Each synced call uses about 3; if the limit is reached, syncing resumes after midnight UTC.
With a personal token Lumaa acts as that user: updates appear under their name and only boards they can edit are reachable.
D365
Microsoft Dynamics 365 Sales
Coming soon
Every AI call is logged as a completed phone call on the Dynamics 365 lead or contact with its summary, the lead's status reason follows the call outcome, callbacks become tasks, and new leads can be imported for calling.
How you'll connect
Sign in with Microsoft is being enabled; Microsoft Dynamics 365 Sales can be connected once it is.
Good to know
Polling only (every 5 minutes by default): Dynamics real-time notifications need a plug-in registered inside your environment.
Only commercial-cloud environments (yourcompany.crm<N>.dynamics.com) are supported.
Lead status: Open reasons (1 New, 2 Contacted) and Disqualified reasons (4 Lost, 5 Cannot Contact, 6 No Longer Interested, 7 Canceled) are set directly; Qualified (3) is refused because qualifying creates account/contact/opportunity records — qualify the lead in Dynamics.
By default 'not interested' disqualifies the lead (No Longer Interested); 'no answer' changes nothing. Override in the status mapping.
Contacts only have Active/Inactive, so status updates apply to leads; opportunities are never closed as Won/Lost by Lumaa.
Calls are completed Phone Call activities; SMS / WhatsApp / email touchpoints are notes.
Ko
Kommo
Beta
Every AI call is logged on the Kommo contact with its summary, the contact's open lead moves to the stage you map for each outcome, callbacks become follow-up tasks, viewings become meeting tasks, and new Kommo contacts can be imported for calling.
How you'll connect
Long-lived token · coming soon: Sign in with Kommo
In your Lumaa dashboard, once integrations open to customers:
Log in to Kommo as an account administrator and open Settings → Integrations.
Click 'Create integration', leave the Redirect URL empty and click Save (all permissions stay ticked).
Open the new integration, go to the 'Keys and scopes' tab, click 'Generate long-lived token', choose the longest expiry date and copy the token.
Paste the token here with your Kommo address (e.g. yourcompany.kommo.com) and click Connect.
A long-lived token acts with the rights of the administrator who created it and stops working on the expiry date chosen when it was generated (1 day to 5 years): reconnect before then.
Kommo contacts have no status. Map each call outcome to a lead stage (a stage name, a stage ID, 'pipelineID:stageID', won or lost) and Lumaa moves the contact's most recently updated open lead. Nothing is moved until you map outcomes.
Real-time contact updates use Kommo webhooks, which need an administrator connection and the Advanced, Pro or Enterprise plan; otherwise the connection syncs every 5 minutes.
Odoo
Beta
Sync Odoo CRM leads and contacts; every AI call is posted on the lead as an internal note with its summary, callbacks become scheduled Call activities, and the lead's stage follows the call outcome.
How you'll connect
Odoo API key
In your Lumaa dashboard, once integrations open to customers:
Log in to Odoo as the user Lumaa should act as (a salesperson with CRM access, or a dedicated 'Lumaa' user).
Click your avatar (top right) → Preferences (called My Profile in some versions) → Account Security tab → New API Key, and confirm your password.
Name the key 'Lumaa', choose the longest duration offered, click Generate Key and copy it — Odoo shows it only once.
Paste your Odoo address, your login e-mail and the key here (leave Database empty for yourcompany.odoo.com), then click Connect.
On odoo.com the external API is only available on the Custom plan; One App Free and Standard plans cannot connect. Self-hosted and Odoo.sh servers work on Odoo 14 to 19.
Lumaa acts as the Odoo user who created the API key and sees exactly what that user can see. Odoo 19 keys last at most three months: create a new key and reconnect before it expires. Disconnecting does not delete the key — remove it under Account Security.
Every CRM record (lead or opportunity) syncs as a lead; the status map uses stage names (default: qualified → 'Qualified'). Lost/archived leads are not synced.
Call summaries are posted as internal notes (never e-mailed to followers); callbacks become scheduled Call activities for the lead's salesperson.
Odoo's phone blacklist (SMS opt-out) is treated as do-not-call.
Fr
Freshsales
Beta
Every AI call is logged on the Freshsales contact's call log with its summary, the contact status follows the call outcome, callbacks become tasks, viewings become appointments, and new Freshsales contacts can be imported for calling.
How you'll connect
API key
In your Lumaa dashboard, once integrations open to customers:
Log in to Freshsales, click your profile picture (top right) and choose Profile Settings.
Open the API Settings tab and copy 'Your API key'.
Copy the Bundle alias shown just below the key (for example yourcompany.myfreshworks.com).
The API key acts as the Freshsales user it belongs to: the integration sees and writes exactly what that user can. Use an administrator's key for full coverage.
Call outcomes: map each outcome to a Freshsales contact status (name or ID). Nothing is written until you map outcomes.
Freshsales has no webhook subscription API (only workflow webhooks set up in its UI), so the connection syncs every 10 minutes.
New deals: when the contact has no account and Freshsales marks the account field required, an account named after the contact is created (the documented on-the-fly account), unless you set 'Account ID for new deals'. Deal value defaults to 0 because Freshsales requires one.
PF
Property Finder
Beta
New Property Finder enquiries (calls, WhatsApp, email) become leads the AI calls within minutes, with the listing they asked about as call context. Your listings sync for reference.
How you'll connect
Enterprise API key
In your Lumaa dashboard, once integrations open to customers:
Log in to PF Expert with an admin account.
In the left menu open Developer Resources → API Credentials.
Create a new key, choose the type 'API Integration' and name it 'Lumaa'. If you are asked for permissions, allow Leads and Listings.
Copy the API Key and the API Secret, paste them below and click Connect.
Then turn on 'Import leads' and pick the campaign that should call new enquiries.
Beta: Property Finder asks third-party platforms to complete its Developer Network partner onboarding (pfdn.propertyfinder.com); each agency connects with its own PF Expert API key.
Read-only: calls and outcomes are not written back to Property Finder (no documented endpoint).
Listings are refreshed at most every 30 minutes.
B
Bayut & dubizzle
Partner access
New Bayut and dubizzle enquiries (calls, WhatsApp, email) become leads the AI calls within minutes, with the listing they asked about as call context. Leads are forwarded to a private Lumaa address by your CRM, automation tool or Bayut Leads API integration.
How you'll connect
Private lead address
In your Lumaa dashboard, once integrations open to customers:
Click 'Create my webhook', then 'Show inbound URL & signing secret', and copy the URL.
Send that URL to whoever handles your Bayut leads today: your CRM's automation, your Zapier / Make / n8n account, or your developer if you use the Bayut Leads API (you can request it from support@bayut.com).
Ask them to send every new Bayut or dubizzle lead to it with the name, phone, email, message and listing reference (the full field list is in the notes on this page).
Turn on 'Import leads' and choose the campaign that should call new enquiries.
Partner-gated: Bayut gives its Leads API to Profolio agencies on request (support@bayut.com) and its technical reference is only visible after a Profolio sign-in, so Lumaa does not connect to Bayut directly. Leads arrive at this integration's private URL instead.
Ways to send leads today: your CRM or Zapier / Make / n8n forwards each new Bayut or dubizzle lead; a developer with Bayut Leads API access forwards them; or ask support@bayut.com to CC lead notification emails to an email-parser that forwards them. If your CRM already receives Bayut leads and is connected to Lumaa, importing from the CRM works too.
The listing and the enquiry are shown to the AI on the call. Phone views and WhatsApp views only mean the buyer revealed your number (Bayut does not count them as TruLeads); to call only real enquiries, set the import filter on tags to call, whatsapp and email.
Read-only: call results are not written back to Bayut or dubizzle (no documented API).
For older leads, export them from Profolio (Reports -> Leads -> Export), save as CSV and use your Lumaa lead upload link.
Re
Reelly
Beta
Imports the Reelly off-plan catalogue — developer projects with starting prices, handover dates, payment plans, bedroom types and brochures — so the AI can answer project questions on calls.
How you'll connect
Reelly API key
In your Lumaa dashboard, once integrations open to customers:
Email your Reelly account manager (or support@reelly.io) and ask for a Reelly API key for your agency. API access is part of a Reelly subscription.
Copy the API key from their reply, paste it below and click Connect.
Optional: in the settings, type the country to import (for example United Arab Emirates) if you only sell in one market.
Read-only: Reelly's API is GET-only, so nothing is written back to Reelly.
Each Reelly project becomes one property (starting price, price and size ranges, bedroom types, handover date, payment plans, brochure). Unit-level inventory needs a Reelly Enterprise plan and is not imported.
Checked for changes every hour (Reelly refreshes its data daily); only changed projects are re-read, using Reelly's documented updated_at_after filter.
Reelly documents that only some list filters are active on its servers. If the change filter or sort order is ignored, the connector falls back to a full re-read at most once a day.
{ }
Custom Webhook (Zapier, Make, n8n)
Connect any system that can send or receive webhooks — Goyzer, PropSpace, website forms, in-house CRMs — through Zapier, Make, n8n or Power Automate.
How you'll connect
Webhook
In your Lumaa dashboard, once integrations open to customers:
Click Connect (the target address is optional — add it if you want call results sent back).
Open the new integration and click 'Show inbound URL & signing secret'.
In Zapier / Make / n8n add a 'Webhook → POST' step that sends each new lead as JSON to that URL (fields like name, phone, email, source, notes).
In the integration's Settings, turn on 'Import leads' and choose the campaign to call them in.
The AI checks your Google Calendar before offering viewing times and books agreed appointments straight into it, inviting the lead by e-mail. Moves and cancellations made in Google Calendar flow back to Lumaa in real time.
How you'll connect
Sign in with Google is being enabled; Google Calendar can be connected once it is.
Good to know
All permission boxes must be ticked on Google's consent screen; a partial grant is refused with a message asking the user to connect again.
Only the chosen booking calendar is watched and checked for availability. Google push channels last up to 7 days and are renewed automatically; polling every 15 minutes is the safety net.
Bookings send Google Calendar invitations to the lead when an e-mail is known (sendUpdates=all).
Ol
Microsoft Outlook Calendar
Coming soon
The AI checks your Outlook / Microsoft 365 calendar before offering viewing times and books agreed appointments straight into it, inviting the lead by e-mail. Moves and cancellations made in Outlook flow back to Lumaa in real time. Works with work and personal Outlook accounts.
How you'll connect
Sign in with Microsoft is being enabled; Microsoft Outlook Calendar can be connected once it is.
Good to know
Work/school (Microsoft 365) and personal Outlook.com accounts are supported. Some organizations require an administrator to approve Lumaa once before users can connect.
Only the chosen booking calendar is checked for availability. Anything not marked Free in Outlook (busy, tentative, out of office, working elsewhere) blocks the time.
Outlook change notifications cover the whole mailbox's events and last up to 7 days; they are renewed automatically, and polling every 15 minutes is the safety net.
Bookings e-mail an Outlook invitation to the lead when an e-mail address is known (Microsoft always sends invitations to attendees). Times are stored in UTC; Outlook shows them in your own time zone.
Microsoft offers no way to revoke a single app token: disconnecting stops all syncing; remove Lumaa from your Microsoft account's app permissions to cut access completely.
Cal.com
Beta
The AI offers the free times of your Cal.com event type (for example 'Property viewing') and books agreed viewings straight into Cal.com, which sends its usual confirmation e-mails. Cancellations and reschedules made in Cal.com flow back to Lumaa in real time.
How you'll connect
Cal.com API key
In your Lumaa dashboard, once integrations open to customers:
In Cal.com open Settings → Developer → API keys (app.cal.com/settings/developer/api-keys) and click New.
Name it 'Lumaa', pick the longest validity offered, click Save and copy the key (it starts with cal_live_). Lumaa stops booking if the key expires or is deleted.
Paste the key here and click Connect. Leave the self-hosted address empty unless your company runs its own Cal.com server.
Back in Lumaa, choose the event type the AI should book (for example 'Property viewing'). Done — bookings appear in Cal.com straight away.
Choose the Cal.com event type the AI books into. Available times come from Cal.com itself (your Cal.com schedule, calendars connected in Cal.com, buffers, minimum notice and limits).
The API key belongs to one Cal.com user: only that user's personal event types can be used, not team event types.
Cal.com needs the lead's e-mail to book (or a phone number if your event type asks for a phone instead of an e-mail). Bookings use the event type's own title, length and location.
Only the start time of a booking can be moved from Lumaa; Cal.com creates a new booking for a reschedule and cancels the old one.
Lumaa registers a Cal.com webhook automatically; polling every 15 minutes is the safety net.
Self-hosted Cal.com: enter your API v2 address. Only the cloud API (api.cal.com) is verified; older self-hosted releases may not support the 2026 API versions Lumaa uses.
Calendly
Beta
The AI offers your real Calendly availability on calls and books agreed viewings straight into the Calendly event type you choose, so Calendly sends its usual confirmations and calendar invites. Cancellations made in Calendly flow back to Lumaa.
How you'll connect
Personal access token · coming soon: Sign in with Calendly
In your Lumaa dashboard, once integrations open to customers:
Log in to Calendly with the account whose bookings the AI should manage, open Integrations & apps and click the 'API and webhooks' tile.
Under Personal access tokens click 'Get a token now' (or 'Generate new token') and name it 'Lumaa'. If Calendly asks for permissions, allow users, event types, availability, scheduled events (read and write), scheduling links and webhooks.
Click Create token, then Copy token (Calendly shows it only once) and paste it here. Then pick the event type the AI should book.
Automatic booking uses Calendly's Scheduling API, which needs a PAID Calendly plan (Standard or above); on the free plan bookings are refused with an explanation. Paid non-Enterprise plans can book at most 10 per minute, 50 per hour and 100 per day per user.
Calendly requires the lead's e-mail address to book. Leads without an e-mail cannot be booked automatically; a single-use Calendly booking link can be sent instead.
Bookings use the event type chosen in the settings: its duration, location and questions apply. Required booking questions other than a phone number must be made optional in Calendly. Paid and poll event types cannot be booked through the API.
Real-time updates (webhooks) need a paid Calendly plan (Standard or above). On the free plan Lumaa checks Calendly every 15 minutes instead.
Only the connected Calendly user's own events are read. Calendly has no API to move a booking: a reschedule made in Calendly shows up as a cancellation plus a new booking.
'Sign in with Calendly' is available once Lumaa enables its Calendly app; the personal access token option always works.
Apple iCloud Calendar
Beta
The AI checks your iCloud calendar (the Calendar app on iPhone and Mac) before offering viewing times and books agreed appointments straight into it. Moves and cancellations made in Apple Calendar flow back to Lumaa.
How you'll connect
Apple ID + app-specific password
In your Lumaa dashboard, once integrations open to customers:
Open account.apple.com (formerly appleid.apple.com) and sign in with your Apple ID.
Go to Sign-In and Security → App-Specific Passwords and choose 'Generate an app-specific password' (this needs two-factor authentication, which most Apple IDs already have).
Name it 'Lumaa' and copy the password Apple shows you.
Back here, enter your Apple ID e-mail and paste that password — your normal Apple password will not work — then click Connect.
Pick the calendar that should receive viewings and check your working hours. Done.
Apple has no calendar API or sign-in for other companies; Lumaa uses iCloud's standard CalDAV service with an app-specific password. Revoking that password at account.apple.com disconnects Lumaa immediately.
No real-time push: changes made in the calendar app reach Lumaa on the next poll (every 10 minutes).
Bookings are added as plain events. Lumaa does not send calendar invitations from this calendar; the lead's name, phone and e-mail are written in the event notes.
Recurring events are read for availability but never edited by Lumaa.
Apple does not publish iCloud CalDAV rate limits or document caldav.icloud.com in a developer reference; Lumaa follows iCloud's own discovery answers (partition hosts under icloud.com only).
DAV
CalDAV calendar
Beta
Connect any CalDAV calendar — Fastmail, Nextcloud, Yahoo, Zoho, Synology and more. The AI checks it before offering viewing times and books agreed appointments into it.
How you'll connect
Server address + username + password
In your Lumaa dashboard, once integrations open to customers:
Find your calendar's CalDAV address: Fastmail https://caldav.fastmail.com · Yahoo https://caldav.calendar.yahoo.com · Nextcloud https://<your-nextcloud>/remote.php/dav · others: search your provider's help for 'CalDAV'.
Create an app password in your provider's security settings (Fastmail and Yahoo require one; Nextcloud: Settings → Security → Devices & sessions).
Enter the address, your username (usually your e-mail) and the password, then click Connect.
Pick the calendar that should receive viewings and check your working hours. Done.
No real-time push: changes made in the calendar app reach Lumaa on the next poll (every 10 minutes).
Bookings are added as plain events. Lumaa does not send calendar invitations from this calendar; the lead's name, phone and e-mail are written in the event notes.
Recurring events are read for availability but never edited by Lumaa.
The server must be reachable on the public internet over HTTPS on port 443 or 8443. Redirects to another host are not followed — enter the final server address instead.
Rate limits differ per server and are not published by most of them; Lumaa stays at 2 requests per second.
Zoho Calendar
Coming soon
The AI checks your Zoho Calendar before offering viewing times and books agreed appointments straight into it, inviting the lead by e-mail. Moves and cancellations made in Zoho Calendar are picked up automatically. Works with every Zoho region, including the UAE and Saudi data centers.
How you'll connect
Sign in with Zoho is being enabled; Zoho Calendar can be connected once it is.
Good to know
Zoho Calendar has no change feed or push notifications: Lumaa re-reads the booking calendar (2 days back to 88 days ahead) every 15 minutes. Deleted events are confirmed one by one before a booking is marked cancelled.
Availability combines Zoho free/busy (all calendars included in free/busy) with the booking calendar's own events. It needs the Zoho account's e-mail address, which Lumaa reads from the Zoho sign-in ('email' permission).
All-day appointments are written as midnight-to-midnight timed events; recurring series are never edited or deleted by Lumaa.
ICS
iCal feed (read-only)
Read busy times from any calendar that can publish an iCal (ICS) link — Google, Outlook, Apple and more. Read-only: Lumaa uses it for availability, it cannot book into it.
How you'll connect
Calendar iCal link
In your Lumaa dashboard, once integrations open to customers:
Google: open Google Calendar → Settings → your calendar → copy 'Secret address in iCal format'.
Outlook: Settings → Calendar → Shared calendars → Publish a calendar → copy the ICS link.
Apple: in Calendar, share the calendar as a Public Calendar and copy its link.
Paste the link here and click Connect. Busy times appear within minutes.
Read-only: availability only. To let the AI book appointments, also connect Google, Outlook, Cal.com, Calendly or CalDAV.
Publishers refresh feeds on their own schedule (Google: up to several hours for some clients), so very recent changes may not show immediately.
Go
Goyzer
Via Custom Webhook
Dubai real-estate CRM. No public self-serve API; access is provisioned by Goyzer's account team.
How to connect it
Use the Custom Webhook integration (Goyzer's Zapier app or its lead-export webhook), or upload leads with a CSV link. A native connector is built on request once Goyzer issues API credentials for your account.
Pr
PropSpace
Via Custom Webhook
Dubai real-estate CRM. No public API.
How to connect it
Use the Custom Webhook integration or a CSV upload link. Listings published to Property Finder are available through the Property Finder integration.