Automation basics
Understand the general concepts and best practices of automation in Atlassian cloud products.
Automation is an admin feature available in Confluence Premium and Enterprise.
Smart values are dynamic variables that can make your rule more flexible. Each smart value is constructed using a specific syntax called dot notation inside double mustache brackets. It's written as a hierarchy, starting with a top-level object and followed by properties of that object, {{object.property.subProperty}}. Notice that multiword properties use camelCase capitalization.
When you’re trying to understand what a particular smart value might do, it can help to read them in reverse. For example:
{{page.title}} is "the title of the page" (that's relevant to your rule component).
{{page.parent.title}} is "the title of the parent (of the relevant) page”.
To learn more about what smart values are and how to use them, read What are smart values? in the Key concepts of Cloud automation.
This is a list of smart values that can currently be used in Confluence automation rules, grouped by object and sorted by the properties available for that object. Not all objects have the same properties.
Objects in Confluence include:
Smart values are case sensitive. Multiword properties use camelCase capitalization.
{{space.url}} – the URL link to the Overview of a specific space
{{space.id}} – the ID number that uniquely identifies a space
{{space.key}} – the keyword in the URL that serves as a unique identifier of a space
Example: http://confluence.atlassian.com/wiki/spaces/KEYWORD/pages
{{space.name}} – the name of the space
{{space.isPersonal}} – Boolean: returns True if the space a personal space and False if it’s not. This is useful, for example, if you want to exclude personal spaces from global rules.
{{content.type}} – identifies the type of relevant content as either a “page” or a “blogpost”.
Example in an automated message: “Hey check out this {{content.type}}”
{{page.url}} – the URL link to a specific page
{{page.parent.url}} – the URL link to a page’s parent page
{{blogpost.url}} – the URL link to a specific blog post
{{content.url}} – the URL link to a piece of content, whether it’s a page or a blog post
{{page.id}} – the ID number that uniquely identifies a page
{{page.parent.id}} – the ID number that uniquely identifies a page’s parent page
{{blogpost.id}} – the ID number that uniquely identifies a blog post
{{content.id}} – the ID number that uniquely identifies a piece of content, whether it’s a page or a blog post
{{page.title}} – the published title of a page
{{page.parent.title}} – the published title of a page’s parent page
{{blogpost.title}} – the published title of a blog post
{{content.title}} – the published title of a piece of content, whether it’s a page or a blog post
{{cqlResult.title}} – the published title of a piece of content that is returned as part of a CQL query.
This is useful, for example, when configuring a For each CQL result (related entities) branch.
{{page.author.fullName}} – the first and last name of the person who originally published the page (the “Full name” in their Atlassian account profile)
{{page.author.publicName}} – the public name of the person who originally published the page (the name or handle they use in public Atlassian forums like Community)
{{blogpost.author.fullName}} – the first and last name of the person who originally published the blog post (the “Full name” in their Atlassian account profile)
{{blogpost.author.publicName}} – the public name of the person who originally published the blog post (the name or handle they use in public Atlassian forums like Community)
{{content.author.fullName}} – the first and last name of the person who originally published the content, whether it’s a page or a blog post (the “Full name” in their Atlassian account profile)
{{content.author.publicName}} – the public name of the person who originally published the content, whether it’s a page or a blog post (the name or handle they use in public Atlassian forums like Community)
{{page.author.emailAddress}} – the email address of the person who originally published the page
{{blogpost.author.emailAddress}} – the email address of the person who originally published the blog post
{{content.author.emailAddress}} – the email address of the person who originally published the content, whether it’s a page or a blog post
{{page.author.timeZone}} – the time zone the person who originally published the page is in
{{blogpost.author.timeZone}} – the time zone the person who originally published the blog post is in
{{content.author.timeZone}} – the time zone the person who originally published the content is in, whether it’s a page or a blog post
{{page.author.accountId}} – the account ID number of the person who originally published the page
{{blogpost.author.accountId}} – the account ID number of the person who originally published the blog post
{{content.author.accountId}} – the account ID number of the person who originally published the content, whether it’s a page or a blog post
You can control the format of date smart values by adding a format modifier.
{{page.dateFirstPublished}} – the date the page was originally published
{{page.dateLastUpdated}} – the date the page was most recently updated
{{blogpost.dateFirstPublished}} – the date the blog post was originally published
{{blogpost.dateLastUpdated}} – the date the blog post was most recently updated
{{content.dateFirstPublished}} – the date the content was originally published, whether it’s a page or a blog post
{{content.dateLastUpdated}} – the date the content most recently updated, whether it’s a page or a blog post
{{page.labels}} – a list of URL links to all the labels on a page
See also: {{labels.url}}
{{content.status}} – the progress of a page or blog post, as indicated by the content status at the top (for example Rough draft, In progress, and Ready for review).
Suggested and/or Custom statuses must be turned on in order for this value to have something to return. Admins can control content statuses in Space settings.
{{content.state}} – the publication state of the page or blog post: either Draft, Current, Archived, or Deleted
{{comment.url}} – the URL link to a specific page or inline comment
{{comment.id}} – the ID number that uniquely identifies a page or inline comment
{{comment.body}} – the message body contained in the page or inline comment
{{comment.author.fullName}} – the first and last name of the person who wrote the comment (the “Full name” in their Atlassian account profile)
{{comment.author.publicName}} – the public name of the person who wrote the comment (the name or handle they use in public Atlassian forums like Community)
{{comment.author.emailAddress}} – the email address of the person who wrote the comment
{{comment.author.timeZone}} – the time zone the person who wrote the comment is in
{{comment.author.accountId}} – the account ID number of the person who wrote the comment
You can control the format of date smart values by adding a format modifier.
{{comment.dateAdded}} – the date the comment was added to the page
{{comment.dateLastEdited}} – the date the comment was most recently edited
{{task.id}} – the ID number that uniquely identifies a particular task (action item)
{{task.contentId}} – the ID number that uniquely identifies the page a particular task is on
{{task.body}} – the message body of the task that contains the assignment, assignee, and due date
{{task.creator.fullName}} – the first and last name of the person who added the task to the page and assigned it to someone (the “Full name” in their Atlassian account profile)
{{task.creator.publicName}} – the public name of the person who added the task to the page and assigned it to someone (the name or handle they use in public Atlassian forums like Community)
{{task.assignee.fullName}} – the first and last name of the person who was assigned a task (@ mention)
{{task.assignee.publicName}} – the public name of the person who was assigned a task (@ mention) (the name or handle they use in public Atlassian forums like Community)
{{task.creator.emailAddress}} – the email address of the person who added the task to the page and assigned it to someone
{{task.assignee.emailAddress}} – the email address of the person who was assigned a task (@ mention)
{{task.creator.timeZone}} – the time zone the person who added the task to the page, and assigned it to someone, is in
{{task.assignee.timeZone}} – the time zone of the person who was assigned a task (@ mention)
{{task.creator.accountId}} – the account ID number of the person who added the task to the page and assigned it to someone
{{task.assignee.accountId}} – the account ID number of the person who was assigned a task (@ mention)
You can control the format of date smart values by adding a format modifier.
{{task.dueDate}} – the task’s due date
{{task.dateLastEdited}} – the date the task was most recently edited
{{task.status}} – the progress of a task (either Complete or Incomplete)
{{user.fullName}} – the first and last name of the user (the “Full name” in their Atlassian account profile)
{{user.publicName}} – the public name of the user (the name or handle they use in public Atlassian forums like Community)
{{user.emailAddress}} – the email address of the user
{{user.timeZone}} – the time zone the user is in
{{user.accountId}} – the account ID number of the user
{{label.url}} – the URL link to a specific label
{{labels.url}} – a list of URL links of all the labels that were added or removed
See also: {{page.labels}}
{{label.id}} – the ID number that uniquely identifies a particular label
{{labels.id}} – a list of ID numbers of all the labels that were added or removed
{{label.contentId}} – the ID number that uniquely identifies the page or blog a particular label is on
{{label.name}} – the name of the label
{{labels.name}} – a list of names of all the labels that were added or removed
Was this helpful?