Integrations
Core Platformintegration_get_configIntegrationsRetrieves legacy facility-level integration settings that are NOT managed through the partner config system.
For partner-based integrations (GymMaster, Stripe, Ubiquiti UniFi, Myzone, Back2Base, W4G Security, Lead Forwarding/CRM, etc.), use the integration_list_partner_configs tool instead — it is the primary and authoritative source for all external partner integrations.
This tool covers only the remaining legacy settings stored directly on the facility record:
- Alarm Relay Settings: alarm type, provider, and relay model (eaAlarmType, eaAlarmProvider, eaRelayModel)
- Marketing & Directory Services: Synup location ID, Google My Business place ID, Yext entity ID
- Communication Channels: LINE Chat, WhatsApp integration
BATCH OPERATIONS SUPPORTED:
- Single facility: Provide facilityId
- Multiple facilities: Provide facilityIds array
When to use this tool:
- Checking alarm relay/type configuration (not the alarm ID itself — that's in the Back2Base partner config)
- Verifying directory service listings (Synup, GMB, Yext)
- Reviewing communication channel integrations (LINE, WhatsApp)
When to use integration_list_partner_configs instead:
- Checking ANY partner-based integration (GymMaster, Stripe, UniFi, Myzone, Back2Base, W4G, CRM, etc.)
- Auditing which integrations are enabled/disabled
- Viewing integration credentials or configuration fields
Parameters
| Name | Type | Description |
|---|---|---|
facilityId | string | Single facility ID. Omit this if using facilityIds for batch operations. |
facilityIds | array | Array of facility IDs for batch operations across multiple facilities. |
integration_list_partner_configsIntegrationsRetrieves external integration (partner) configurations for one or multiple facilities from the modern partner config system.
This is the primary tool for checking external integrations. It covers ALL partner-based integrations including GymMaster, Stripe, Ubiquiti UniFi, Myzone, Back2Base, W4G Security, Lead Forwarding (CRM), and any other partners configured in the system.
BATCH OPERATIONS SUPPORTED:
- Single facility: Provide facilityId
- Multiple facilities: Provide facilityIds array
FILTERING:
- By partner ID: Provide partnerId to get a single integration
- By partner name: Provide partnerName for case-insensitive partial match (e.g. "gym" matches "GymMaster")
- Enabled only: Set enabledOnly to true to skip disabled integrations
Returns per-partner configuration including:
- Partner metadata: name, code, category, field definitions
- Enabled/disabled status and brand-level overrides (alwaysOnForAllFacilities)
- Configuration values with secret fields masked
- Linking identifiers if configured
For legacy facility settings not managed through the partner system (alarm relay settings, directory services like Synup/GMB/Yext, communication channels like LINE/WhatsApp), use the integration_get_config tool instead.
Parameters
| Name | Type | Description |
|---|---|---|
facilityId | string | Single facility ID. Omit if using facilityIds for batch operations. |
facilityIds | array | Array of facility IDs for batch operations across multiple facilities. |
partnerId | string | Filter to a specific partner by its ID (UUID). |
partnerName | string | Filter by partner name (case-insensitive partial match, e.g. "gym" matches "GymMaster"). |
enabledOnly | boolean | If true, only return integrations that are enabled. Defaults to false. |
includeSecrets | boolean | If true, return actual secret values (API keys, passwords) instead of masking them. Use only when the actual credential values are needed (e.g. troubleshooting connectivity). Defaults to false. |