Skip to main content

Macros Management

We’re launching a new Macros page to manage all property macros—both PMS-imported and custom—in one centralized place.

Overview

The Macros page lets customers view, add, and manage macros per unit. It simplifies handling both synced (PMS-imported) and unsynced (custom) macros.

Macro Types

  • Import Field: Pulled from supported PMS systems

  • Custom Field: Manually created by the user

Page Features

1. Add Import Field
​
The Add Import Field button allows customers to add property macros that are imported directly from their connected PMS (Property Management System). These fields automatically pull in dynamic property-specific data, such as address, number of bedrooms, or amenities.
​


​Note: This button is only visible for customers using PMS platforms that support field importing. It is not available for VR, OwnerRez, Hospitable, or Hostaway.
​

2. Add Custom Macro
​
The Add Custom Macro button allows customers to create their own property macros manually. These custom macros can be used to insert personalized or property-specific content that isn't pulled from a PMS.

When a custom macro is added:

  • It is categorized as "Unsynced"

  • It can be edited or updated at any time

  • It is available for use across messaging templates, Home Guides, and more
    ​

This option is ideal for customers who need flexibility beyond standard PMS fields.


Unit Macros Integration

Viewing Macros

  • Customers can view all macros associated with a unit by navigating to the Units page and clicking Details.
    ​


Editing Macros

  • Customers can update macro values by clicking Edit on the corresponding unit from the Units page.
    ​

Macros are linked to individual units. To learn more about managing units, click here to view the Units Management article.


Additional Implementation Details

  • Remove the “Add Property Macro” dropdown from the API page

  • Enforce unique macros – duplicates are not allowed

  • Restrict use of reserved macro names such as:

    • [DoorCode], [PropertyId], [CheckIn], etc.

  • Make Property ID a required and unique field for all units

Did this answer your question?