Integrations

Last verified: 31 July 2026

Cloud connectors are set up from the Connections page in the web app at app.remly.it. Local file indexing lives in the Mac app. Once connected, sources appear together in a single search.

Available cloud connectors

Jira and Confluence share an Atlassian account, site selection, and OAuth behaviour. See Atlassian.

Planned

Linear is a catalog entry only, with no runtime connector. Figma, Salesforce, HubSpot, Asana, Microsoft Teams, ClickUp, and Zoom are the same.

Mac local files

Local files is not a cloud connector. It is a capability of the Mac companion app, which is implemented but not yet publicly downloadable.

How connectors work

Indexed versus live

Connectors run in one of two modes, and some do both:

• Indexed – Remly extracts text, embeds it, and stores derived chunks so the content is searchable and can ground Ask answers.
• Live – Remly queries the provider at request time. Nothing is stored, results are current, and coverage depends on what the provider's own search returns.

Each connector page states which mode applies. Slack is live only, and its content is never indexed.

Selection

Most connectors ask what they should cover before syncing: a workspace, an account, a site, a project, a space, or a set of folders or roots. Narrow selection means faster syncs and less irrelevant content in results. You can change a selection later; Remly fences the change so content from a removed selection is cleaned up rather than left orphaned.

Sync schedules

For indexed connectors you choose when they sync:

• Real-time, where the provider supports webhooks
• Every hour (default)
• Every 6 hours
• Daily, at a time you pick
• Manual only – you click Sync now

You can change the schedule per connector at any time.

How credentials are stored

Provider credentials are encrypted server-side before storage. Plaintext is only held in memory inside a request handler or sync job, sent to the provider in the Authorization header, and never returned in a response body. Refresh tokens are stored in the same encrypted bundle.

OAuth tokens are refreshed shortly before they expire. If a refresh fails – for example because you revoked Remly's access in the provider – the connection flips to an error state, the card shows Reconnect, and sync pauses until you renew it.

Not every connector uses OAuth. Granola uses a provider token, and the Mac app uses device pairing. See the individual pages.

Re-indexing

Each source card has a Sync now button. You can also re-index a single item from the Library page.

Pausing and disconnecting

Pausing stops scheduled syncs and leaves your indexed content in place.

Disconnect revokes access with the provider where the provider supports it, and immediately and permanently deletes that connector's sources, documents, text chunks, embeddings, and permissions. There is no recovery window and no undo – reconnecting starts a fresh index.

Your account survives, and other connectors on the same account are untouched. Disconnecting Jira does not affect your GitHub content.

Related

• Release status
• Usage limits – document and chunk caps that apply across all connectors
• Privacy and security