Prevent Automation Webhook Trigger on REST API Page Updates in Confluence

[Ganesh Naiknavare]

I'm working with Confluence automation and have set up a rule that sends a webhook whenever a page is updated.

Here’s the setup:
1-When a page is updated directly in Confluence (manually edited), the automation rule triggers correctly and sends the webhook with the updated content.

2-I also have a process where content is updated locally in another system and pushed to Confluence using the REST API. In this case, I don’t want the automation webhook to be triggered.

Problem:
Currently, the webhook is triggered even when the page is updated via the REST API. I want to restrict the webhook trigger to only manual edits made directly in Confluence. How can I differentiate between manual edits and REST API updates in automation rules, or prevent automation from triggering in case of API-based updates?

Any suggestions or best practices to handle this?

[Tomislav Tobijas]

Hi @Ganesh Naiknavare ,

Is this somewhat related to Sourcetree? If so, can you maybe clarify?
I'm asking as this has landed in Sourcetree app group.

As for this specific question, Confluence automation cannot natively distinguish between manual edits and updates made via the REST API. Both trigger the same "page updated" event.

A potential workaround could be having your API process add a unique label, property, or marker to the page when updating via REST API. This would need to be tested, though.

On top of this, there is an open feature request to improve webhook administration and event filtering in Confluence: CONFCLOUD-36613: Allow Confluence Webhook Administration 

Cheers,
Tobi