Skip to main content
Telara

Integrations / Confluence

Confluence logo

Confluence

Confluence team collaboration and documentation platform

OAuth 2.0
Indexes
Actions
Events

What Telara does

Capability matrix

Indexes YesTracks spend NoDiscovers shadow AI NoRuns actions YesReal-time events Yes

Before you connect

Prerequisites

A Confluence Cloud site (not Server/Data Center unless Telara can reach it).
Confluence product admin, or a user who can approve Atlassian apps for that site.

Vendor setup

Get the credential

1
Click Connect in Telara
Settings → Integrations → Confluence. Telara sends you to Atlassian. You do not create an OAuth app or set a callback URL.
2
Pick the site and approve
On the Atlassian consent screen, choose the Cloud site Telara should index, then Allow. If you belong to several sites, the wrong site is the usual empty-space list.
3
Limit spaces if asked
Grant only the spaces Telara should see. You can start with one space and widen later.

Permissions Telara requests

  • read:confluence-space.summary
    OAuth 2.0
  • write:confluence-space
    OAuth 2.0
  • read:confluence-content.all
    OAuth 2.0
  • write:confluence-content
    OAuth 2.0
  • write:confluence-file
    OAuth 2.0
  • read:confluence-props
    OAuth 2.0
  • write:confluence-props
    OAuth 2.0
  • search:confluence
    OAuth 2.0
  • read:confluence-content.permission
    OAuth 2.0
  • read:confluence-user
    OAuth 2.0
  • read:confluence-groups
    OAuth 2.0
  • read:audit-log:confluence
    OAuth 2.0
  • read:content.restriction:confluence
    OAuth 2.0
  • write:content.restriction:confluence
    OAuth 2.0
  • read:space:confluence
    OAuth 2.0
  • read:page:confluence
    OAuth 2.0
  • read:hierarchical-content:confluence
    OAuth 2.0
  • offline_access
    OAuth 2.0

In Telara

Connect in Telara

OAuth 2.0

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Fields Telara asks for
  • Expires At
Basic auth

Basic authentication with email and API token (Confluence Cloud). base_url: your site URL e.g. https://yourcompany.atlassian.net

In Telara, open Settings → Integrations, choose this connector, and enter the username and password (or key) Telara asks for.

Fields Telara asks for
  • Email
  • API token
  • Base Url
Bearer token

Personal Access Token for Confluence Data Center / Server. base_url: your instance URL e.g. https://confluence.yourcompany.com

In Telara, open Settings → Integrations, choose this connector, and paste the bearer token into the field Telara shows.

Fields Telara asks for
  • Personal Access Token
  • Base Url

Knowledge

What gets indexed

ResourceCoverage
SpacePartial — not every record the vendor holds is synced
PagesPartial — not every record the vendor holds is synced

Sync

Freshness & sync

ResourceLagDeletions
SpaceUp to 1 dayRemoved records disappear on the next full sync
PagesUp to 1 dayRemoved records disappear on the next full sync

Data handling

Permissions & data handling

The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.

Excluded from semantic search: Space, Pages.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

Connecting Jira does not connect Confluence. They are separate Connect buttons.
Anonymous or restricted pages stay out of Telara if the authorizing user cannot open them.