Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
To listen for a deleted Confluence page in a Forge app, subscribe to avi:confluence:deleted:page. Configure the required OAuth scopes, obtain site-admin approval for event-payload access, and design cleanup around the app system user’s permissions. Do not expect a separate event for every page or other descendant removed by a cascade.
Register for the page deletion event
The Confluence Cloud event identifier for a deleted page is avi:confluence:deleted:page. Atlassian groups it with page and live-document lifecycle events in its Confluence Forge events reference.
For page, live-document, and blog-post events, the reference lists read:confluence-content.summary. Trashed and deleted events also require write:confluence-content; Atlassian notes that this additional scope requirement may change in the future. The site’s administrator must also grant the app permission to access the data included in event payloads.
Use the current Forge module documentation to configure the trigger and permissions for your app. The cited event reference identifies the event and its scope requirements, but does not provide a complete event-specific manifest example.
#1 Best Overall
Read the payload defensively
The documented common payload fields are eventType, atlassianId, eventCreatedDate, suppressNotifications, selfGenerated, and content. The content field represents the page, live doc, or blog post. eventCreatedDate uses ISO 8601. atlassianId is absent when an anonymous user caused the event, so do not make actor identification a prerequisite for processing deletion.
Validate the event type and content identifiers your handler needs, and allow for documented optional or absent fields. The event reference describes the common payload, but the cited sources do not establish event delivery timing or retry guarantees.
Rank #2
- Used Book in Good Condition
Plan for the app system user’s access
Forge event handlers run as the app system user, not as the person who initiated the deletion. If your handler fetches additional information, the app identity may lack permission to access a resource that the initiating user could see. Check access under the app’s identity and handle failed reads without assuming the user’s permissions apply.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteHandle cascading deletion at the parent level
Atlassian emits delete events for top-level entities in cascading deletion cases, not one event for every descendant. Deleting a space, for example, does not produce separate delete events for its child pages and other descendants. Likewise, deleting a page or blog post does not produce separate events for descendants such as comments, attachments, or custom content. See Atlassian’s Forge events guide.
Rank #3
- PLAY THE ULTIMATE CREATIVE CLASS—Become a master of magical inventions with the revised Artificer class, redesigned for the new Core Rules
- 5 ARTIFICER SUBCLASSES—Choose from 4 revised Artificer subclasses and 1 new subclass: the Cartographer
- SPARK NEW CHARACTER IDEAS—Explore 5 revised species, 18 backgrounds, and 28 feats, including the redesigned Dragonmarks, which are no longer species-locked
- EXPERIMENT WITH NEW OPTIONS—Eberron: Forge of the Artificer includes new spells, bastions, and magic items
- CRAFT EXHILIRATING ADVENTURES FOR YOUR PARTY—Use 3 different campaign models with guidance for building fantasy noir, political thriller, and pulp adventure campaigns in the world of Eberron
If your app needs to remove or reconcile descendant records, save the relevant relationships while they are still available and make the parent entity’s deletion handling cover its descendants. A consumer that relies on one event per child will leave stale associations after a cascade.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Distinguish page deletion from trashing and purging
The Forge event tells your app about a deletion; it does not define the REST API’s deletion behavior. In the Confluence Cloud REST API v2, the page deletion operation accepts a page ID. Its outcome depends on whether the page is a draft and which query parameter you use.
| Operation | How it works | Permission detail |
|---|---|---|
| Delete a non-draft page by default | Moves the page to trash, where it may be restored. | The operation requires permission to view the page and space and permission to delete pages in the space. |
| Delete a draft | Pass draft=true. The discarded draft is permanently deleted rather than sent to trash. |
The operation’s general page and space viewing and page-deletion permissions apply. |
| Permanently delete a trashed page | Pass purge=true to purge an already trashed page. |
Purge additionally requires the space’s manage/content permission. |
The API reference lists delete:page:confluence as the OAuth 2.0 scope for the deletion operation. A successful deletion returns HTTP 204 No Content. Check the Confluence Cloud REST API v2 Page API for the current operation details.
Quick Recap
Best Value
Implementation checklist
- Register a Forge event trigger for
avi:confluence:deleted:pageusing the current module reference. - Configure
read:confluence-content.summaryand the additionalwrite:confluence-contentscope required for deleted events; have a site administrator grant access to payload data. - Parse the event type and content identifiers while allowing for an absent
atlassianId. - Use app-system-user permissions when fetching extra data, and handle access failures.
- Persist relationships before deletion if later descendant cleanup depends on them; process descendant cleanup from the parent deletion rather than waiting for child events.
- For REST deletion, select default trashing, draft deletion, or purge based on the page state and intended reversibility, and verify the corresponding permissions.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
