Workflows stores a number of content properties on Confluence content. Historically, these properties were considered internal implementation details and were neither officially documented nor supported.
Because content properties are accessible through the Confluence REST API, users have nevertheless used Workflows content properties to build external automations, integrations, and reporting tools. While these integrations often worked successfully, the underlying properties were undocumented, outside our support scope, and not guaranteed to remain stable over time.
We recognise the value of these use cases and are now formalising support for a defined set of Workflows content properties. The properties documented here are part of the supported public contract for Workflows and are intended for long-term external use.
Any additions, edits, and/or removals to these content properties will be documented with advance notice being given to users.
Any content properties outwith this document remain unsupported and are subject to change without notice.
Content properties
For pages that pre-date the introduction date on each of the content properties below, property data may not be present and up-to-date until the documented conditions have been met on the page post-introduction.
Latest Finalised Official Version
Data about the latest official version which has been approved and finalised on the page.
|
Name |
|
|---|---|
|
Introduced |
|
|
Schema |
|
|
Conditions |
|
Need programmatic access to Workflows data that doesn’t exist yet? Feel free to reach out to our service desk to file a feature request; we would love to hear about your use case!
Need support? We’re here to help 🧡
If you have any questions or would like to speak with us about Workflows, please don’t hesitate to reach out to our Customer Support team.