Integration Overview: What Connects to SecureAI

SecureAI connects to external platforms so your team can pull in data, push results to other tools, and keep SecureAI part of your existing workflows. This article is a map of every integration available today, what each one does, and how to get started.

How Integrations Work in SecureAI

SecureAI runs on OpenWebUI, which supports integrations through three mechanisms:

1. Built-in connectors -- Pre-configured integrations that an admin enables in the SecureAI admin panel. These require credentials and a few settings but no custom code.
2. Pipelines -- Server-side automation scripts that process data between SecureAI and external systems. These handle tasks like ingesting support tickets or syncing documents.
3. API access -- SecureAI exposes a REST API that external tools can call to send queries, retrieve conversation history, or trigger actions programmatically.

Most users interact with integrations passively -- the data just appears in SecureAI because an admin configured the connection. Admins and developers are the ones who set up and maintain integrations.

Available Integrations

HubSpot

What it does: Syncs customer and account data from HubSpot CRM into SecureAI so that conversations can reference customer context -- account type, recent interactions, open tickets, and purchase history.

Use cases:

• Parts specialists can ask SecureAI about a customer's order history without leaving the chat.
• Service advisors can pull up account details (fleet size, preferred brands, pricing tier) during a conversation.
• Support teams can reference open HubSpot tickets when helping a customer with a parts question.

How to connect:

1. In the SecureAI admin panel, go to Settings > Integrations > HubSpot.
2. Enter your HubSpot API key (generated in HubSpot under Settings > Integrations > API Key).
3. Select which HubSpot objects to sync: Contacts, Companies, Deals, Tickets.
4. Set the sync interval (default: every 15 minutes).
5. Save and test the connection.

What users see: When HubSpot is connected, users can ask questions like "What is the account status for [customer name]?" and SecureAI will include HubSpot data in its response.

Limitations: HubSpot integration is read-only. SecureAI cannot create or update HubSpot records. Data freshness depends on the sync interval.

Google Drive

What it does: Connects SecureAI to your organization's Google Drive so that documents, spreadsheets, and PDFs stored in Drive can be referenced in conversations. This is especially useful for parts catalogs, spec sheets, and internal documentation that your team already maintains in Drive.

Use cases:

• Upload a parts catalog PDF to a shared Drive folder and let SecureAI reference it during parts lookups.
• Store vehicle spec sheets in Drive and ask SecureAI to pull fitment data from them.
• Keep internal SOPs in Drive and let SecureAI answer process questions using the latest version.

How to connect:

1. In the SecureAI admin panel, go to Settings > Integrations > Google Drive.
2. Authenticate with a Google Workspace account that has access to the target Drive folders.
3. Select which folders SecureAI should index. Only files in selected folders are accessible.
4. Choose file types to include (PDF, DOCX, XLSX, Google Docs, Google Sheets).
5. Set the re-index interval (default: every hour).

What users see: Users can reference Drive documents in conversations: "Check the 2026 Dorman catalog for part number 523-1234" and SecureAI will search the indexed Drive content.

Limitations: SecureAI can read Drive files but cannot modify them. Large files (over 50 MB) may be partially indexed. Google Sheets formulas are not evaluated -- only cell values are indexed.

Slack

What it does: Enables two-way communication between SecureAI and Slack channels. SecureAI can post summaries, alerts, or answers to Slack, and Slack users can query SecureAI directly from a channel.

Use cases:

• Set up a #parts-lookup Slack channel where team members can ask SecureAI questions without opening the web interface.
• Have SecureAI post daily summaries of common parts questions to a team channel.
• Receive notifications in Slack when SecureAI identifies a trending parts question or knowledge gap.

How to connect:

1. In the SecureAI admin panel, go to Settings > Integrations > Slack.
2. Click Install Slack App to authorize the SecureAI Slack bot in your workspace.
3. Select which channels the bot can read and post to.
4. Configure bot behavior: response mode (threaded replies vs. channel messages), mention triggers, and quiet hours.
5. Save and test by mentioning @SecureAI in a connected channel.

What users see: In connected Slack channels, users mention @SecureAI followed by a question. SecureAI responds in a thread with the answer. Users can also DM the bot for private queries.

