Connector library

Implemented source Scheduling, Booking & Practice Systems

Vagaro connector.

Read selected Vagaro v3 business vendor pages and exact vendor references through two named actions with managed issued access tokens.

Download connector See all connectors

Connector download

Download Vagaro

Versioned ZIP for your CXFabric tenant.

Sign in to download Using connectors

Use this connector in a flow

  1. Register the ZIP in your tenant, or add a new version if the connector is already installed.
  2. Create or select a credential if the action requires one.
  3. In a Draft flow, add an available action, choose its version, connect it, and map inputs.
  4. Test the step and flow; review output and failures before activation.

See readme.md in the ZIP for settings and limitations.

Version
v0.2.0.0 Choose version
Release
2026-10-04
Package
Implemented source
Schema credentials
Bearer token
Connection settings
Account Region
Package size
9 KB
SHA-256
ec2d0104862c4716f9ca3019610ec667b8ab29675c98b086722c0b3fd814758e

Version history

What's new

  1. v0.2.0.0Latest · 2026-10-04 · Implemented source

    Replaces the generic HTTP scaffold with two explicit v3 vendor reference reads: one business vendor page and one exact vendor lookup.

    Full release notesView download
  2. v0.1.1.0Earlier · 2026-10-02 · Starter scaffold

    Historical configurable HTTP scaffold; not a vendor-specific implementation.

    View download

Included in this version

Included actions

Implemented in v0.2.0.0. Use a separate flow trigger; no webhook trigger is included.

List business vendor references

Read one selected ID/name page in business and access-token scope; no completeness or automatic paging claim.

Get vendor reference

Read selected exact vendor ID/name metadata and check the returned identity.

Vendor API

API and access

Vendor API documentation Vendor website
Implementation considerations
  • Store only the approved issued read-access token in a managed token credential. Requests use the native accessToken header without Authorization or a Bearer prefix; token lifecycle remains external.
  • Account Region is the exact Vagaro account subdomain. Requests use only api.vagaro.com with the fixed v3 paths. Raw opaque IDs preserve case and padding and are encoded once.
  • One caller-selected page is returned, with native page size 1–100 and a local page number cap of 1000000. There is no automatic paging, URL following or full-business completeness claim. The page businessId is requested context, not echoed identity.
  • Contacts, merchant links, customers, employees, appointments and writes are omitted. The single-brand schema/example disagree, so brand reads are excluded.
  • Native status 200 and responseCode 1000 envelopes are checked. HTTP 404 and API errors remain failures; empty pages are scoped reads rather than global absence. Reference data does not establish inventory or operational availability.
  • Strict JSON/media/UTF-8, a 1 MiB response cap, normal TLS trust and shared 1–8 second budget fail without redirects, proxies or replay. Hosted import, dependencies and live region/token/read-access/ID/paging behavior remain untested.
  • Two packaged v3 vendor reference reads use approved issued tokens with read access in the native accessToken header. Current native schema and account-region guide establish the contract; live region/token/paging and hosted dependency behavior need validation.

Support

Need help with Vagaro?

Tell us what you need to connect or change.

Contact us Back to connectors