Connect Hostaway and Map Listings

Connect Hostaway first, then map each external listing to the correct CleanOver unit. Accurate mapping keeps reservations, messages, jobs, and unit information aligned.

What you will accomplish

By the end of this guide, you will be able to complete a Hostaway listing connection from the correct CleanOver screen, understand the important checks before saving, and verify that the result is visible to the people who use it next.

Before you begin

• Have authorized Hostaway connection credentials available.
• Create the matching CleanOver units before mapping listings.
• Sign in to the Admin workspace and confirm you are in the correct business context.
• Use real operational dates and the property’s local timezone when the workflow includes time.

Step 1: Open Channels

Go to Channel Manager > Channels and select Hostaway. Review the current connection state before adding or replacing credentials.

Expected result: You know whether a Hostaway account is already connected.

Step 2: Connect the account

Use the Hostaway connection flow and enter the approved account credentials or token. Complete the connection and wait for the initial listing sync.

Expected result: Hostaway shows as connected.

Step 3: Review imported listings

Open Listing Mapping and wait for external listings to load. Search by listing name or provider ID when the account is large.

Expected result: The intended Hostaway listing is visible.

Step 4: Find the CleanOver unit

Confirm the internal unit’s alias, address, building, and unit number in Units before selecting it as the mapping target.

Expected result: The destination unit is unambiguous.

Step 5: Create the mapping

Pair one external listing with the correct unit. For combined or multi-unit listings, follow the business’s approved inventory design instead of guessing.

Expected result: The row shows the external and internal records together.

Step 6: Check for duplicate mappings

Search both the listing and unit to ensure neither is accidentally mapped in a conflicting way.

Expected result: One source listing feeds the intended unit relationship.

Step 7: Run or wait for synchronization

Allow reservations and listing data to sync. Review errors before continuing with additional mappings.

Expected result: The connection reports a healthy sync.

Step 8: Verify downstream data

Open Calendar Management, Jobs, and Messages for a known reservation. Confirm dates, unit, guest thread, and generated work match Hostaway.

Expected result: Connected data appears under the correct CleanOver unit.

How to confirm the workflow is complete

• Refresh the destination list or calendar and confirm the saved record appears only once.
• Check the unit, date, status, owner or assignee, and any linked record before leaving the page.
• Open the next downstream view mentioned in the guide and confirm it shows the same information.
• Record an internal note when the action corrects historical data or changes another person’s responsibility.

Common issues and what to do

The expected record is missing

Clear old filters, check the date and business context, then search by the most specific identifier available. If the data comes from a connected provider, check connection and mapping status before recreating it manually.

A button is disabled

Look for a required field, incomplete checklist item, missing permission, locked lifecycle status, or unresolved linked task. Complete the highlighted requirement instead of trying to bypass it.

The page shows different information after refresh

Another user or integration may have updated the record. Compare timestamps and the source system, then apply the correction in the system that owns the data.

You are unsure whether to continue

Stop before cancelling, overwriting, revoking, or issuing a financial document. Ask the workflow owner to confirm the intended outcome and add that decision to the internal record.

Best practices

• Use clear names that make sense to a new team member without extra context.
• Prefer the smallest safe scope for bulk actions, filters, permissions, and date ranges.
• Keep guest-facing communication separate from internal diagnostic notes.
• Verify a high-risk change in a second view before considering it finished.
• Update the source configuration when the same correction is needed repeatedly.