+
Connect Confluence to GitHub
Automate Confluence and GitHub with AI
Architecture pages in Confluence go stale the moment the GitHub repo moves ahead of them. Your Operator agent on OpenClaw appends merged pull request titles to the Confluence release page, refreshes a doc with current file paths from the repo tree, and opens a GitHub issue when a page flags work that is not yet tracked. Ask what changed since the last release and it pulls the GitHub commits and the Confluence sections that mention them.
It reaches both apps directly or through connectors like Composio MCP and Pipedream MCP, which handle the sign in and token refresh, so there is no Zap to build and no API keys to paste.
What your agent can do with Confluence and GitHub
What your agent does in Confluence
Add Content Label
Tool to add labels to a piece of content. Use after obtaining the content ID to tag pages or blog posts with metadata labels.
CQL Search
Searches for content in Confluence using Confluence Query Language (CQL). CQL is a powerful query language that allows you to search across all Confluence content with advanced filtering capabilities including: - Full-text search: `text...
Create Blogpost
Tool to create a new Confluence blog post. Use when you need to publish content in a specific space. Response includes `data.id` for the post ID and `data._links.base` + `data._links.webui` for the URL.
Create Blogpost Property
Tool to create a property on a specified blog post. Use when you need to add custom metadata to a blog post. Creates a new property with a key-value pair on a specified Confluence blog post. This allows users to add custom metadata relev...
Create Whiteboard Property
Tool to create a new content property on a whiteboard. Use when you need to attach custom metadata to a Confluence whiteboard.
Create Footer Comment
Tool to create a footer comment on a Confluence page, blog post, attachment, or custom content. Use when you need to add a comment without editing the page body itself.
What your agent does in GitHub
Abort Repository Migration
Tool to abort a repository migration that is queued or in progress. Use when you need to cancel an ongoing migration operation.
Accept a repository invitation
Accepts a PENDING repository invitation that has been issued to the authenticated user.
Add app access restrictions
Adds GitHub Apps to the list of apps allowed to push to a protected branch. The branch must already have protection rules with restrictions enabled. This endpoint only works for organization repositories, not personal repositories. Apps...
Add a repository collaborator
Adds a GitHub user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation ma...
Add assignees to an issue
Adds assignees to a GitHub issue. This action only adds users - it does not remove existing assignees. Changes are silently ignored if the authenticated user lacks push access to the repository.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's GitHub account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the...
How it works
Tell the agent what you want to happen between Confluence and GitHub, for example to watch one and act in the other, or to keep the two in step. It reads what it needs from Confluence, works out what to do, and runs the matching action in GitHub without you mapping a single field.
You can have it run once, on a schedule, or whenever something changes. Ask it for a status any time and it reads the latest from both apps back to you in the same chat.
Common questions about Confluence and GitHub
- How do I connect Confluence and GitHub to Operator?
- You authorize Confluence and GitHub once each from your Operator dashboard. Operator holds both connections and refreshes the access tokens for you, so your agent keeps working across them without you signing in again.
- What can my agent do across Confluence and GitHub?
- Tell it the job and it moves between Confluence and GitHub as one task, choosing which actions to run on each side. There is nothing to map and no trigger to configure; you give instructions the way you would to a person.
- Can my agent keep Confluence and GitHub in sync?
- Yes. It can watch Confluence and act in GitHub, or keep both in step, reading from one and running the matching update in the other. This runs on demand when you ask or on a schedule you set.
- Do I need to build a workflow or write code?
- No. There is no workflow to build, no fields to map, and no API keys to paste. Operator manages both connections, and you give the agent instructions in plain language.
Confluence and GitHub integrations
Put your agent on Confluence and GitHub
Sign in, connect both apps, and hand your agent the work. The same setup reaches every app in the catalog. Your first week is free.
Try for free