Help

Integrations allow you to connect TowerOps with third-party services to enrich your monitoring data, sync subscriber information, and streamline your workflow. Configure integrations from Organization Settings → Related pages → Integrations .

The settings page groups providers by what they contribute; the groups below come from the same catalog the settings page renders, so this list cannot fall behind it. Each configured integration has an enable toggle, a Configure panel, and, for providers that pull data on a schedule, a Sync now button.

• Billing & Subscriber Management: Gaiia, Sonar, Splynx, VISP (only one can be enabled at a time)
• Quality of Experience: Preseem
• Incident Management: PagerDuty
• Ticketing & PSA: ConnectWise, Halo PSA, Jira (only one can be enabled at a time)
• Communications: Quo
• Subscriber Events: MikroTik
• Infrastructure & IPAM: NetBox, UISP, cnMaestro
• Inbound Events: Inbound Alerts

Quo

Quo (formerly OpenPhone) captures incoming calls, texts and voicemail without polling. In Organization Settings → Integrations → Communications, configure Quo with a workspace API key and save. TowerOps provisions the signed webhook automatically; no signing key needs to be copied.

Use Test Connection to check the key, then Send test event to exercise delivery. The Communications page lists incoming events and links unambiguous phone matches to billing subscribers. Numbers with no match stay unlinked.

Subscribed events: message.received , call.completed , call.voicemail.completed . The read-only listener URL is shown in the Quo configuration panel.

Disabling Quo rejects further deliveries and attempts to delete the remote subscription. A deletion warning means Quo may still retry; re-enabling adopts the subscription instead of creating another. Events follow your organization's data retention. Recording URLs are not mirrored and may expire.

Preseem

Preseem is a Quality of Experience (QoE) monitoring platform designed for WISPs and broadband providers. The Preseem integration syncs subscriber and access point QoE data into TowerOps, giving you a unified view of network health alongside device monitoring.

What It Syncs

• Access point QoE, capacity, and RF scores
• Subscriber metrics: latency, jitter, packet loss, and throughput
• Score history used to build baselines and insights

Configuration

Gaiia

Gaiia is a billing and subscriber management platform. The Gaiia integration syncs subscriber data, service plans, and entity mappings into TowerOps, enabling you to correlate network issues with specific customers and services.

What It Syncs

• Subscribers and their contact information
• Network sites and inventory items
• Billing subscriptions and service status
• Links between Gaiia subscriber accounts and TowerOps devices, for impact analysis

Configuration

PagerDuty

PagerDuty is an incident management and on-call alerting platform. The PagerDuty integration provides 2-way alert sync, when a device goes down in TowerOps, a PagerDuty incident is automatically triggered. Acknowledging or resolving the alert in TowerOps updates the PagerDuty incident as well.

How It Works

• Device or site goes down → PagerDuty incident triggered (critical severity)
• Alert acknowledged in TowerOps → PagerDuty incident acknowledged
• Device recovers / alert resolved → PagerDuty incident resolved
• Incident acknowledged or resolved in PagerDuty → the TowerOps alert is updated through PagerDuty's V3 webhook

Outbound events need only the Events API v2 integration key. To receive PagerDuty's own acknowledgements and resolutions back, add a webhook subscription in PagerDuty pointing at /api/v1/webhooks/pagerduty/<organization id> and set the integration's webhook secret credential (through the API or GraphQL) to the signing secret PagerDuty issues for it.

Configuration

Sonar

Sonar is a cloud-based ISP billing and operations platform. The Sonar integration reads your account totals so TowerOps can report subscriber count and monthly recurring revenue alongside your network health.

What It Syncs

• Subscribers and their monthly recurring revenue

Configuration

Navigate to Organization Settings → Related pages → Integrations and enter your Sonar instance URL and API token. Save the integration and set a sync interval; use Test Connection first to verify the credentials.

Splynx

Splynx is an ISP billing, CRM, and network management platform. The Splynx integration syncs the subscriber registry and internet services so TowerOps can attribute each subscriber to the devices serving them, report outage impact in subscribers and monthly recurring revenue, and, when enabled, write outage notes back to the subscriber record.

What It Syncs

• Subscribers
• Internet services and their monthly recurring revenue
• Device-to-subscriber links derived from service IPs and MACs against ARP and wireless-client data
• Optional write-back of outage notes to subscriber records

Configuration

Navigate to Organization Settings → Related pages → Integrations and enter your Splynx instance URL, API key, and API secret. Save the integration and set a sync interval; use Test Connection first to verify the credentials.

VISP

VISP is a billing and subscriber management platform for WISPs. The VISP integration reads your subscriber totals so TowerOps can report subscriber count and monthly recurring revenue.

What It Syncs

• Subscribers and their monthly recurring revenue

Configuration

Navigate to Organization Settings → Related pages → Integrations and enter your VISP API key. Save the integration and set a sync interval; use Test Connection first to verify the key.

NetBox

NetBox is a network source of truth for IPAM, DCIM, and infrastructure documentation. The NetBox integration imports your sites and devices so TowerOps can monitor the inventory you already maintain there.

What It Syncs

• Sites, matched onto your existing TowerOps sites
• Devices, matched onto your existing TowerOps devices

Configuration

Navigate to Organization Settings → Related pages → Integrations and enter your NetBox URL and API token. Choose whether sites, devices, or both are imported, set a sync interval, and use Test Connection to verify the token.

UISP

UISP is Ubiquiti's network management platform. The UISP integration imports your sites and devices, and enriches the imported devices with GPS coordinates and configuration snapshots.

What It Syncs

• Sites and devices
• Device GPS coordinates
• Device configuration snapshots

Configuration

Navigate to Organization Settings → Related pages → Integrations and enter your UISP URL, the host is enough because /nms/api/v2.1 is added for you, plus an API key. Save the integration and set a sync interval; use Test Connection to verify the key.

cnMaestro

cnMaestro is Cambium Networks' cloud management platform. The cnMaestro integration authenticates with OAuth 2.0 and imports your networks and devices.

What It Syncs

• Networks, imported as sites
• Devices: a new or unplaced device starts at its network's site, and a device that already has a site keeps it

Configuration

Navigate to Organization Settings → Related pages → Integrations and enter your cnMaestro URL with the OAuth client ID and secret. Save the integration and set a sync interval; use Test Connection to verify the credentials.

Ticketing & PSA

ConnectWise Manage, Halo PSA and Jira each open a ticket in your PSA or issue tracker when an alert storm starts and close it when the storm clears, so the alert-to-ticket handoff never depends on somebody watching the dashboard. Only one ticketing integration can be enabled at a time: exactly one system owns the ticket ledger, the same way billing providers are exclusive. Configure it under Organization Settings → Integrations → Ticketing & PSA, a Beta category shown once your organization has the ticket handoff feature enabled; enabling a provider's card makes that provider the one that owns the tickets.

Subscriber Events

The MikroTik card under Organization Settings → Integrations → Subscriber Events, which needs a membership that can manage integrations to open, hands you a webhook token and ready-made RouterOS scripts for DHCP lease and PPP on-up/on-down events. Once the router posts them, every lease and session lands in TowerOps, the evidence behind the subscriber trace page, which resolves a subscriber to a port, MAC address and IP.

General Integration Features