Skip to content
EkLine Documentation

Manage a Confluence or Pylon knowledge base

Use Docs Agent to keep an internal Confluence or Pylon knowledge base accurate — update pages across a space, improve articles from support tickets, and publish changes back to the source.

Docs Agent helps internal teams keep a knowledge base accurate and up to date. Connect an internal Confluence space — for example, an engineering or support team’s knowledge base — or a Pylon knowledge base used by your support team. The agent updates individual pages, maintains an entire space, and improves articles from sources like support tickets, then publishes the changes straight back to the source with no copying between tools.

This guide starts with a single page, then shows how the same workflow scales to the whole knowledge base. By the end, your edits are live in Confluence or Pylon.

Before you begin

Section titled “Before you begin”

You need:

  • An EkLine account with Docs Agent and knowledge base management enabled.
  • A connected Confluence or Pylon knowledge base with at least one space or knowledge base marked as managed (see Connect your knowledge base).
  • Permission to edit the page or article you want to update.

Connect your knowledge base

Section titled “Connect your knowledge base”

An organization administrator connects the knowledge base once. The agent can then read from and write to the spaces or knowledge bases you select.

  1. Connect Confluence under Settings > Organization > Integrations.
  2. Go to Settings > Organization > KB Management.
  3. Enable Manage Confluence.
  4. Select each Confluence space you want the agent to manage.
  5. Click Save.

The agent can now read and update pages in the selected spaces.

Step 1: Open the editor

Section titled “Step 1: Open the editor”
  1. Log in to your EkLine dashboard.
  2. Click Docs Agent in the left navigation.

Step 2: Retrieve the page

Section titled “Step 2: Retrieve the page”

Ask the agent to fetch the page you want to update. The agent loads it into the editor panel as Markdown you can edit.

Paste the page URL:

Retrieve this Confluence page and fix the outdated CLI flags
in the installation section:
https://your-org.atlassian.net/wiki/spaces/ENG/pages/123456

The agent reads the live page and writes it into the editor panel, keeping the formatting the source needs for a clean round-trip.

Step 3: Review the retrieved content

Section titled “Step 3: Review the retrieved content”

Read through the page in the editor and confirm it matches what you expect to see in the knowledge base. Editing a page you retrieved keeps your changes scoped to that page.

Step 4: Edit with follow-up prompts

Section titled “Step 4: Edit with follow-up prompts”

Refine the page by continuing the conversation. The agent keeps the context from your first prompt, so you can build on the content incrementally. You can also edit directly in the editor panel.

Rewrite the "Requirements" section to list the new minimum
version, and add a note about the deprecated config option.

Step 5: Publish your changes

Section titled “Step 5: Publish your changes”

When the page is ready, publish it back to the source.

  1. Enable View All Changes in the toolbar to review a diff of your edits.
  2. Make any final adjustments in the editor panel.
  3. Click Update KB to publish. The tooltip reads Publish your knowledge base edits.

The Update KB button replaces Raise PR when you work on a knowledge base, because there is no pull request to open — your approval publishes the edits to the source instead.

Verify the update

Section titled “Verify the update”

Confirm the change reached the source:

  • Open the live page. The Confluence page or Pylon article shows your edits.
  • Check the structure. Headings, tables, and links render the way they did before, with your changes applied.
  • Confirm the diff matched. What you reviewed under View All Changes is what appears on the live page.

Maintain the whole knowledge base

Section titled “Maintain the whole knowledge base”

The same workflow scales beyond a single page. Point the agent at a managed space or knowledge base, and it can review many pages at once, apply consistent updates, and create new articles — publishing each change back with Update KB.

Review the Engineering space for pages that still reference the
old deployment command. Update each one to the new command and
summarize what you changed.

Review each change under View All Changes before you publish. For new Pylon articles, the agent uses the default author you set in KB Management.

Troubleshooting

Section titled “Troubleshooting”
ProblemCauseFix
The space or knowledge base isn’t available to the agentIt isn’t marked as managed, or the integration isn’t connectedEnable it under Settings > Organization > KB Management and confirm you selected the space or knowledge base
The agent can’t retrieve a pageThe connected account lacks permission, or the URL is wrongVerify you can open the page yourself, then paste the exact page URL
The Update KB button is disabledThere are no changes to publishMake an edit first — the button enables once the page differs from the retrieved version
A new Pylon article can’t be createdNo default author is setSet a Default author under Settings > Organization > KB Management

Next steps

Section titled “Next steps”