confluence

import { confluence } from '@agentskit/tools/integrations'

const tools = confluence({
  baseUrl: 'https://my-org.atlassian.net',
  email: process.env.CONFLUENCE_EMAIL!,
  apiToken: process.env.CONFLUENCE_API_TOKEN!,
})

Bundled: confluence(config) returns both sub-tools. Uses Confluence REST API (search at /wiki/rest/api, create at /wiki/api/v2) under your Atlassian site.

#Sub-tools

#Schema

#confluence_search

Returns: id, title, url for each matching page.

#confluence_create_page

Returns: id and url of the created page.

#Example — knowledge-base agent

import { createRuntime } from '@agentskit/runtime'
import { confluence } from '@agentskit/tools/integrations'

const runtime = createRuntime({
  adapter,
  systemPrompt: 'You answer questions from the engineering Confluence. Cite the page title and URL.',
  tools: confluence({
    baseUrl: process.env.CONFLUENCE_BASE_URL!,
    email: process.env.CONFLUENCE_EMAIL!,
    apiToken: process.env.CONFLUENCE_API_TOKEN!,
  }),
})

await runtime.run('What is our on-call escalation policy?')

#Security

• Env vars required: CONFLUENCE_EMAIL, CONFLUENCE_API_TOKEN (Atlassian API token from id.atlassian.com/manage-profile/security/api-tokens), and the site base URL.
• Authentication is HTTP Basic: email:apiToken base64-encoded. Never commit tokens; use env vars or a secrets manager.
• Use a service-account email for production agents.
• confluence_create_page writes content to your Confluence space — gate via HITL for autonomous agents.
• CQL queries are passed directly to Confluence — treat user-supplied CQL fragments as untrusted input.

#Related

• jira — pair with Confluence for full Atlassian issue + docs coverage.
• Integrations overview