Skip to main content

​
What are Connectors?

Connectors are software components that sync and index data from external applications into PipesHub. They enable your chatbot and agents to search through your organization’s knowledge base. Use Connectors when you want to query or search data. The indexed data becomes searchable knowledge for your AI assistants. Key characteristics:
  • One-way data sync - Import data into PipesHub for indexing
  • Knowledge retrieval - Make data searchable for AI assistants
  • Periodic syncing - Data is synced on a schedule, not in real-time
Important: When authenticating a connector, use the same email address as your PipesHub account. Using a different email will cause permission issues on the PipesHub platform.
When you want to use both Connector and Toolset: In the Agent Builder add nodes from Knowledge (Apps, Collections) for document search and context retrieval, and add nodes from Tools for performing actions. Connect both to the Agent node so the agent can search context and take action in the same conversation.

​
Available Connectors

Our platform supports a wide range of connectors organized by ecosystem to help you integrate with your favorite tools and services.

​
Google Workspace

​
Microsoft Ecosystem

​
Atlassian

​
Communication & Support

​
CRM & Sales

​
Web and feeds

​
Local & network storage

​
Cloud Storage & Infrastructure

​
Development & Project Management

​
Knowledge Management

​
Database & Analytics

​
Security & Compliance

All connectors are built with enterprise-grade security in mind, supporting OAuth 2.0 or token-based authentication (depending on the source), data encryption, and compliance with major industry standards including SOC 2, GDPR, and HIPAA where applicable.

​
Frequently Asked Questions

Example: Use a Gmail Connector to index and search your email history. Use a Gmail Toolset to send new emails through an agent.
Connector — Use when you need document context search: connectors sync and index your documents, emails, and pages so your assistant can find and use that context, and they do not perform actions.Toolset — When you need actions: create or update content, send messages, or run analytical queries (e.g. JQL, CQL, reports).Quick takeaway: Search & context → Connector. Actions → Toolset.
The callback URL is displayed in PipesHub when configuring a connector:
  1. Go to Settings > Connectors
  2. Click “Configure” on the connector you want to set up
  3. Copy the Redirect URI shown in the dialog
  4. Add it to your OAuth app’s allowed redirect URIs in the service’s developer console
The callback URL must match exactly between PipesHub and the OAuth app for authentication to succeed.
Connectors only read and index data; they never modify or delete anything in your external applications. Connectors use OAuth 2.0 or token-based authentication, depending on the source. For OAuth, grant only the scopes listed on the connector’s documentation page when you create your OAuth app in the service’s developer console. For a token, the connector’s page says what access the token’s user needs.Some sources only expose what a connector needs to read through broader permissions. For example, GitHub lists a private repository’s collaborators only to accounts with Write access, and Salesforce’s api scope covers both reading and writing. Use the least access each connector’s page asks for.
Turning off Sync Enabled on a connector’s instance card pauses that connector. PipesHub asks you to confirm before it does.
  • Indexed records stay searchable. Records that were fully indexed before you turned sync off still show up in search, chat, and agents, for the people who could see them before.
  • Records that were never indexed stay unsearchable. For example, records left out by Enable Manual Indexing or by the connector’s indexing filters were not searchable before, and turning sync off does not change that.
  • A record with an update still waiting to be indexed can drop out of search. If an edit had been synced but not yet indexed when you turned sync off, that record leaves search until it is indexed again. Turning sync back on queues these records for indexing automatically, so you don’t need a full sync or a manual reindex.
  • Access is frozen as of that moment. While sync is off, PipesHub reads nothing from the source, including changes to sharing. If someone gains or loses access to a file in the source app, PipesHub keeps the access it had when you turned sync off. The change reaches PipesHub only after you turn sync back on.
  • New and edited content stops arriving until you turn sync back on.
Saving configuration changes on a connector whose sync is on turns its sync off first, and it stays off after the save until you turn it back on.To remove a connector’s records from PipesHub, delete the connector instead: open the instance, go to Settings, and choose Remove connector instance.
There are three common causes:
  1. Email mismatch - The email used during connector authentication doesn’t match your PipesHub account email. This causes permission issues preventing you from accessing synced data.
    • Fix: Reconfigure the connector and authenticate using the same email as your PipesHub account.
  2. Records not displaying in “All Records” - Documents or data from the connector are not showing up at all in the All Records section.
    • Fix: Check permissions in the connector configuration, verify email match, and go to Settings > Connectors to ensure all records have synced successfully.
  3. Data not yet indexed - The connector is still syncing or hasn’t completed the initial indexing process.
    • Fix: Go to Settings > Connectors, check the sync status, and wait for indexing to complete.