Connectors

Automatically sync documents from external sources into your knowledge base

Connectors let you pull documents directly from external services into your knowledge base. Instead of manually uploading files, a connector continuously syncs content from sources like Notion, Google Drive, GitHub, Slack, and more — keeping your knowledge base up to date automatically.

Available Connectors

SteelEngine ships with 30 built-in connectors spanning productivity tools, cloud storage, development platforms, and more.

CategoryConnectors
ProductivityNotion, Confluence, Asana, Linear, Jira, Google Calendar, Google Sheets
Cloud StorageGoogle Drive, Dropbox, OneDrive, SharePoint
DocumentsGoogle Docs, WordPress, Webflow
DevelopmentGitHub
CommunicationSlack, Discord, Microsoft Teams, Reddit
EmailGmail, Outlook
CRMHubSpot, Salesforce
SupportIntercom, ServiceNow, Zendesk
DataAirtable
Note-takingEvernote, Obsidian
MeetingsFireflies

Adding a Connector

Select a source

Open a knowledge base and click New connector. You'll see the full list of available connectors — pick the service you want to sync from.

Authenticate

Most connectors use OAuth — select an existing credential from the dropdown, or click Connect new account to authorize through the service's login flow. SteelEngine refreshes tokens when the provider permits it. Reconnect if the grant expires, is revoked, or needs different permissions.

Slack and Salesforce can use connections from Custom Apps. The connector uses the selected app and account, including that app's permissions and refresh configuration.

A few connectors (Evernote, Obsidian, Fireflies) use API keys instead. Paste your key or developer token directly, and it will be stored securely.

If you rotate an API key in the external service, you'll need to update it in SteelEngine as well. OAuth tokens are refreshed automatically, but API keys are not.

Configure

Each connector has its own configuration fields that control what gets synced. Some examples:

  • Notion: Choose between syncing an entire workspace, a specific database, or a single page tree
  • GitHub: Specify a repository, branch, and optional file extension filter
  • Confluence: Enter your Atlassian domain and optionally filter by space key or content type
  • Obsidian: Provide your vault URL and optionally restrict to a folder path

All configuration is validated when you save — if a repository doesn't exist or a domain is unreachable, you'll get an immediate error.

Choose sync frequency

Select how often the connector should re-sync:

FrequencyDescription
LiveEvery 5 minutes, for sources that must stay current
Every hourBest for fast-moving sources
Every 6 hoursGood balance for most use cases
Daily (default)Suitable for content that changes infrequently
WeeklyFor stable, rarely-updated sources
Manual onlySync only when you trigger it

Live requires a Team, Scale, or Enterprise plan on hosted SteelEngine. Other plans see it locked, and SteelEngine rejects any interval under an hour. Self-hosted deployments can use it on every plan.

Configure metadata tags (optional)

If the connector supports metadata tags, you'll see checkboxes for each tag type (e.g., Tags, Last Modified, Notebook). All are enabled by default — uncheck any you don't need.

See the Metadata Tags section below for details.

Connect & Sync

Click Connect & Sync to save the connector and trigger the first sync immediately. Documents will begin appearing in your knowledge base as they are processed.

Workload automation uses a separate paused configuration contract. It can create/update supported OAuth definitions using authorized workspace-local credentials, pause idle connectors with the connector update grant, and remove configuration while retaining documents. Pausing clears the next scheduled sync and prevents queued automatic syncs, including the first sync queued at creation, from restarting the connector. A pause request during a running sync returns a conflict. Activation and manual sync remain human-authorized operations. The machine configuration contract does not start ingestion or activate connectors. If configuration changes during validation, the change is rejected with a conflict; reload the current source before retrying.

How Syncing Works

On each sync, the connector fetches documents from the external service and compares them against what's already in your knowledge base. Only documents that have actually changed are reprocessed — new content is added, updated content is re-chunked and re-embedded, and documents that no longer exist in the source are removed.

