Confluence

Productivity Email and API token

Read and write Confluence pages, spaces and attachments from any Windmill script, flow or app.

Set up in 3 steps

1

Create an API token

At id.atlassian.com, under Security, create an API token. Copy it — it is shown only once.

2

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.

3

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.

Submit a script →

Trigger flows from Confluence

Confluence is not only a destination. These inbound paths are supported today.

New or updated page (scheduled poll)

The New or Updated Page trigger script polls Confluence and returns the pages created or updated since its last run, optionally for one space. To run it, open a flow, add a trigger and choose Scheduled Poll, then pick the trigger script and an interval. Windmill puts the script first in the flow with a loop after it, so the steps you add run once per new item. The cursor is saved per flow: two flows polling the same source each get every item, and test runs keep a cursor of their own.

Resource type

The shape of the credential every script on this page expects.

FieldTypeRequiredWhat it is
apiTokenstringYesAPI token for your Atlassian account. Create one at https://id.atlassian.com/manage-profile/security/api-tokens
baseUrlstringYesBase URL of your Confluence Cloud site, e.g. https://your-domain.atlassian.net (no trailing slash, no /wiki).
emailstringYesEmail 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.