Integrations, Connectors, and Event Delivery

Rivolq supports several integration patterns. Pick the one that matches what the outside system needs to do.

Integration paths

• Chat connectors send operational events to Slack, Microsoft Teams, or Discord channels.
• Native integrations connect supported providers through the Integrations marketplace.
• Scheduled exports send recurring data snapshots to configured destinations. See Scheduled exports.
• OAuth apps and developer APIs let customer-owned or partner applications act through scoped access.
• Rivolq Connect exposes scoped Rivolq data to MCP-compatible AI clients.

Chat connectors

Open Connectors from the customer workspace. The page is available to admins with API access. Each connector has a name, destination kind, incoming webhook URL, selected event list, enabled state, and last-delivery details. Destinations are Slack, Microsoft Teams, and Discord.

Event families include work_order.created, work_order.completed, incident.opened, incident.resolved, maintenance_request.submitted, and asset.failure. Select only the events the destination should receive; too many turn a useful channel into noise.

Native integrations marketplace

Open Integrations when your workspace needs a provider-backed connection. The marketplace shows available providers, whether each has a native connector, and the org's current connection state. Inbound callbacks are record-only status signals; a provider cannot change work orders outside the normal Rivolq workflow.

OAuth apps, APIs, and Rivolq Connect

Use OAuth apps when another application acts on behalf of a Rivolq user. Use service accounts and API keys for internal automation.

Rivolq Connect speaks MCP over authenticated HTTPS: ChatGPT and OpenAI Apps use https://connect.rivolq.com/mcp/, while Claude, Cursor, and some generic clients use https://connect.rivolq.com/sse. It is not a general API gateway; role and tenant checks stay in the main app. Work-order writes are staged as proposals first. See Rivolq Connect and MCP apps.

Safe practices

Treat webhook URLs, API keys, OAuth secrets, and integration credentials like secrets. Store them in your secrets manager, rotate them if exposed, and revoke apps or connectors that are no longer used. Avoid sending every event to a busy channel, treating chat delivery as the source of truth (Rivolq remains the system of record), and confusing Rivolq Connect with the in-product assistant.