Plugins and Integrations
Where: Settings → Plugins (/plugins)
The Plugin Shop is one place to browse, install, and configure both integrations (external systems) and payment providers. It has a Discover tab and an Installed tab, plus a configuration screen for each item.
Plugin shop discover tab
Discover offers three view layouts (grid, category list, and featured) and a search box. Items are grouped by category — Accounting, Booking, POS, CRM, E-commerce, Payments, and Analytics — and each card shows a status pill:
| Pill | Meaning |
|---|---|
| Connected | Active and fully configured. |
| Needs authorization | Active but missing credentials or a sign-in step. |
| Error | Active but not working. |
| Off | Not enabled. |
To install and configure any plugin:
- Open its card to reach the configuration screen.
- Turn on the master switch at the top.
- Fill in the required fields (keys, IDs, options).
- If the plugin has an Authorize or Provision schema action, run it after saving.
- Save. The status pill updates to reflect the new state.
Integrations
| Integration | Category | What it does |
|---|---|---|
| Xero Accounting | Accounting | Pushes invoices, credit notes, payments, and contacts to Xero. Use Authorize to sign in; set the Xero organisation (tenant), account codes, tracking category, and webhook key. Re-authorize if Xero prompts about permissions. |
| Zoho Books | Accounting | Sends bookings to Zoho via webhooks; choose the booking states that trigger a send. |
| Poster | POS | Connects the Poster POS. Use Authorize, then set the account and application details. |
| Cloudbeds | Booking | Imports reservations from Cloudbeds; set the API key, resort, rate sheet, and defaults. |
| SUAPI | Booking | The OTA/channel-manager bridge behind OTA mapping. Set the licence and keys; the optional card-view keys enable secure card viewing (see the note below). |
| WooCommerce | E-commerce | Syncs with a WooCommerce store using its API keys. |
| HighLevel | CRM | Pushes each guest's stays to GoHighLevel. Set the access token and location ID, then use Provision schema to set up the data model. You can also back-fill a single guest's stays from their customer page. |
Tip (Xero): Set the sales account code (your Xero revenue account, e.g.
200), the payment account code (the bank account payments post to), and the refund account code. Without a sales account code, Xero rejects new invoices with "Account code or ID must be specified." Xero also rejects any currency your organisation hasn't added under its own Settings → Currencies. If Xero prompts about permissions, use Authorize again to refresh access.
Note (HighLevel): Only regular guest customers are pushed — system, API, agency, and staff accounts are skipped. A guest's stays sync when a booking is reserved, confirmed, cancelled, resolved, or deleted. Run Provision schema once (creates the Stays data model in GoHighLevel) before the first sync.
Note (SUAPI card viewing): For bookings that arrive through the channel manager with a stored credit card, staff with the SU API permission can open the card through Suissu's secured vault page — a short-lived link generated per request and tied to your connection. The card number itself is never stored in, or displayed by, Gurita, and the booking must belong to one of your properties. To enable it, enter the Card API name and Card API key you receive from Suissu in the SUAPI configuration.
Payment providers
The Payments category holds the online payment gateways — Stripe, PayPal, FlyWire, FastSpring, AirWallex, DOKU, Wise, Maya, and PesoPay. Enable and configure the one(s) you use here; they then appear as options when taking payments. For how payments are recorded and reconciled, see Finance.
Note: When the WhatsApp module is active, a WhatsApp card appears here for the connection — the account credentials Gurita sends messages through. The actual per-event messages are still composed on the Notification settings page. Inbound webhooks (Xero, Stripe, FlyWire, Zoho) are verified automatically once you enter each provider's signing key in its config screen.
Who can access this: Requires Administrator access for integrations; payment providers additionally require the Payment providers permission.