Confluence Integration

What it does

  • Bring your team’s documentation and knowledge into VDF Cloud so answers reflect your context.

Adding the App

Recommended (OAuth 2.0):

  1. In VDF, go to Integrations → Confluence → Connect via OAuth.
  2. Sign in with your Atlassian account and grant access to VDF.
  3. You’ll be redirected back to VDF and the status will change to Connected.

Legacy (API token):

  1. In VDF, go to Integrations → Confluence → Connect with API Token.
  2. Enter your Confluence Cloud URL (e.g., your‑site.atlassian.net), username/email, and API token.
  3. Click Connect. You can disconnect anytime.

If you run into issues, see the Troubleshooting guide in this document.

Use in Chat

  • Ask questions like “Summarize our onboarding runbook” or “Where is the API key rotation guide?”
  • VDF Cloud blends your Confluence content with general knowledge for more precise answers.

Notes

  • After connecting, lightweight indexing begins automatically. You can keep working while it finishes.

Removing the App

There are two parts: disconnect in VDF and revoke/remove in Atlassian.

  • Disconnect in VDF (stops processing immediately):

    1. In VDF, go to Integrations → Confluence → Disconnect.
    2. This clears active tokens on our side and stops new API calls.

  • Revoke/Remove in Atlassian (account/workspace):

    1. Log in to your Atlassian account (Confluence Cloud).
    2. Go to Manage your apps/Connected apps (site admin) or your Atlassian account’s app authorizations.
    3. Find “VDF” (or your VDF app name) and revoke access/remove the app.

Potential implications of removal:

  • New content sync and searches from VDF will no longer access Confluence.
  • Existing indexed artifacts and references in VDF remain until deleted or per retention.
  • OAuth tokens and refresh tokens are invalidated or removed; VDF will cease all Confluence API access.

Examples and use cases

  • Quick summaries and answers:
    • "Summarize our onboarding runbook into 5 steps."
    • "Where is the incident escalation process documented?"
  • Turn long docs into checklists:
    • "Convert the ‘Deployment Guide’ page into a step‑by‑step checklist for engineers."
  • Compare and consolidate content:
    • "Compare ‘API Access Policy’ and ‘Security Policy’ pages and produce a unified guidance section."
  • Create communications from docs:
    • "Draft a short internal announcement summarizing the changes in ‘Release 2.3 Notes’."

At-a-glance table

Goal Prompt idea Output
Find content “Where is X documented?” Page references
Summarize “Summarize the onboarding runbook” 5‑step summary
Transform “Turn this page into a checklist” Actionable steps 
flowchart LR
  CF[Confluence] --> K[Vector Search]
  K --> A[Answer with references]

Troubleshooting

  • OAuth window closes but no connection — allow pop‑ups and complete the redirect that includes ?oauth=confluence at least once.
  • “state_invalid” or “access_denied” — start the flow from VDF Integrations and retry; if you cancelled consent, run Connect via OAuth again.
  • 401/unauthorized or expired — reconnect via OAuth to refresh tokens.
  • API token path fails — verify you’re using Confluence Cloud and a valid API token for the correct site (ends with .atlassian.net).
  • Indexing seems slow — initial indexing is incremental and runs in the background; content remains usable while it completes.

FAQ

  • Which authentication should I use? — OAuth 2.0 is recommended. API token is available as a fallback.
  • What content does VDF access? — Only spaces and pages you have permission to access through your account.
  • Can I limit what’s indexed? — Yes. Use selective sync (space keys, page IDs) when available, or restrict the bot’s permissions.
  • What happens to my data if I disconnect? — VDF stops calling Confluence. Indexed artifacts in VDF remain until you delete them or per retention.
  • How do I manage email notifications? — Manage your email preferences in your VDF profile; unsubscribe via the link in any email.

Contact Support

  • Email: support@vdf.ai
  • Hours: Mon–Fri, 09:00–18:00 UTC
  • First response SLA: Within 1 business day