Askel connects to your customer's Confluence Cloud tenant and lets your product read pages, create new documentation, and update existing content in the spaces their teams already use for knowledge management.
Use the Confluence content API to create new pages in a named space, with title, body content in Confluence storage format or wiki markup, and a parent page for hierarchy.
Fetch the current page version and PUT an updated body, incrementing the version number correctly so Confluence preserves the edit history.
Retrieve the body, title, labels, version, and space key of any page the connecting user can access, useful for reading runbooks or configuration pages into your product.
Use the Confluence CQL search endpoint to find pages by title keyword, label, space, or last-modified date, so your product can locate the right page before reading or updating it.
Attach labels to pages programmatically to flag them for review, mark them as auto-generated, or categorise content created by your product.
Add file attachments to a Confluence page using the content attachments endpoint, useful for including PDFs, diagrams, or data exports alongside the page text.
You sell a cloud infrastructure management tool. Crestview Technologies expects a technical runbook to appear in their Confluence when their new environment is provisioned, covering connection details, maintenance procedures, and escalation contacts.
Crestview's Atlassian admin navigates to id.atlassian.com and generates an API token. They enter their Atlassian email address and the token in your product's onboarding form.
Askel calls the Confluence spaces endpoint to list available spaces. Your onboarding team picks the Infrastructure space as the destination for runbooks.
Askel searches for a page titled Customer Environments. If it does not exist, Askel creates it as the parent. The new runbook will be a child of this page.
Your product compiles the environment details into a Confluence storage format body. Askel creates the page with the title set to the customer's environment name.
Askel uploads the architecture diagram as a page attachment and adds the labels auto-generated and customer-runbook so the page is easily searchable.
Atlassian Confluence Cloud uses a unified token model: the customer generates an API token at id.atlassian.com, then provides their Atlassian account email address alongside the token. Askel uses HTTP Basic auth with the email as the username and the API token as the password. Personal API tokens can be revoked from the Atlassian account security page at any time.
© 2025 Askel.ai. All rights reserved.