Knowledge BaseKnowledge Base

Setting Up the Breezeway Connector

Connect Breezeway property operations into Wazzi for cleaning, maintenance, inspections, and task management via MCP.

April 25, 2026
4 min read

Path: Connectors → Breezeway → Configuration

What this connector does

The Breezeway connector exposes property operations data — cleaning, maintenance, inspections, tasks, reservations, and property metadata — to your team's AI assistants via MCP. Vacation rental operators use it to ask "what's the housekeeping status of unit 14?" or "list open maintenance tasks at the Aspen properties" without leaving their AI chat.

It also feeds Wazzi's Data Sources for any Centers products that consume Breezeway data (most commonly Operations Center).

Wazzi authenticates via OAuth2 client_credentials — your Breezeway client ID and client secret are exchanged for a 24-hour JWT bearer token, which Wazzi caches and refreshes automatically.

Before you start — getting your Breezeway credentials

You'll need a Breezeway account with admin permissions and access to the API settings.

  1. Sign in to Breezeway at app.breezeway.io.
  2. Open Settings → Integrations → API Access.
  3. If you don't see API Access, contact Breezeway support — they enable it on a per-account basis.
  4. Generate or copy your Client ID and Client Secret. Treat the secret like a password.

Reference: Breezeway's API docs are at api.breezeway.io/public/docs. Their auth flow uses the standard OAuth2 client_credentials grant.

Heads up — auth rate limits. Breezeway's auth endpoint is rate-limited to 1 request per minute. Wazzi caches tokens (24-hour TTL) to avoid hammering this endpoint, but if you rotate credentials and immediately Test Connection, give it 60 seconds before retrying.

What this connector unlocks for your team

Once configured, members with the right MCP permissions can ask Claude / ChatGPT / Cursor things like:

  • "List housekeeping tasks scheduled for tomorrow at the Tahoe properties."
  • "What's the cleaning status of unit 14?"
  • "Show open maintenance tasks across the portfolio."
  • "Find inspection reports flagged as urgent this week."

The exact set of available actions depends on which MCP toggles you've flipped on for the user's group — see Managing Permissions.

Steps — configuring Breezeway in Wazzi

1. From the Connectors catalog, click Configure on the Breezeway tile.

You'll land on Breezeway's Configuration tab:

Breezeway connector Configuration tab

2. Fill in the fields.

  • Client ID — from Breezeway → Settings → Integrations → API Access.
  • Client Secret — same page. Encrypted at rest.

3. Click Test Connection.

Wazzi exchanges the credentials for an access token, then verifies the token works against Breezeway's API. Success means you're connected.

4. Click Save Configuration.

Breezeway moves to the Active section and the dot turns green.

Troubleshooting

  • "Test Connection failed: invalid_client." Client ID or secret is wrong. Re-copy from Breezeway. Watch out for trailing whitespace.
  • "Test Connection failed: 429 Too Many Requests." You hit Breezeway's auth rate limit (1 req/min). Wait 60 seconds and retry.
  • Test passes but tool calls return 401 mid-session. Breezeway's tokens are 24h. Wazzi handles refresh automatically — if you see persistent 401s, it usually means the credentials were rotated externally; update them in Wazzi.
  • "Test Connection failed: 403 Forbidden." The app's API permissions are too narrow. Contact Breezeway support to grant additional scopes.
  • The connector worked, then Breezeway deleted properties don't disappear. Wazzi reads on-demand, so deletes propagate immediately. If they don't, the AI may have cached older tool responses — start a fresh chat.

Best practices

  • Use a dedicated Breezeway integration user. Easier to revoke without affecting humans on the team.
  • Document the credential location. Save a note about who issued the credentials and when, so rotation is straightforward.
  • Set a quarterly rotation reminder. Breezeway credentials don't expire automatically.
  • Wire Breezeway into Data Sources. If you're using Wazzi's Operations Center, Breezeway is a natural data source for cleaning and maintenance task tables. See Configuring Data Sources.

Frequently asked questions

Does Wazzi store the Client Secret in plaintext?
No. Encrypted at rest, decrypted at request time only.

How often does Wazzi refresh the access token?
On expiry. Tokens last 24 hours; Wazzi caches them in a two-tier cache (in-memory + DB) so all instances converge on a single token, refreshed at most once per day.

Will this connector write to Breezeway?
The connector includes selected write endpoints for tasks (create, update). Read endpoints cover the full property and reservation surface. See the connector's Permissions page for the full list.

What if my Breezeway plan doesn't include API access?
API access is included on Breezeway's higher tiers — contact Breezeway sales to confirm.

What's next

Was this article helpful?