This means syncing is efficient even for large document sets. A connector with thousands of documents will only do meaningful work when something changes.

Handling Failures

If a single document fails to fetch (e.g., due to a permission issue or timeout), the sync continues with the remaining documents. The failed document will be retried on the next sync cycle.

OAuth authentication failures are handled at the connection level, including failures while fetching an individual document. They can trigger token refresh or a reconnect requirement instead of being silently treated as an unavailable document.

If an entire sync fails (e.g., the service is down or credentials expired), the connector automatically backs off and retries later. Each consecutive failure adds 30 minutes to the wait, up to 24 hours. The backoff resets as soon as a sync succeeds. After 10 consecutive failures, SteelEngine marks the connector Disabled and stops scheduling syncs. Fix the cause, then use Reconnect (for OAuth connectors) or the resume button on the connector card to re-enable it.

Metadata Tags

Connectors can automatically populate tags with metadata from the source, letting you filter documents in the Knowledge block based on information from the external service.

For example, a Notion connector tags documents with their Tags, Last Modified date, and Created date. A GitHub connector tags documents with their File Path, Repository, Branch, File Size, and Last Modified date. This metadata becomes available for tag-based filtering in your workflows.

Opting Out

You can disable specific metadata tags during connector setup. Disabled tags won't be populated, leaving those tag slots available for other connectors or manual tagging.

Tag slots are shared across all documents in a knowledge base. If you have multiple connectors, each one's metadata tags draw from the same pool of available slots.

Excluding Documents

You can manually exclude specific documents from a connector's sync. Excluded documents are skipped on every subsequent sync, even if they change in the source. This is useful for filtering out templates, drafts, or other content you don't want in your knowledge base.

Every synced document retains a link back to the original in the external service. This lets you trace any knowledge base document to its source — whether that's a Notion page, a GitHub file, a Confluence article, or a Slack conversation.

Multiple Connectors

You can add multiple connectors to a single knowledge base. For example, you might sync internal documentation from Confluence alongside code from GitHub and meeting notes from Fireflies — all searchable together through the Knowledge block.

Each connector manages its own documents independently. Metadata tag slots are shared across the knowledge base, so keep an eye on slot usage if you're combining several connectors that each populate tags.

Common Use Cases

  • Internal knowledge base: Sync your team's Notion workspace and Confluence spaces so AI agents can answer questions about internal processes, policies, and documentation
  • Customer support: Connect HubSpot or Salesforce alongside your help docs from WordPress or Google Docs to give support agents full context on customers and product information
  • Engineering assistant: Sync a GitHub repository and Jira or Linear issues so an AI agent can reference code, specs, and ticket history when answering developer questions
  • Meeting intelligence: Pull in Fireflies transcripts alongside Slack conversations to build a searchable archive of decisions and discussions
  • Research and notes: Sync Evernote notebooks or an Obsidian vault to make your personal notes available to AI workflows

Common Questions

You can choose from live (every 5 minutes), hourly, every 6 hours, daily (default), weekly, or manual-only sync frequencies. Each connector can have its own schedule. Live sync requires a Team, Scale, or Enterprise plan on hosted SteelEngine.
On the next sync, the connector detects that the document no longer exists in the source and removes it from your knowledge base automatically.
Yes. You can add as many connectors as you need to a single knowledge base. Each connector manages its documents independently.
OAuth-based connectors refresh tokens automatically. API key-based connectors (Evernote, Obsidian, Fireflies) need manual updates if you rotate the key.
If a single document fails, the rest of the sync continues. If the entire sync fails (e.g., service is down), the connector backs off 30 minutes per consecutive failure (up to 24 hours) and retries automatically. After 10 consecutive failures it is disabled until you reconnect or resume it.
Yes. You can manually exclude documents from any connector. Excluded documents are skipped on every subsequent sync, even if they change in the source.
Tag slots are shared across all documents in a knowledge base. If you have multiple connectors, their metadata tags draw from the same pool of available slots.

On this page