Skip to main content

Confluence Feeds

Atlassian Confluence is a collaborative wiki tool used to help teams collaborate and share knowledge efficiently. The Confluence Feeds connector is a source-only ELT connector that extracts data from Confluence Cloud using the Confluence REST API v2. Select from five workspace objects — spaces, pages, blog posts, attachments, and users — and Nexla ingests each selected object as its own feed on a schedule, with full-refresh and incremental sync strategies available.

Confluence Feeds icon

Power end-to-end data operations for your Confluence Feeds API with Nexla. Our bi-directional Confluence Feeds connector is purpose-built for Confluence Feeds, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Confluence Feeds or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Confluence Feeds workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites​

The Confluence Feeds connector supports two authentication methods against Confluence Cloud: OAuth 2.0 (3-legged), recommended for production use, and API Token Authentication (your Atlassian account email plus an API token, sent as basic auth), suitable for personal use or testing. Gather the items for the method you plan to use before creating a credential in Nexla.

Option 1: OAuth 2.0 (3-legged)​

This method requires an OAuth 2.0 (3LO) app created in the Atlassian developer console. To set one up:

  1. Go to developer.atlassian.com, select your profile icon in the top-right corner, and select Developer console.

  2. Select the Create dropdown and choose OAuth 2.0 integration, then enter a name for the app and create it.

  3. In the app's Authorization section, select Configure next to OAuth 2.0 (3LO) and enter a callback URL.

  4. In the Permissions section, add the Confluence API and grant the scopes your integration needs. The connector's default scope set is read:confluence-space.summary read:confluence-content.all read:confluence-content.summary read:confluence-props read:confluence-user.

  5. In the app's Settings section, copy the Client ID and Client Secret.

  6. Note your Atlassian Cloud ID for the Confluence site you want to connect to. Atlassian's OAuth 2.0 (3LO) documentation describes retrieving it from the https://api.atlassian.com/oauth/token/accessible-resources endpoint after authorization; the id field of the returned site object is the cloud ID.

For details, see the Atlassian OAuth 2.0 (3LO) apps guide.

Option 2: API Token Authentication​

This method requires your Confluence Cloud domain, your Atlassian account email, and an Atlassian API token:

  1. Note your Confluence Cloud domain — the site URL without the protocol, in the format your-domain.atlassian.net.

  2. Note the email address associated with your Atlassian account.

  3. Generate an API token at https://id.atlassian.com/manage/api-tokens: sign in, click Create API token, enter a label (for example, Nexla Integration), and copy the generated token immediately — Atlassian does not display it again.

The API token inherits the permissions of the Atlassian account that created it, so the account must have access to the spaces, pages, and other content you plan to ingest. Treat the token as a sensitive secret and rotate it if it is exposed. For more information, see the Atlassian API token documentation and the Confluence REST API v2 introduction.

Authenticate​

Credentials required​

Connect to Confluence using OAuth 2.0 authorization code flow. Recommended for production use.

FieldRequiredSecretDescription
Client IDYesNoOAuth 2.0 Client ID from your Atlassian app
Client SecretYesYesOAuth 2.0 Client Secret from your Atlassian app
OAuth ScopesYesNoSpace-separated list of OAuth scopes
Cloud IDYesNoYour Atlassian Cloud ID (obtained after OAuth authentication)

Create a credential in Nexla​

  1. After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.

  2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

    Resource descriptions are recommended but are not required. Use them to identify the Confluence site, authentication method, or access level represented by this credential.

  3. Select the authentication method for this credential, and complete the fields for that method:

    • OAuth 2.0 (3-legged): Enter the Client ID and Client Secret from your Atlassian OAuth 2.0 app, the space-separated OAuth Scopes the credential should request, and the Cloud ID of the Confluence site. Complete the OAuth authorization flow when prompted so Nexla can obtain and refresh access tokens on your behalf.

    • API Token Authentication: Enter your Confluence Domain (for example, your-domain.atlassian.net), the Email Address associated with your Atlassian account, and the API Token generated in Prerequisites. Nexla sends the email and token as basic auth on requests to the Confluence REST API.

  4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation and can be selected for use with Confluence Feeds flows.

Use as a data source​

How This Connector Works​

The Confluence Feeds connector is a source-only, multi-feed ELT connector. Rather than configuring one endpoint at a time, you select the Confluence objects you want from a catalog of available resources, and Nexla ingests each selected object as its own feed from the Confluence REST API v2.

  • Discovery: When you create the source, Nexla lists the Confluence resources available from the connector and presents them for selection.

  • Loading strategies: The connector supports two data loading strategies, selectable in the Data Loading Strategy setting — Full Refresh (the default), which reads the complete current set of records for each feed on every run, and Incremental Sync, which reads only records changed within the configured lookback window.

  • Pagination: Confluence REST API v2 responses are paginated with next-page links. Nexla follows the pagination links automatically while reading each feed, using the configured Page Size (1–100 records per page; default 25).

  • Deduplication: The id field is used as the primary key to uniquely identify records within each feed.

  • Parallel ingestion: Selected feeds are ingested in parallel (up to three feeds at a time), so a single source can pull multiple Confluence objects on the same schedule.

Create a New Data Flow​

  1. To create a new data flow, navigate to the Integrate section, click the New Data Flow button, select the ELT flow type, and click Create.

  2. Select the Confluence Feeds connector tile from the list of available connectors. Then, select the credential that will be used to connect to the Confluence site and click Next; or, create a new Confluence Feeds credential for use in this flow.

Select the Objects to Ingest​

After authenticating, Nexla lists the Confluence objects available from the connector. Select one or more of the following objects to ingest. Each selected object becomes its own feed and is refreshed on the configured schedule.

  • Spaces — Confluence spaces.
  • Pages — Confluence pages.
  • Blog Posts — Confluence blog posts.
  • Attachments — File attachments.
  • Users — Confluence users.

Configure Loading Options​

  • Data Loading Strategy — Choose Full Refresh to re-read all records for each feed on every run, or Incremental Sync to read only recent changes. With incremental sync, pages and blog posts are filtered by their last-modified date, and spaces and attachments are filtered by their created date; the users feed is always read in full.

  • Incremental Sync Lookback Time — When using incremental sync, set the lookback window for each run — for example, {now-1d} for one day (the default) or {now-7d} for seven days.

  • Page Size — The number of records fetched per API request, between 1 and 100 (default 25).

Schedule and Activate​

  • Use the default sync schedule or adjust the schedule in the source settings before activating the flow. On each run, every selected feed is read using its configured loading strategy, and Nexla organizes the ingested data into Nexsets.

Reference​

For object schemas, field definitions, and additional detail on each Confluence endpoint, see the Confluence REST API v2 documentation.