Skip to content
TeamLoop

Confluence Integration

Connect Confluence to search pages, blog posts, and documentation across your spaces.

What You Can Query

Section titled “What You Can Query”
Content TypeDescription
PagesWiki pages, specs, runbooks
Blog PostsTeam updates, announcements
CommentsDiscussion threads on pages
SpacesSpace-level metadata and structure

Connecting Confluence

Section titled “Connecting Confluence”

Confluence uses an Atlassian connection shared with Jira. One connection enables both integrations.

  1. Log into TeamLoop at app.teamloop.io
  2. Navigate to Settings > Integrations
  3. Click Connect next to Atlassian
  4. Enter your Atlassian email, API token, and site URL (e.g., yoursite.atlassian.net)
  5. TeamLoop validates the credentials and saves them encrypted

If you already connected Atlassian for Jira, Confluence is automatically available.

Creating an Atlassian API Token

Section titled “Creating an Atlassian API Token”
  1. Go to id.atlassian.com/manage-profile/security/api-tokens
  2. Click Create API token
  3. Give it a label (e.g., “TeamLoop”)
  4. Copy the token
  5. In TeamLoop, enter your Atlassian email, the API token, and your site URL

See the Jira Integration page for more details on Atlassian authentication.

Your API token provides read access to all Confluence spaces your Atlassian account can access. We never write to your Confluence instance.

Example Queries

Section titled “Example Queries”

Search Documentation

Section titled “Search Documentation”
teamloop_query:
  query: "API design guidelines"
  sources: "confluence"

Find Architecture Decisions

Section titled “Find Architecture Decisions”
teamloop_query:
  query: "architecture decision record database"
  sources: "confluence"

Search Team Processes

Section titled “Search Team Processes”
teamloop_query:
  query: "deployment process runbook"
  sources: "confluence"

Automatic Change Tracking

Section titled “Automatic Change Tracking”

TeamLoop automatically tracks Confluence page revisions. Confluence provides detailed version history that makes it excellent for temporal queries.

Page Version History

Section titled “Page Version History”

When you query a page, TeamLoop fetches its version history:

  • Version numbers with timestamps
  • Author of each version
  • Content changes between versions
  • Page title changes

This version history makes Confluence ideal for answering “what did the spec say last month?” queries.

Entity Extraction

Section titled “Entity Extraction”

Confluence content maps to TeamLoop entity types:

Confluence ContentTeamLoop Entity
PageDOCUMENT
Blog postDOCUMENT
CommentDOCUMENT
SpacePROJECT
Person mentionPERSON
Page updateCHANGE

Temporal Queries with Confluence

Section titled “Temporal Queries with Confluence”

Point-in-Time

Section titled “Point-in-Time”

What was documented on a specific date:

teamloop_query:
  query: "authentication design spec"
  sources: "confluence"
  mode: "as_of"
  as_of: "2024-06-01"

Evolution

Section titled “Evolution”

Track how documentation changed over time:

teamloop_evolution:
  query: "product requirements"
  from_date: "2024-01-01"
  to_date: "2024-06-30"

Troubleshooting

Section titled “Troubleshooting”

No Results

Section titled “No Results”
  • Verify the Atlassian integration is connected
  • Check that your Atlassian account has access to the Confluence space
  • Ensure pages aren’t in restricted spaces
  • Try broader search terms

Missing Pages

Section titled “Missing Pages”
  • Check space permissions in Confluence
  • Verify your Atlassian account has the correct role
  • Pages in personal spaces may require additional access

Security

Section titled “Security”
  • API tokens are encrypted at rest using pgcrypto
  • Accesses all Confluence spaces your Atlassian account can see
  • You can revoke the token at id.atlassian.com/manage-profile/security/api-tokens
  • TeamLoop never writes to Confluence
  • You can disconnect at any time from TeamLoop settings

Next Steps

Section titled “Next Steps”