# Integrations

RivetMSP connects to the tools an MSP already runs. Configure them under **Administration > Settings**, in the integrations area.

## Remote monitoring and management (RMM)

An RMM integration brings devices and alerts into RivetMSP. Supported providers:

- **Tactical RMM**
- **Level.io**
- **Action1** (OAuth2, for patch management)
- **Sophos Central** (OAuth2, for firewall inventory and alerts)

RMM agents are matched to your RivetMSP assets automatically, first by linked ID, then by serial number, MAC address and hostname. Alerts sync on every cron cycle and can **create tickets automatically**. Ticket automation rules can also react to new alerts and to devices going offline or coming back, and can run an RMM script or acknowledge an alert. See [Ticket automation rules](/docs/msp/ticket-automation).

Switch the RMM module on from its own settings screen.

## UniFi

Connect a local or cloud UniFi controller and its devices, networks and access details are mapped into assets, credentials and networks. The sync runs from its own script and **needs its own cron entry**; the main cron dispatcher does not start it. See [Cron Manager](/docs/msp/cron-manager).

## Comet Backup

Comet Backup status can be shown against your clients.

## Email

- **Inbound.** A mailbox poller reads IMAP mailboxes and turns messages into tickets or replies. Microsoft 365 and Google Workspace mailboxes are supported with OAuth2. Mail from unknown senders can be held for review.
- **Outbound.** Notifications and replies are delivered through a mail queue, by SMTP or by OAuth token. The queue is drained by cron, so keep cron enabled.

## Accounting and payments

- **QuickBooks Online.** A one-way push from RivetMSP to QuickBooks: customers, items, invoices and payments. It is never read back. A queue retries failures with backoff and respects the order QuickBooks needs (customer before invoice, invoice before payment).
- **Stripe.** Clients can pay invoices from an emailed link and save cards in the client portal, and staff can record payments. The payment layer is built so further gateways can be added later.

## Sign-in

- **Microsoft Entra ID** can be offered to clients on the client portal. It is sign-in only and does not sync your directory.

## Webhooks and the API

- **Webhooks** announce events to other systems. Configure them under **Administration > Webhooks**. A guided four-step setup covers 24 ready-made platforms (n8n, Node-RED, Activepieces, Windmill, Huginn, Zapier, Make, Pipedream, IFTTT, Slack, Teams, Discord, Mattermost, Rocket.Chat, Matrix, Telegram, ntfy, Gotify, Apprise, Home Assistant, and generic JSON, form or custom template), with 13 payload formats, bearer, basic, custom-header or signed authentication, retries, **Send test** and **Preview**.
- Pick from **113 events in 14 groups** in a searchable list, with group wildcards such as `ticket.*`. 96 are emitted today and 17 are planned.
- Signed requests carry a timestamp so receivers can reject replays; the Guides hub has verification snippets in five languages.
- **Event rules** turn the same events into actions. See [Ticket automation rules](/docs/msp/ticket-automation).
- The **REST API** lets you build your own integrations and powers the mobile app. See the [REST API guide](/docs/msp/api) and the [API reference](/api/msp).

## Real-time updates and push notifications

Live ticket updates, live ticket chat and in-app notifications use server-sent events backed by Redis. Push notifications to phones use Firebase Cloud Messaging.
