Audit Confluence space permissions and public links for compliance
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 12 nodes and runs manually, when you click “Execute workflow”. Along the way it connects GraphQL.
How it runs
Trigger: Manually, when you click “Execute workflow”.
- Set Variables (Edit Fields (Set)): sets 2 fields: atlassianDomain, spaceKeys
- Confluence - Get Spaces (HTTP Request): calls an HTTP API
- Split Out: splits a list into separate items
- Confluence - GQL Space Pages with Public Link (GraphQL): uses GraphQL
- Confluence - GQL Space Public Links Enabled (GraphQL): uses GraphQL
- Confluence - GQL Space Anonymous Access (GraphQL): uses GraphQL
- Set Space Pages with Public Link (Edit Fields (Set)): sets 1 field: pagesWithPublicLink
- Set Space Public Links Enabled (Edit Fields (Set)): sets 1 field: publicLinksEnabled
- Set Anonymous Access (Edit Fields (Set)): sets 1 field: anonymousAccess
- Merge: merges the data from its input branches
…plus 1 more step. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (6)
- Manual Trigger
n8n-nodes-base.manualTrigger - Edit Fields (Set)
n8n-nodes-base.set - GraphQL
n8n-nodes-base.graphql - Split Out
n8n-nodes-base.splitOut - Merge
n8n-nodes-base.merge - HTTP Request
n8n-nodes-base.httpRequest
From the author
Audit permissions in Confluence to ensure compliance This workflow scans selected Confluence spaces for public exposure risks, helping teams identify unintended access and potential data leakage. What it does - Detects public exposure risks in Confluence…