Confluence
Productivity Email and API tokenRead and write Confluence pages, spaces and attachments from any Windmill script, flow or app.
Set up in 3 steps
Create an API token
At id.atlassian.com, under Security, create an API token. Copy it — it is shown only once.
Add the resource in Windmill
Open Resources, add a resource of type confluence. baseUrl is your site — https://yourteam.atlassian.net/wiki — email is your Atlassian account email, and apiToken is the token.
Run your first script
Fork any script below and read before writing anything.
Scripts
Building blocks, if none of the projects above fit. Fork one, run it, or call it as a step inside your own flow.
New or Updated Page
Update Page
Update Blog Post
Search Content (CQL)
List Spaces
List Pages
List Blog Posts
Get Pages in Space
Get Page by ID
Get Current User
Delete Page
Delete Blog Post
Create Page
Create Blog Post
Add content watcher
Add group to content restriction
Add label watcher
Add labels to a space
Add labels to content
Add member to group by groupId
Add new custom content permission to space
Add new permission to space
Add space watcher
Add user to content restriction
Archive pages
Asynchronously convert content body
Check content permissions
Copy page hierarchy
Copy single page
Create asynchronous content body conversion tasks in bulk
Resource type
confluence — the shape of the credential every script on this page expects.
| Field | Type | Required | What it is |
|---|---|---|---|
| apiToken | string | Yes | API token for your Atlassian account. Create one at https://id.atlassian.com/manage-profile/security/api-tokens |
| baseUrl | string | Yes | Base URL of your Confluence Cloud site, e.g. https://your-domain.atlassian.net (no trailing slash, no /wiki). |
| string | Yes | Email of the Atlassian account used to authenticate. |
Questions
Why an email as well as a token?
Confluence Cloud authenticates over HTTP Basic with the account email as the username and the token as the password. Neither works alone.
Is this the recommended way?
Yes — Atlassian recommends API tokens for scripts and automation. OAuth is meant for distributable apps acting on many users' behalf.
Are my credentials stored on the hub?
Never. They live only in your own Windmill workspace, encrypted at rest.