Limitations: Slack conversations are separate from web conversations -- context does not carry over between the two. File uploads through Slack are limited to text and PDF. Image analysis is not available through the Slack integration.

Microsoft 365

What it does: Integrates with Microsoft 365 services -- SharePoint, OneDrive, Outlook, and Teams -- to bring your organization's documents and communications into SecureAI's context.

Use cases:

• Index SharePoint document libraries containing parts catalogs, technical bulletins, and training materials.
• Connect OneDrive folders for individual users who store reference documents there.
• Enable Teams integration so users can query SecureAI from a Teams channel (similar to the Slack integration).
• Reference Outlook email threads when discussing customer issues in SecureAI.

How to connect:

1. In the SecureAI admin panel, go to Settings > Integrations > Microsoft 365.
2. Sign in with a Microsoft 365 admin account and grant the required permissions (read access to selected services).
3. Select which services to enable: SharePoint, OneDrive, Teams, Outlook.
4. For SharePoint/OneDrive: select the sites or folders to index.
5. For Teams: select which channels the SecureAI bot can access.
6. Set sync and indexing intervals.
7. Save and test the connection.

What users see: Users can reference Microsoft 365 content in conversations. If Teams is connected, users can query SecureAI from a Teams channel using @SecureAI.

Limitations: Microsoft 365 integration requires a Microsoft 365 Business or Enterprise plan. SharePoint site-level permissions are respected -- SecureAI only indexes content the authenticated account can access. Outlook integration is read-only and limited to the last 90 days of messages.

Custom APIs

What it does: SecureAI exposes a REST API and supports custom pipeline scripts, allowing your development team to build integrations with any system not covered by the built-in connectors.

Use cases:

• Connect a proprietary parts database or inventory management system so SecureAI can check real-time stock levels.
• Build a pipeline that ingests repair orders from your shop management system and makes them searchable in SecureAI.
• Create a webhook that triggers SecureAI analysis when a new support ticket is filed.
• Integrate with distributor APIs (WHI Solutions, PartsTech, OEConnection) for live pricing and availability lookups.

API access:

1. In the SecureAI admin panel, go to Settings > API Keys.
2. Generate an API key with the appropriate scope (read, write, or admin).
3. Use the API key in the Authorization: Bearer <token> header for all API requests.

Key API endpoints:

• POST /api/chat -- Send a message and receive a response.
• GET /api/chats -- Retrieve conversation history.
• POST /api/documents -- Upload a document for indexing.
• GET /api/models -- List available models.

Custom pipelines: For more complex integrations, create a pipeline script in the pipelines/ directory. Pipelines can:

• Pull data from external sources on a schedule.
• Transform and load data into SecureAI's document index.
• React to events (new conversations, user uploads, etc.) and trigger external actions.

See the existing pipelines (pipelines/ticket-ingestion/, pipelines/usage-analysis/) for examples.

Limitations: Custom integrations require development resources. API rate limits apply (see the "API rate limiting and quotas" article). Pipeline scripts run server-side and must be deployed with the SecureAI instance.

Integration Comparison

Getting Started

1. Decide what you need: Review the integration descriptions above and identify which platforms your team uses daily.
2. Check with your admin: Built-in integrations (HubSpot, Google Drive, Slack, Microsoft 365) are configured in the admin panel. Ask your SecureAI admin to enable the ones your team needs.
3. Start with one: Enable one integration at a time. Test it with real workflows before adding more.
4. For custom needs: If your team needs an integration not listed here, talk to your development team about using the API or building a custom pipeline.

Security and Data Access

All integrations respect SecureAI's security model:

• Credential storage: Integration credentials are encrypted at rest and never exposed to end users.
• Access control: Admins control which integrations are active and which data sources are indexed.
• Audit logging: All integration activity (syncs, API calls, document indexing) is recorded in the audit log.
• Data retention: Integrated data follows the same retention policies as other SecureAI content. See "Configuring Data Retention Policies" for details.

Related Topics

• Shop management system integration (Mitchell, CCC, Audatex)
• Using SecureAI with parts ordering platforms
• Generating and managing API keys
• API rate limiting and quotas
• Configuring data retention policies