Linking Lodgify as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
This source is currently in alpha. The interface and available tables may change.
The Lodgify connector syncs properties, bookings, and rooms from your Lodgify vacation rental account into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
A Lodgify account with API access enabled. You need an API key from your Lodgify dashboard – read access is enough for syncing data.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
Enter your Lodgify API key to connect your account.
To generate an API key:
- Log in to your Lodgify dashboard.
- Go to Settings > Public API.
- Copy the API key.
Back in PostHog, paste the API key and click Next. Select the tables you want to sync, choose a sync method and frequency, then click Import.
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
The properties and bookings tables support incremental syncing using updated_at as the replication key. The rooms table only supports full refresh because the Lodgify API does not provide a time-based filter for rooms.
To remove deleted properties from an incrementally synced table, run a full refresh sync.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
properties | Rental properties with location, prices, room types, and account status. | Incremental, Full refresh | updated_at | — |
bookings | Bookings across all stay dates, including trash, transaction details, and quote details. | Incremental, Full refresh | updated_at | — |
rooms | Room types for each property, with capacity, amenities, and prices. | Full refresh | — | — |
Troubleshooting
If the connection fails with an authorization error, the API key is incorrect or has been revoked. Copy a new key from Settings > Public API in your Lodgify dashboard, then reconnect the source.
If the connection fails with a permission error, your Lodgify account may not have API access enabled. Check your account's API access settings and reconnect.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.