Stop writing wiki pages by hand. Generate clean Confluence pages from a template whenever a form, script, or app sends data to your webhook. Great for status reports, meeting notes, SOPs, and launch checklists.

A webhook receives a POST and passes inputs forward. A Set node holds your site URL and the template ID so changes are easy. The workflow pulls the template content from Confluence using your API token. A Code node finds tokens like $project.name$ in the title and body and replaces them with values from the payload. It then calls the Confluence REST API to create a new page. A time stamp is added to the title so names stay unique.

You need an Atlassian account, a Confluence API token, your base URL, and the template ID. Send a small JSON test to the webhook and confirm a new page appears in your space. Teams usually cut page creation from about 10 minutes to under a minute and get the same format every time. Common uses include weekly updates, onboarding checklists, and release notes. After testing, turn it on and point any tool that can send HTTP requests to the webhook.

• Webhook trigger accepts POST requests from forms, apps, or scripts
• Central parameters in the Set node for base URL and template ID
• HTTP request pulls template content from the Confluence REST API
• Code node replaces $placeholder$ tokens in both title and body
• HTTP request creates the page with a time stamped title for uniqueness
• Basic authentication using email and API token stored in n8n credentials

• Reduce manual work from 10 minutes to 1 minute per page
• Streamline documentation by up to 80 percent using one webhook
• Improve consistency and reduce formatting errors by 90 percent
• Connect any tool that can send HTTP requests to Confluence
• Handle many page requests without extra clicks or copy paste

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Atlassian Confluence. See the Tools Required section above for links to create accounts with these services.
3. In your Atlassian account, create a Confluence API token. Save it somewhere secure. You will use your email as the username and the API token as the password.
4. In the n8n credentials manager, create a new HTTP Basic Auth credential named clearly, for example Atlassian. Use your Atlassian email as the username and paste the API token as the password. If unsure, double click the Confluence HTTP Request node, choose Credential to connect with, click Create new credential, and follow the on screen steps.
5. Open the Set parameters node. Enter your confluence_base_url, for example https://your-domain.atlassian.net, and the template_id of the space template you want to use. Add a default page_title if provided.
6. Double click the Confluence HTTP Request nodes and select the credential you created so both requests use the same Basic Auth.
7. Copy the Test URL from the Webhook node. Send a POST request with JSON that includes keys for each placeholder, for example { "values": { "project.name": "Apollo", "owner": "Dana" }, "page_title": "Release Notes" }.
8. Execute the workflow in n8n and send the test POST using curl or Postman. Confirm that the template content is fetched and a new Confluence page appears with the expected title and replaced text.
9. If you see 401 errors, check the email and API token in your credential. If you see 404, verify the template_id and base URL. If placeholders do not change, make sure your JSON keys match the tokens in the template exactly, including dots and case.
10. Switch the Webhook node to Production URL and turn on the workflow. Connect your form, CRM, or CI pipeline to POST to the webhook whenever you need a new page.