Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Using webhook with page actions - how to set source page?

I am using Confluence Automation and want to copy a page.

I want to do it when it receives a webhook from Jira Automation.

All the actions say "will use the page of the trigger"

But the webhook trigger describes no way to set an ID or CQL as the 'page' for subsequent actions to use, and there is no 'lookupPage' like Jira llaows for issues.

Question: How can web trigger rules do anything useful to pages?

1 answer

1 accepted

0 votes
Answer accepted
Sam Harding
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 05, 2022

Hi @Edward Webb 

One way to do what you are describing is to use a combination of the webhook body's smart value, and the Branch Component `Branch rule / related entities`. The branching would essentially be a functional replacement for the 'lookupPage' concept.

In the sending of the webhook from Jira, you could include a page ID or a page title, then use the smart value `title = {{webhook.body.title}}` for the value of the CQL in the branch component. The rest of the action components should then be able to execute inside the branch, against the relevant Confluence entity.

Because the product is still young, there is some limitations on what is currently available, but better tooling and components to make that process easier will be coming in the future. For now, I hope that helps solve your problem!


Thank you @Sam Harding !

That is the approach I ended up taking.

A few asks/gaps remain for my use case:

- 'Add Comment' does not respect wiki markup, markdown, or HTML -- how to add a link?
- Ability to get the created page ID as a smart value that can be recorded AND/OR

- Ability to link Jira issues with Confluence pages.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events