PageCraft documentation

Publisher: 汇科天下 (hktx.cn). Marketplace partner app for Confluence Cloud and Rovo. Support: [email protected].

PageCraft exposes Rovo and custom-agent actions that create or update rich Confluence pages — status lozenges, panels, column layouts, mentions, and an allowlist of macros — as the signed-in user. A custom agent’s built-in Create Page skill can only emit Markdown; PageCraft is the write path around that limit. The agent supplies structured sections; the app turns them into Confluence storage format and writes the page with asUser().

The app does not call an external model and does not hold an LLM API key. Rovo writes the words. PageCraft only materializes the page. It runs on Atlassian Forge with no remote backend and no external analytics.

Quick start

  1. Install PageCraft from the Atlassian Marketplace on your Confluence Cloud site, and accept the permission prompt.
  2. Open Rovo chat on a Confluence page. In the agent picker, choose the bundled agent named PageCraft. You can also attach PageCraft’s tools to an agent you build in Rovo Studio (see below).
  3. Ask the agent to create a rich page (for meeting notes, an ADR, an RFC, or a PIR, ask it to load a template first). Give a title and a space key when it asks. Do not invent owners, dates, or decisions if the facts are missing.
  4. When Rovo shows Please review for the Create rich page action, check the title, space, sections, and labels, then choose Confirm selected. The app does not write the page until you confirm.
  5. Open the page URL the agent returns and confirm status lozenges, panels, columns, and people mentions look correct.
Rovo chat agent picker listing the bundled PageCraft agent
Figure 1. In Rovo chat, open the agent picker and choose the bundled PageCraft agent.
Rovo Please review card for the Create rich page action, with Confirm selected
Figure 2. Review the Create rich page action (title, space key, labels, and sections) and choose Confirm selected. The write runs as you.
Confluence page created by PageCraft with a status lozenge, two-column layout, info and warning panels, and a user mention
Figure 3. A page created by PageCraft: a status lozenge, a two-column layout, info and warning panels, labels, and a real Confluence user mention rather than leftover Markdown.

What you can ask it to do

ActionWhat it does
Create rich pageCreates a page from a title, a space, optional parent page id, a JSON sections string, and optional labels.
Update rich pageReplaces the entire body of an existing page. Adding labels does not remove labels already on the page. It does not move the page or change restrictions.
Get page templateReturns JSON the agent can fill for meeting-notes, adr, rfc, or pir. Pass list for the catalog. This action does not write a page.

PageCraft does not change content restrictions or space permissions. A new page keeps the space’s normal permissions. Because Confluence calls run as the invoking user, the app cannot read or write anything that person cannot already do.

Use a custom agent in Rovo Studio

Install the app, then in Rovo Studio create an agent, choose Add tools, and under Connected apps add PageCraft’s three tools: Create rich page, Update rich page, and Get page template. The bundled PageCraft agent uses the same contract, so you can try it before writing your own. A starting instruction:

You are a Confluence page author. The built-in Create Page skill only writes Markdown. It cannot create panels, columns, status lozenges, or macros. Use PageCraft for those pages.

1. If the user wants meeting notes, an ADR, an RFC, or a PIR, call getPageTemplate first (template = meeting-notes | adr | rfc | pir). Use list if they only want the catalog.
2. Replace every {{token}} with facts the user gave you. If a fact is missing, ask once. Do not invent owners, dates, decisions, or incident causes.
3. Call createRichPage with a plain-text title, a space key, an optional numeric parentId the user supplied (never guess), a sections JSON array string, and optional labels.
4. For attendees, pass a mention with an accountId, or a people link [Name](/people/ari:cloud:identity::user/<accountId>). A bare name is fine when you do not know the account id. Do not leave Markdown people links as the page text.
5. Reply with the url from the tool. If ok is false, show error.message and do not claim the page exists.
6. To revise a page, call updateRichPage with its numeric pageId. That replaces the entire body. Confirm before replacing a page you did not just create.
7. Do not change restrictions or who can view a page. Labels only.

Create and update use action verbs CREATE and UPDATE. Atlassian does not let agents started by an automation rule invoke those verbs. Use PageCraft from chat. Get page template is GET and can run either way, but it does not publish a page.

Sections the agent can send

sections must be a JSON array string (Rovo action inputs are scalars). Supported kinds:

KindResult
headingHeading levels 1–6
paragraphParagraph text; people links become mentions
mentionA Confluence user mention when an account id is provided; otherwise the display name
panelInfo, note, tip, warning, error, success, or panel, with optional title
columnsOne to three cells (a column layout cannot nest inside another)
codeCode macro, with optional language and title
statusStatus lozenge (text up to 40 characters; colors Grey, Red, Yellow, Green, Blue, Purple)
macroAllowlisted macros only: toc, children, pagetree, contentbylabel, expand, excerpt

Text is XML-escaped. Raw HTML from the agent is not trusted. Labels are optional, comma-separated, at most 20, and limited to letters, numbers, hyphens, and underscores (for example, Meeting Notes, ADR becomes meeting-notes and adr).

Plans

Marketplace tier (listing intent)WhoPrice
FreeConfluence Cloud site with ≤10 users who can use Confluence$0
PaidSites above that cap10% of Confluence Cloud

This is the Marketplace listing price table. PageCraft does not bill inside the app.

Limits

Privacy and brand

Documentation for Marketplace App Review. Last updated 2026-11-13.