Skip to main content

How to use and configure the Aloware-Guesty integration

Aloware–Guesty integration syncs reservation data with communication tools, giving teams unified access to guest details and activity.

Laarni D avatar
Written by Laarni D
Updated yesterday

Understanding the Aloware–Guesty integration

The Aloware–Guesty integration connects Guesty reservation data with Aloware’s communication tools. It allows teams to manage calls, messages, and guest information in one place. The reservation card in Aloware displays key booking details such as confirmation codes, check-in and check-out dates, listing IDs, and guest counts, giving users the context they need while communicating with guests.

Admins can also manage how data flows between systems through direction-based sync settings. This includes the sync direction and contact update prevention feature, which gives admins the option to block Aloware from updating Guesty contacts. This helps maintain accurate reservation information and prevents unwanted overwrites.

Before you begin, ensure you have:

  • Aloware admin access to configure integrations

  • Guesty API credentials

  • A unique UUID for each Guesty account if you are using a multi-account setup


What problem this solves

Teams often switch between platforms to retrieve reservation data and interact with guests. This increases the chance of missed updates, duplicated records, and inconsistent contact information.

This integration helps by:

  • Keeping guest details, reservations, and communication in sync

  • Reducing errors caused by outdated or modified contact records

  • Preventing Aloware from unintentionally updating Guesty reservation contacts

  • Providing faster access to reservation information and communication logs


How business admins can use this

Admins can configure how reservation and contact data moves between systems, automate guest communication, and manage call and message logs inside Guesty.

Common use cases include:

  1. Automated messaging
    Trigger booking confirmations, reminders, or other updates based on Guesty reservation activity.

  2. Sync direction settings
    Choose how Aloware and Guesty exchange contact data:

    1. Inbound (Guesty → Aloware) - Guesty sends updates to Aloware only

    2. Bidirectional (↔) - Both systems can update contact information

  3. Activity visibility
    Aloware calls, SMS, and summaries appear inside Guesty’s inbox conversations to help staff see communication history alongside reservation details.

  4. Filtering options
    Admins can select which events sync, such as calls, SMS, emails, notes, appointments, and disposition statuses. Additional controls allow filtering by duration, skipping certain lines, or syncing only qualified contacts.


Step-by-step configuration

Step 1: Open the Guesty integration settings

  1. Log in to your Aloware Admin Dashboard.

  2. Go to Integrations → Guesty.

  3. Open the Settings panel for the Guesty integration.

  4. Click Connect to generate your Guesty API token.

  5. Copy the API token provided by Guesty.

  6. Paste the token into Aloware to authorize and connect your Guesty account.

Once the token is accepted, the Aloware–Guesty integration will show as Successfully Connected.


Step 2: Review contact sync options

In the Contact Sync Settings section, you can control how Guesty and Aloware manage contact data. These settings determine whether each system can create new contacts or update existing ones during the sync.

You will see options that control:

  • Whether Guesty or Aloware can create new contacts

  • Whether either system can update existing contact information

  • Whether sync runs in one direction (← Inbound) or in both directions (↔ bidirectional)

These settings help ensure that reservation-related contact information in Guesty remains accurate.

Recommended default: Both systems can update contact information (↔ bidirectional), but as a best practice, Aloware should not create new contacts in Guesty (use Inbound ←) to prevent accidental data duplication.

This keeps Guesty as the main source for contact creation while still allowing information updates to reflect in both systems.


Step 3: Configure sync direction

In this step, choose how data flows between Guesty and Aloware. This determines whether contacts can be updated in one direction or in both systems.

To prevent Aloware from modifying any contact information stored in Guesty:

  1. Set the sync direction to Inbound only: Guesty → Aloware (←)

  2. Keep Inbound enabled so all Guesty-created contacts continue syncing into Aloware.

With this configuration, Guesty remains the source of truth for reservation records, while Aloware receives updated guest information without sending any changes back to Guesty.


Step 4: Test the configuration

After saving your settings, run a quick test to confirm the sync direction is working as expected.

  1. Update a contact in Guesty
    Make a small change such as updating the guest’s phone number or name. This update should appear in Aloware once the sync completes.
    (Inbound: Guesty → Aloware)

  2. Update the same contact in Aloware
    Make a similar change in Aloware. This update should not appear in Guesty if Inbound-only sync is correctly configured.

You can also use Manual Sync to speed up verification and confirm that data is flowing in the correct direction.


Step 5: Validate contact creation behavior

If you disabled contact creation from Aloware to Guesty, confirm that Guesty remains the source of truth.

  1. Create a new contact in Aloware

    Add a test contact with basic information.

  2. Check Guesty

    • Verify that this new contact does not appear in Guesty.

    • This confirms that Aloware cannot create new Guesty records under your selected settings.

    This step ensures that all new contacts originate from Guesty only, maintaining consistent reservation and guest records.


How users interact with this integration

Once the integration is active, team members can access Guesty reservation data directly inside Aloware while communicating with guests. This lets users stay in one workspace without switching between platforms.

With the integration, users can:

  • Make calls and send messages to guests from a single interface.

  • View reservation details through the Guesty reservation card in Aloware.

  • Open the booking in Guesty by clicking the reservation link.

  • See all reservations associated with the same contact, when applicable.

  • Access accurate, up-to-date guest information while handling conversations.

The reservation card displays key details such as the confirmation code, reservation number, check-in and check-out dates, listing ID, number of guests, currency, and total income.


How this relates to other tools

The Guesty integration works alongside other connected systems, such as CRMs. For example, if you use HubSpot with Aloware, guest activity from Aloware can update HubSpot contact records without requiring manual entry. The integration supports unified communication workflows across departments and tools.

Did this answer your question?