| sidebar_custom_props |
|
|---|
Integrations connect QuilrAI to the systems that provide identity, device, SaaS, cloud, and AI signals. They are the setup and lifecycle surface for connectors and connector instances.
Use Integrations when you need to:
- Connect QuilrAI to an external system.
- Review existing connected integrations.
- Browse available integrations.
- Configure or update an integration instance.
- Follow setup guidance for supported connectors.
- Manage integration-specific OAuth or configuration flows.
- Connected integrations view.
- Available integrations catalog.
- Search and filter connectors.
- Configure new instances.
- Edit existing instances when permitted.
- Connector-specific setup documentation, including required scopes, permissions, and configuration.
- Separate advanced routes for OAuth, token flow, MCP clients, MCP servers, and tool policies where enabled.
Connectors are organized into the following categories:
- Data Forwarding: Webhook, Syslog, Syslog Audit, Email.
- Identity Providers: Microsoft Entra ID, Google Workspace, Okta, Ping Identity.
- Authentication: SAML.
- Microsoft Ecosystem: Microsoft Purview, Microsoft Calendar.
- Google Ecosystem: Google Calendar, Google Drive.
- Mobile Device Management (MDM): Microsoft Intune, Jamf Pro.
- Communication & Collaboration: Microsoft Teams, Slack, Zoom ChatBot.
- Asset Discovery: AWS Cloud, Azure Cloud, ChatGPT, vLLM, Ollama.
- Open Integrations.
- Review Connected integrations or browse Available integrations.
- Search or filter by connector category.
- Select a connector.
- Follow configuration guidance and complete required scopes or credentials.
- Return to Connected integrations to monitor or update the instance.
Some integration routes are specialized operational areas and may not be visible to every customer:
- OAuth integration configuration.
- Token flow configuration.
- MCP clients and MCP servers.
- Tool policies for MCP or AI tool governance.
- OAuth and token-flow routes that support connector authorization and callback workflows.
Integrations require Integration permissions. Editing existing integrations requires update access. Some MCP-related integration routes require MCP Gateway permissions.