Text version. The interactive version, with live examples, is at https://app.proptonomy.ai/docs/integrations. This page as Markdown: https://app.proptonomy.ai/docs/integrations.md. Index of all pages: https://app.proptonomy.ai/llms.txt.
What syncs with each integration
For each PMS, task tool, key service, pricing tool and messaging channel: what Proptonomy reads, what it writes back, how often it syncs, and how to connect it.
https://app.proptonomy.ai/docs/integrations
Reading the tables
Each table is one kind of tool. A row is an integration, the Sync column says how often the two systems talk, and every other column is a kind of data.
Hover or tap a mark to see exactly what it covers, or the sync chips for the full schedule. Writes are changes Proptonomy makes in the other tool. Some happen on their own, such as a task’s status. Others only when you or the assistant act, such as pushing a property or blocking dates.
Property management systems
Your PMS stays the system of record for listings and bookings. Proptonomy reads them to run the work around each stay, and writes back where the PMS lets it.
- Guesty. How it syncs: Webhooks, plus a full sync every morning and two lighter syncs in the afternoon.
- Listings: Proptonomy reads and writes. Name, address, rooms, check-in and check-out times. Written when you push a property to Guesty. - Content: Proptonomy reads and writes. Descriptions, house rules, photos, amenities, Wi-Fi and parking. A push writes descriptions, property details, prices, Wi-Fi, parking notes, address, amenities and rooms; photos only for a new listing. The full list is under What a push to Guesty sends. - Bookings: Proptonomy reads and writes, partly. Dates, status, guests, channel and tags, with the guest's name, e-mail and phone. The assistant can move a guest's check-in or check-out after you approve it. - Notes: not synced. Booking notes and booking custom fields are not read yet. - Money: Proptonomy reads. Fare, fees, payout, refunds, payment fees, taxes and commission. - Blocks: Proptonomy reads and writes. Blocks are read, and set or lifted by you or the assistant. - Messages: Proptonomy reads and writes. Every message is read and replies are sent through Guesty. Messages from other channels can be copied into Guesty as internal notes (off by default). - Reviews: Proptonomy reads and writes, partly. Reviews are read. A reply is posted only after a team member approves it. Proptonomy never writes a review of a guest. - Tasks: Proptonomy reads and writes. Guesty tasks are read; tasks created in Proptonomy are created in Guesty, with status, schedule and comments kept in step. - Owners: Proptonomy reads and writes. Read on import. Pushing a property creates or assigns its owner. - Prices: Proptonomy reads and writes. Base price and cleaning fee. Written when you push a property.
- Hostaway. How it syncs: Webhook for bookings and messages, messages also checked every 3 minutes, a full sync daily.
- Listings: Proptonomy reads and writes. Name, address, capacity and rooms. A push also writes check-in and check-out hours. - Content: Proptonomy reads and writes, partly. Only photos are read. A push writes the description, house rules, amenities and Wi-Fi. - Bookings: Proptonomy reads. Dates, status, guests, check-in and check-out hours. With the guest's name, e-mail and phone. - Notes: not synced. Host and guest notes are not read yet. - Money: Proptonomy reads, partly. Total, host fee and cleaning fee. Not taxes. - Blocks: Proptonomy reads and writes. Blocks are read, and set or lifted by you or the assistant. - Messages: Proptonomy reads and writes. - Reviews: Proptonomy reads. Guest reviews. Replies are not posted to Hostaway. - Prices: Proptonomy writes. A push sets price, cleaning fee and minimum and maximum nights; the assistant can set a nightly price for dates. Prices are not read. - Not synced: Tasks, Owners.
- KrossBooking. How it syncs: Messages checked every 3 minutes, everything else every 6 hours.
- Listings: Proptonomy reads. Name, address, capacity, rooms, size and floor. - Content: Proptonomy reads, partly. Amenities and photos. Not descriptions or house rules. - Bookings: Proptonomy reads. Dates, status, guests, channel and arrival time. With the guest's name, e-mail and phone. - Notes: Proptonomy reads, partly. Booking custom fields (a cot, early check-in, door codes), refreshed for upcoming stays. Booking notes are not read yet. - Money: Proptonomy reads, partly. Total and currency. - Blocks: Proptonomy reads and writes. Blocks are read from the planner, and set or lifted by staff. - Messages: Proptonomy reads and writes. - Owners: Proptonomy reads. The owner register, linked to each unit. - Not synced: Reviews, Tasks, Prices.
- Lodgify. How it syncs: Webhooks for bookings and messages, messages also checked every 3 minutes, a sync three times a day.
- Listings: Proptonomy reads. Name, address, guest capacity, bedrooms, bathrooms, floor area in m² and active/inactive status when supplied by Lodgify. Missing values preserve existing data. Not check-in times. - Content: Proptonomy reads, partly. Listing descriptions and full room photo galleries. Existing staff photos are preserved. House rules, Wi-Fi and structured amenities are not imported by this sync. - Bookings: Proptonomy reads, partly. Dates, status and guests. Not the channel. With the guest's name, e-mail and phone. - Money: Proptonomy reads, partly. Total and currency. - Blocks: Proptonomy reads and writes, partly. Properties with a single room type only. - Messages: Proptonomy reads and writes. - Not synced: Notes, Reviews, Tasks, Owners, Prices.
- Smoobu. How it syncs: Live webhooks for booking changes and new messages, plus a full sync twice daily (04:00 and 14:00 UTC by default). Property details refresh during these passes; guest contacts for current and upcoming stays are refreshed on recurring imports. If webhooks are unavailable or the initial import is unfinished, sync is checked every 3 minutes. Proptonomy admins can also start separate property, reservation and conversation syncs. Full booking history, including cancellations, is read on each full pass.
- Listings: Proptonomy reads, partly. Names, addresses, coordinates, capacity, bedrooms and bathrooms when supplied. Missing fields preserve verified local values. The current property API does not provide floor area or active/inactive status. - Content: Proptonomy reads, partly. Amenities and bed summaries are retained as integration metadata. The current property API does not provide photos or descriptions; these can be added separately in Proptonomy and are preserved on sync. - Bookings: Proptonomy reads. Past and future bookings, dates, cancellations, guests, check-in/check-out times and booking references. Guest name, email and phone are imported. - Notes: Proptonomy reads, partly. Booking notices, language and guest-app links are retained in private integration metadata. - Money: Proptonomy reads, partly. Gross booking total and currency. Payment amounts and paid flags remain in private integration metadata. Separate fee, tax and payout accounting is not imported. - Blocks: Proptonomy reads. Owner blocks and grouped-property availability remain calendar blocks; they do not become financial bookings. - Messages: Proptonomy reads. Complete available booking conversation history, including guest messages and host replies. Messages matched to a live webhook use its first received time; retries and later syncs preserve it. API-only history uses Europe/Berlin source time, and display uses the organization timezone. Deleted or inaccessible booking threads cannot be imported. AI replies and sending to Smoobu are unavailable. - Tasks: not synced. PMS tasks are not imported. Normal Proptonomy booking automation may create local tasks. - Not synced: Reviews, Owners, Prices.
- Uplisting. How it syncs: Webhooks for bookings and properties, the inbox checked every 2 minutes, a sync three times a day.
- Listings: Proptonomy reads, partly. Name, capacity and rooms. Not the address. - Bookings: Proptonomy reads, partly. Dates, status, guests and arrival times. Not the channel. With the guest's name, e-mail and phone. - Money: Proptonomy reads. Total, commission and cleaning fee. - Blocks: Proptonomy reads and writes. Availability. - Messages: Proptonomy reads and writes. Needs the Uplisting inbox connection. AI replies to these are off by default. - Not synced: Content, Notes, Reviews, Tasks, Owners, Prices.
- Booking Automation. How it syncs: Checked every 5 minutes; current and upcoming stays re-read every 30 minutes for their booking icons.
- Listings: Proptonomy reads, partly. Units you choose at connect, with their check-in and check-out times. The address is the one you confirm at connect. - Content: Proptonomy reads. Description, house rules, amenities and cleaning fee, filled where Proptonomy has none; photos when Booking Automation provides them. - Bookings: Proptonomy reads and writes. Dates, status, guests and channel, with the guest's name, e-mail and phone. With the write switch on, staff can create a booking, change a direct booking's dates or cancel it, each confirmed first, and automations can set a booking's flag and status. - Notes: Proptonomy reads and writes. Host notes, the guest's comments and arrival time, the booking's flag, and booking info codes (the icons). With the write switch on, staff and automations can add or remove an info code and automations can set the flag. - Money: Proptonomy reads. Total, tax and commission, when the invite may read financials. - Blocks: Proptonomy reads and writes. Blocks are read; with the write switch on, set or lifted by staff or the assistant as a blocked booking on the unit. - Messages: Proptonomy reads. Guest and host messages with attachments. Replies are sent in Booking Automation. - Reviews: Proptonomy reads. Airbnb and Booking.com guest reviews. Replies are not posted. - Not synced: Tasks, Owners, Prices.
- Resly. How it syncs: Webhooks, plus a sync three times a day.
- Listings: Proptonomy reads. Room types: name, address, occupancy and rooms. - Bookings: Proptonomy reads. Dates, status, guests, times and channel reference. With the guest's name, e-mail and phone. - Money: Proptonomy reads, partly. Total and currency. - Blocks: not synced. Resly blocks are neither read nor written. - Messages: not synced. Resly has no guest messages to connect. - Not synced: Content, Notes, Reviews, Tasks, Owners, Prices.
- AndHamlet. How it syncs: Checked three times a day.
- Listings: Proptonomy reads. Name and address. - Content: Proptonomy reads, partly. Photos, and the English description where yours is empty. - Bookings: Proptonomy reads. Owner stays: dates, guests and status. The share owner on the stay, with name, e-mail and phone. - Owners: Proptonomy reads. Share owners, and the house manager as a contact. - Not synced: Notes, Money, Blocks, Messages, Reviews, Tasks, Prices.
- Hybel.no. How it syncs: Messages daily, maintenance every 30 minutes, properties and tenants hourly.
- Listings: Proptonomy reads. Name, address, floor and unit number. - Bookings: Proptonomy reads, partly. Rental contracts, as long-term leases. Only the tenant's name. - Money: Proptonomy reads, partly. Monthly rent. - Messages: Proptonomy reads and writes. Messages with tenants; internal notes are posted as staff comments. - Tasks: Proptonomy reads. Maintenance cases become maintenance tasks. - Not synced: Content, Notes, Blocks, Reviews, Owners, Prices.
What a push to Guesty sends
A push writes the property's approved values to its Guesty listing. Pushing a property with no linked listing creates a new listing, unlisted, so you can check it in Guesty before it goes live. Fields left empty in Proptonomy are not sent.
Sent on every push:
- Guest-facing title and internal name.
- Descriptions: summary, house rules, the space, guest access, neighbourhood, getting around and other notes.
- Property type and room type, translated to Guesty’s own list.
- Maximum guests, living space (sent in square feet) and tags.
- Base price, cleaning fee and currency.
- Minimum and maximum nights.
- Check-in and check-out times.
- Parking notes.
- Wi-Fi name and password.
- Address: full address, street, unit, floor, postcode, city, region, country and the map position.
- Amenities, from the Amenities step.
- Rooms and beds, as Guesty Spaces. On an existing listing, rooms are added, never removed.
- Listing taxes, on an existing listing only, and only when your organization’s standard property settings define them. Owners never supply taxes, and nothing is sent when no standard is set.
Sent only when the push creates the listing: photos, in gallery order, so the first photo becomes the cover. Later pushes never send photos, so a gallery arranged in Guesty is never overwritten.
Never sent:
- The number of bedrooms and bathrooms. Guesty rebuilds its rooms to match those counts, which would wipe the rooms Proptonomy sends, so Guesty takes them from the rooms instead.
- The parking type choice; only the parking notes text is sent.
- Your own profile questions (for example lockbox, mailbox, local registration or check-in texts). They stay in Proptonomy, where the assistant and your team use them.
Task and operations tools
Task tools stay in step with Proptonomy's own tasks. Knowledge sources are read so the assistant can answer from them.
- Breezeway. How it syncs: Pulled within minutes of Breezeway's notification e-mails, plus sweeps through the day.
- Properties: Proptonomy reads, partly. Breezeway homes are linked to your properties. Their details and inventory go into knowledge if you switch it on. - Bookings: Proptonomy reads, partly. Only to link a task to its booking. - Tasks: Proptonomy reads and writes. Created, edited, finished, reopened and cancelled, kept in step both ways. - Checklists and photos: Proptonomy reads and writes, partly. Checklist results and photos are read, and the AI checks the photos. Photos added in Proptonomy are attached in Breezeway. Checklist answers are not written. - Comments: Proptonomy reads and writes. - Team: Proptonomy reads and writes. Breezeway people become contacts; assignees are written back. - Not synced: Knowledge.
- SuiteOp. How it syncs: Checked every 30 minutes.
- Bookings: Proptonomy reads, partly. Looked up for the booking card, not stored. - Tasks: Proptonomy reads and writes, partly. Tasks are read; title, description, status, priority and dates are written back. New tasks are not created in SuiteOp. - Team: Proptonomy reads. Users become contacts. - Not synced: Properties, Checklists and photos, Comments, Knowledge.
- Airtable. How it syncs: Every 30 minutes.
- Knowledge: Proptonomy reads. Records from one base and table. - Not synced: Properties, Bookings, Tasks, Checklists and photos, Comments, Team.
- Notion. How it syncs: When a shared page changes, plus nightly.
- Knowledge: Proptonomy reads. The pages you share with Proptonomy, and their subpages. - Not synced: Properties, Bookings, Tasks, Checklists and photos, Comments, Team.
You can also attach a file or share a document link in a conversation. See What can Proptonomy read? (https://app.proptonomy.ai/docs/what-can-proptonomy-read) for spreadsheets, images, PDFs and other supported sources.
Guest experience and keys
Check-in apps and key services hold what a guest needs to get in. Proptonomy reads their status so the team and the assistant can see it, and acts where the tool allows.
- Enso Connect. How it syncs: Listing content nightly; everything else live when you or the assistant open it.
- Bookings and guests: Proptonomy reads. The guest, their bookings and bill items. - Check-in and ID: Proptonomy reads and writes. Verification steps and the boarding-pass link are read. Staff can skip an ID or agreement step, reset steps or release check-in. - Keys and codes: Proptonomy reads, partly. Check-in and check-out steps and Wi-Fi are copied into knowledge. The boarding-pass view never shows codes. - Upsells and fees: Proptonomy reads and writes, partly. Upsells, fees, deposits and pending actions are read. A deposit or damage-waiver fee can be waived. - Guest messages: Proptonomy writes, partly. Staff can send the boarding-pass link through Enso. Messages in Enso are not read.
- Chekin. How it syncs: Live, when the assistant looks a guest up.
- Bookings and guests: Proptonomy reads. - Check-in and ID: Proptonomy reads. Registration, ID verification and police status, and the online check-in links. - Upsells and fees: Proptonomy reads, partly. Deposit and tax status. - Not synced: Keys and codes, Guest messages.
- ChargeAutomation. How it syncs: Arrivals from yesterday through the next 14 days every 30 minutes, or on request; deposits, payments, verifications and upsells live through webhooks.
- Bookings and guests: Proptonomy reads, partly. Matched to your Booking Automation reservations by booking id; guest phone and email as given in ChargeAutomation. - Check-in and ID: Proptonomy reads. Whether pre-check-in is completed, the guest's own pre-check-in link, and ID verification. - Upsells and fees: Proptonomy reads. Security deposit holds, payments, card verification and upsells, as ChargeAutomation reports them. - Not synced: Keys and codes, Guest messages.
- KeyNest. How it syncs: The key list every 30 minutes; codes live when asked.
- Keys and codes: Proptonomy reads and writes. Keys, valid codes and store details are read. A new collection code is booked only when staff ask for one (KeyNest Points). - Not synced: Bookings and guests, Check-in and ID, Upsells and fees, Guest messages.
- EasyPick. How it syncs: Live, when asked.
- Keys and codes: Proptonomy reads. Keys, pickup codes and pickup and drop-off status. - Not synced: Bookings and guests, Check-in and ID, Upsells and fees, Guest messages.
Pricing and supplies
Pricing tools are opened on demand. The linen supplier keeps stock and deliveries in step.
- PriceLabs. How it syncs: On demand, when you or the assistant open it.
- Listings: Proptonomy reads. - Bookings: Proptonomy reads. - Prices: Proptonomy reads and writes. Recommended prices, each night's minimum stay and check-in and check-out rules, and date overrides are read; base, minimum and maximum prices and date overrides can be set. - Not synced: Orders and deliveries.
- Wheelhouse. How it syncs: On demand, when you or the assistant open it.
- Listings: Proptonomy reads. Listings, with occupancy and rate figures. - Bookings: Proptonomy reads. - Prices: Proptonomy reads and writes. Recommendations and custom rates are read; base price, minimum price and stay, custom rates and auto-posting can be set. - Not synced: Orders and deliveries.
- Nortekstil. How it syncs: Every 6 hours, and on demand.
- Orders and deliveries: Proptonomy reads and writes. Orders, products and delivery days are read. Draft orders are created and submitted after you confirm. - Not synced: Listings, Bookings, Prices.
Messaging channels
Where guests, owners, partners and your team talk to Proptonomy. A channel carries messages, so the columns are about what moves through it.
- E-mail. How it syncs: Microsoft 365 instantly, Gmail every 2 minutes, Proptonomy's own address instantly.
- Messages: Proptonomy reads and writes. Microsoft 365 and Gmail mailboxes and Proptonomy's own address arrive in the inbox, and replies go out in the same thread. An IMAP mailbox is read only when the assistant looks. Mail is never marked as read. - Photos and files: Proptonomy reads and writes, partly. Received from Microsoft 365 and Proptonomy's own address, not from Gmail. Sent from every kind of mailbox. - Read and delivery status: Proptonomy reads, partly. Delivery reports for mail sent from Proptonomy's own address. - Not synced: Group chats, Contacts.
- WhatsApp. How it syncs: Instantly.
- Messages: Proptonomy reads and writes. Sent messages can be edited and deleted. - Photos and files: Proptonomy reads and writes. Photos, files and video. - Group chats: Proptonomy reads and writes, partly. Groups and their members are read. Proptonomy joins a group from an invite link. - Contacts: Proptonomy reads. Names and profile pictures. - Read and delivery status: Proptonomy writes. Read receipts and typing are shown to the sender.
- WhatsApp Business Platform. How it syncs: Instantly through Meta webhooks.
- Messages: Proptonomy reads and writes, partly. Direct messages and operator-sent approved templates. Free-form replies need an open 24-hour window; this is not a promise of free delivery. Sent messages cannot be edited or deleted through this connection. - Photos and files: Proptonomy reads and writes. Photos, video, audio and documents on direct messages. - Contacts: Proptonomy reads, partly. Profile names received with new messages; old contacts and chat history are not imported. - Read and delivery status: Proptonomy reads. Delivery, read and failure updates from Meta. - Not synced: Group chats.
- Telegram. How it syncs: Instantly.
- Messages: Proptonomy reads and writes. Sent messages can be edited. - Photos and files: Proptonomy reads and writes. Photos and documents. - Group chats: Proptonomy reads. Group chats and their admins. - Contacts: Proptonomy reads. - Read and delivery status: Proptonomy writes. Reactions and typing.
- Slack. How it syncs: Instantly.
- Messages: Proptonomy reads and writes. Channels, direct messages and threads. - Photos and files: Proptonomy reads and writes. - Group chats: Proptonomy reads. Channels and their members. - Contacts: Proptonomy reads. - Not synced: Read and delivery status.
- LINE. How it syncs: Instantly.
- Messages: Proptonomy reads and writes. - Photos and files: Proptonomy reads and writes, partly. Photos, video and audio. Documents go out as links. - Group chats: Proptonomy reads. - Contacts: Proptonomy reads. - Read and delivery status: Proptonomy writes. Messages are marked read, with a loading indicator.
- Microsoft Teams. How it syncs: Instantly.
- Messages: Proptonomy reads and writes. - Photos and files: Proptonomy writes, partly. Attachments sent to Proptonomy are not read. Files go out as links. - Contacts: Proptonomy reads. The member list, when you import it. - Not synced: Group chats, Read and delivery status.
- SMS and calls. How it syncs: Instantly, through Twilio or Telnyx.
- Messages: Proptonomy reads and writes. Text messages in and out, with opt-out. Calls in and out, with recordings. - Photos and files: Proptonomy reads, partly. Picture messages are noted but not downloaded. Outgoing messages are text only. - Read and delivery status: Proptonomy reads. Delivery reports. - Not synced: Group chats, Contacts.
For separate owners and guests numbers, see WhatsApp Business setup (https://app.proptonomy.ai/docs/whatsapp#business-numbers). The same guide explains Meta's message pricing (https://app.proptonomy.ai/docs/whatsapp#platform-pricing) and messaging limits (https://app.proptonomy.ai/docs/whatsapp#platform-limits).
Booking Automation: which field holds what
When staff ask the assistant to put something on a Booking Automation booking, this is where each thing goes and which action sets it. Anything not listed here cannot be set from Proptonomy and is done in Booking Automation.
- New booking: CreateBookingAutomationReservation, always confirmed. It sets the unit, dates, adults and children, guest first and last name, email and phone (only when staff gave them) and price (the booking total, recorded as the booking's price and as its "Reservation Charge" line under Charges, where staff read it; nothing is charged to the guest).
- Referrer (Booking Automation's Referrer field, for example "direct"): the referrer value on CreateBookingAutomationReservation.
- Unpaid, verified or any other visual marker: the booking's flag, a label of up to 32 characters with a colour. On a new booking use flagText and flagColor on CreateBookingAutomationReservation, for example UNPAID in red (ff0000). Booking Automation has no "unpaid" status: a confirmed booking flagged UNPAID is how staff mark one. On existing bookings the flag is set only by a published automation (SetBookingAutomationFlag).
- Internal note (for example "Payment did not go through on SiteMinder"): the note value on CreateBookingAutomationReservation, saved in the booking's Notes.
- A reference from another system (a SiteMinder, channel or booking-engine reference): the reference value, saved in Notes as "Reference: …".
- Info codes and icons ($ = I-DOLLAR-SIGN, early check-in, parking and the like): SetBookingAutomationInfoCode on an existing booking, with a staff preview and yes; by an automation, SetBookingAutomationInfoCodeFromAutomation.
- New dates or a cancellation of a direct booking: ChangeBookingAutomationReservation. Channel bookings (Airbnb, Booking.com, Agoda) are changed on the channel.
- Not settable from Proptonomy: guest comments, the guest message, custom fields, payments, deposits and invoices, and Booking Automation's own auto actions. Staff do these in Booking Automation.
Booking Automation: rebuild its auto actions
Booking Automation's own auto actions cannot be read, listed or triggered by Proptonomy, because Booking Automation's API does not support it. Those that set a booking's flag or an info code can be rebuilt as a Proptonomy automation. Every other action, including guest emails, keeps running in Booking Automation, or staff press Send Now there.
A Booking Automation booking carries its own fields under reservation.bookingAutomation: channel, apiSource, flagText, flagColor, infoCodes, notes and guestComments. A change to the flag, the info codes or the notes fires reservation.updated. Most Booking Automation actions start on a new booking; use the events reservation.created and reservation.updated for those. Each write is a Use an agent action step whose values come from the step's own settings, never from AI-written text, and a step whose change is already on the booking is skipped as unchanged, so its own reservation.updated never loops.
Flags. Booking Automation: on booking, Airbnb, set the flag to Verified & Paid and the status to Confirmed. Proptonomy: When an event occurs, reservation.created and reservation.updated; Only if reservation.bookingAutomation.channel === "airbnb"; step SetBookingAutomationFlag with flag text Verified & Paid, colour 0000ff and status confirmed. Cancelled, blocked and inquiry bookings never change status. An action that depends on the payment balance cannot be rebuilt yet.
Info icons. Booking Automation: on booking, when Notes contain Upsell Purchased Parking, add I-PARKING. Proptonomy: the same events; Only if contains(reservation.bookingAutomation.notes, "Upsell Purchased Parking") && !contains(reservation.bookingAutomation.infoCodes, "I-PARKING"); step SetBookingAutomationInfoCodeFromAutomation with code I-PARKING. Tick remove to take a code off instead.
How to connect
Connections are made under Settings → Integrations by an admin, or in the PMS's own connect wizard. Most take minutes; we set them up with you.
Property management systems:
- Guesty: Click Connect on the Proptonomy tile in the Guesty Marketplace. That authorises Guesty's official partner connection; there are no API keys to create.
- Hostaway: Open Proptonomy in the Hostaway Marketplace, select Create API Key, then confirm with Create. Copy the Account ID and API key into Proptonomy before closing the dialog. Hostaway shows the key only once.
- KrossBooking: Sign in through Proptonomy's connect wizard with the hotel ID, username and password you use in KrossBooking, plus the e-mailed code if two-factor is on.
- Lodgify: In Lodgify, create a key under Settings → Public API and paste it into Proptonomy's connect wizard.
- Smoobu: Create a signed API key and secret in Smoobu Settings → Advanced → API Keys, then enter both in the Proptonomy connect wizard. Smoobu shows the secret once.
- Uplisting: In Uplisting, create an API key under Settings → API and paste it into Proptonomy's connect wizard. Guest messaging also needs Uplisting's messaging connection, which we switch on with you.
- Booking Automation: In Booking Automation, open Settings → Marketplace → API and generate an invite with properties, bookings and booking personal data (read; write as well, plus inventory, to let Proptonomy write), plus linked properties. Paste it into Proptonomy's connect wizard and review which units are your homes. Nothing is written until an admin turns on “Let Proptonomy write to Booking Automation”.
- Resly: In Resly, create an API key under Settings → Integrations, then enter your account ID and the key in Proptonomy's connect wizard.
- AndHamlet: Enter the e-mail and password you use for AndHamlet's admin in Proptonomy's connect wizard.
- Hybel.no: Enter your Hybel.no login under Settings → Integrations. Add each landlord account you manage.
Task and operations tools:
- Breezeway: Enter a Breezeway user's e-mail and password under Settings → Integrations (a dedicated user works well), then choose what syncs and whether tasks are written back.
- SuiteOp: Enter your SuiteOp workspace e-mail, region and API key under Settings → Integrations. SuiteOp has to enable API access for your account.
- Airtable: Create a personal access token in Airtable scoped to your base, paste it under Settings → Integrations and pick the base, table and (optionally) view.
- Notion: Authorise Proptonomy in Notion under Settings → Integrations and pick the pages and databases to share. You can add or remove pages later.
Guest experience and keys:
- Enso Connect: Enter your Enso Connect login under Settings → Integrations, next to your PMS connection.
- Chekin: Paste the API key Chekin support issues for you under Settings → Integrations.
- ChargeAutomation: Paste the API key from ChargeAutomation's API settings under Settings → Integrations.
- KeyNest: Paste your KeyNest API key under Settings → Integrations, then link each key to its property.
- EasyPick: Enter the phone number and password you use for EasyPick under Settings → Integrations. Keys named after your properties are matched automatically.
Pricing and supplies:
- PriceLabs: Create an API key in PriceLabs and paste it under Settings → Integrations. Proptonomy checks it by listing your properties.
- Wheelhouse: Create an RM API key under Api Key in your Wheelhouse account and paste it under Settings → Integrations.
- Nortekstil: Set up with the Proptonomy team for your Nortekstil customer account; it then shows under Settings → Integrations.
Messaging channels:
- E-mail: Sign in with Microsoft or Google under Settings → Integrations and pick the mailbox; shared mailboxes work. Other mail servers connect over IMAP and SMTP.
- WhatsApp: Two ways. Add Proptonomy's WhatsApp number to a group, or message it, and click the connect link it posts, once per chat. Or pair your organization's own WhatsApp number by scanning a QR code under Settings → Integrations → Chat channels, as with WhatsApp Web; direct guest chats then go out from your number.
- WhatsApp Business Platform: An organization admin uses Settings → Integrations → WhatsApp Business Platform → Connect with Facebook. Authorize the business account and verify the number. Use Connect another number for an owners line and a guests line; route each connection to its own inbox. Meta message charges and limits apply. Use Keep using the WhatsApp Business app when Meta offers coexistence.
- Telegram: Add the Proptonomy bot to a group and click the connect link it posts. A partner without a group gets a personal invite link from their contact.
- Slack: Click Add to Slack under Settings → Integrations, then invite Proptonomy to the channels it should work in.
- LINE: Add the Proptonomy LINE account and connect each chat with the code from your workspace, or bring your own LINE official account.
- Microsoft Teams: Upload Proptonomy's app package in your Teams admin center, then add Proptonomy to the channels it should work in.
- SMS and calls: Connect your Twilio or Telnyx account under Settings → Integrations, then import the numbers it owns or buy one per country.
Limits worth knowing
- A read-only connection writes nothing to calendars or listings. Set an integration to read-only and Proptonomy refuses those writes.
- The assistant does not delete listings, cancel bookings or change payments in your PMS. Those stay with a person in the PMS itself.
- Replies to reviews wait for a person. A review reply is drafted, and posted only after a team member approves it.
All documentation pages
- Testing with AI guests — Enable a demo sandbox, play guest scenarios and test an approved partner connection with simulated reservations.
- What can Proptonomy read? — Images, PDFs, Excel, Google Sheets and SharePoint links, documents, recordings and the data in your connected workspace.
- White-label setup and custom domains — Preparing a provider or organization workspace, DNS, branding, sign-in and API access during the controlled rollout.
- Working for a client — How a cleaning or maintenance company receives a client's tasks in its own workspace, and what it sees of the client.
- Roles and what they can do — The six roles, which one to give whom, and a live view of what each role can read and change.
- Inviting people and managing roles — Inviting a coordinator or a cleaner, accepting the invitation, changing a role, and property scopes.
- Receiving and delegating tasks — Where a client's tasks appear, how a coordinator hands one to a cleaner, and what the client sees back.
- The app for cleaners — Inviting staff, installing the iPhone or Android app, signing in, and taking a task from Start work to Finish.
- Location sharing — What the app records about where people are, with whose consent, and what a coordinator sees in the Command Center.
- WhatsApp: teams and business numbers — Connect business numbers for owners and guests, understand Meta's pricing and limits, and work with your team from WhatsApp.
- Setting up connected chats — Chat type, who each chat is with, the properties it is about and everyone's role, so a request for the owner reaches the owner group and not the cleaners.
- Languages and translation — The relay that re-posts every group message in each language, your inbox language, translating one message, and the language the AI writes in.
- Setting up the property profile — The field pool, the structure and the Express, Full and Continuation forms; the built-in fields to use instead of custom copies; field options, show-when rules, translations and publishing.
- SOPs and automation triggers — Start SOPs, automatic tasks and messages from events, schedules or webhooks, with typed conditions and assistant chat commands.
- What syncs with each integration — For each PMS, task tool, key service, pricing tool and messaging channel: what Proptonomy reads, what it writes back, how often it syncs, and how to connect it.