Integrations
Akiles integrates with external platforms in two ways:
- Sync integrations automate member creation and access management. They connect to property management systems (PMS) or identity providers and keep Akiles members in sync with reservations or user accounts on the external side.
- Notification integrations push messages out of Akiles. They watch for events and alerts inside Akiles and deliver them to a chat platform of your choice (Discord, Slack, Telegram).
A single integration is either a sync integration or a notification integration. You can have any number of integrations of either kind.
Sync integrations
When a sync integration is connected, Akiles can automatically:
- Create and update members based on reservations or user accounts in the external platform.
- Assign members to the correct groups based on resource mappings you configure.
- Set access validity periods (start and end dates) automatically.
- Provision opening methods such as PINs and Magic Links.
- Remove access when a reservation ends or a user is removed from the external platform.
Available sync integrations:
- Guesty — Vacation rental and property management.
- Cloudbeds — Hotel and short-stay property management.
- Nexudus — Coworking space management.
- Google Workspace — Sync members from your organization’s Google directory.
- SCIM — Sync members and groups from any SCIM 2.0 identity provider (Okta, Azure AD, JumpCloud, etc.).
How sync integrations work
All sync integrations follow the same general flow:
- Connect — Link your external account to Akiles from the integration settings page. Each integration has its own connection method (OAuth, marketplace install, or API token).
- Map resources — The integration imports resources from the external platform (listings, groups, tariffs, etc.). You map each resource to one or more Akiles member groups to control which doors members can access. See Resource mappings below.
- Automatic sync — Akiles periodically syncs members from the external platform. Members are created, updated, or removed automatically. Webhooks provide near-instant updates when changes happen on the external platform.
Resource mappings
A mapping connects one resource to one Akiles member group. It is what turns a reservation or a user account into access to real doors. A resource with no mapping gives no access, and its members are not synced.
You can map a resource to more than one group. Members of that resource get access to every group in the list. For example, an apartment can map to both an “Apartment 101” group and a shared “Lobby” group.
Time modifiers
Each mapping has two optional time modifiers, one for the start of the access period and one for the end:
- Offset — Adds time. Use a negative value to move the time earlier.
- Set time — Replaces the time of day and keeps the same day.
If you set both, the set time applies first and the offset applies after it.
A modifier changes only the group it belongs to. The other groups of the same resource keep the original period. This is how you give a guest the apartment door for exactly the reservation, and the lobby door for a longer period:
| What you want | How to set it |
|---|---|
| Lobby access from 1 hour before check-in until 1 hour after check-out | Start offset -60 minutes, end offset +60 minutes |
| Lobby access until 21:00 on the day of check-out | Set end time to 21:00 |
The member’s own validity period grows to include the modified periods. If the lobby ends 1 hour after check-out, the member stays valid for that hour.
A modifier does nothing when that end of the period has no date. Google Workspace and SCIM members have no start or end date, so time modifiers have no effect on them.
Which local time “set time” uses
A set time is a local time, not UTC. Akiles finds the timezone in this order, and uses the first one it finds:
- The timezone the external platform reports for the property (Guesty listings, Cloudbeds properties and Avantio accommodations all report one).
- The timezone of the site of the member group.
- The timezone of the first site of your organization.
Common settings
All integrations share these settings:
- Enabled — When disabled, the integration stops doing any work. For sync integrations, member creation/updates/deletion stops; existing members remain and can continue to be used. For notification integrations, message delivery stops.
- Member sync scope — (Sync integrations only.) Choose whether to sync all members, or only those valid within a certain number of days from now. This is useful for PMS integrations where you only want to sync upcoming reservations.
Member sync status
Each integration member shows a sync status:
- Synced — The member was successfully created or updated in Akiles.
- None — The member was not synced. This can happen if no resource mapping matches, or if the member has a skip reason (e.g. reservation not confirmed, user suspended).
You can view the skip reason for each member in the integration member list to understand why a member was not synced.
Notification integrations
When a notification integration is connected, Akiles can push messages to an external chat platform whenever something happens — a door opens, an admin makes a change, or a hardware alert fires.
Available notification integrations:
- Discord — Post to a Discord channel via webhook.
- Slack — Post to a Slack channel.
- Telegram — Send messages to a Telegram chat or group.
All notification integrations share the same set of toggles and rules. See Notification rules for how to control which events get delivered.