Resources · Make integration

Confluence Make integrationAutomate Confluence with Make.

Could your Confluence space keep itself up to date? The Confluence Make integration gives you 15 modules: 2 scheduled triggers, 9 actions and 4 searches. This guide is for teams that document in Confluence and want pages to move with their other tools, with a first scenario built step by step.

Try the Confluence integration on MakeSee the 15 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Confluence Make integration do for your team?

The Confluence Make integration links your Confluence Cloud account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick such as a trigger, an action or a search. Confluence then reacts to your other apps, and your other apps react to Confluence, without a line of code.

Announce new documentation. Watch Pages spots a page that was created or updated, Get a Page reads its full content, and the next module posts the news wherever your team talks. Product managers stop pasting links by hand.

Publish release notes from another tool. When a ticket closes or a form comes in, Create a Blog Post writes the entry in the right space. Update a Blog Post fixes it later if the details change, so support always quotes the current version.

Audit a space before a cleanup. Search Pages returns every page, List Page Versions shows how each one evolved, and Delete a Page removes what the team agreed to drop. Keep that last step behind a filter you trust.

What Make does not do here: the two triggers are scheduled, there is no instant trigger in the directory, and anything outside the 15 modules goes through Make an API Call. n8n often covers the same app; the n8n vs Make comparison lays out both options, and the Make review or Make training helps you decide how far to go.

Connect

How do you connect Confluence to Make?

  1. 01

    Add a Confluence module

    Open your scenario, add any Confluence module, then click Create a connection. A connection is your Confluence account linked to Make once; every Confluence module in your scenarios reuses it afterwards.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear label such as the site or the team helps when several people share one Make organization and you end up with more than one Confluence account.

  3. 03

    Sign in or paste your credentials

    Enter the credentials copied from your Confluence account, or follow the on-screen steps. You need an active Confluence Cloud account, and Make accepts basic auth, OAuth 2.0 or JWT to authenticate it.

First scenario

Build your first Confluence scenario

GoalWhen a page is created or updated in Confluence, Make reads its full content so the next module can share it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Search for Confluence and pick Watch Pages as the first module.

  2. 02

    Link your account and set the trigger

    Click Create a connection and sign in. Once the connection exists, Make lists what it can read in Confluence, so you choose from menus instead of typing identifiers from memory.

  3. 03

    Read the page in full

    Click the + to the right of Watch Pages and add Get a Page. Map the page ID from the trigger, so each bundle (one page flowing to the next module) carries its complete content.

  4. 04

    Send it where your team reads

    Add one more module from the app your team lives in, a chat or an email tool, and map the page title and link. That third bubble is where the news actually lands.

  5. 05

    Test, then switch it on

    Edit a test page, then click Run once and open each module to read the bundles it received. When it looks right, set the schedule on the first module (every 15 minutes by default) and turn the scenario on.

Triggers

What starts a Confluence scenario

2 modules start a scenario when something happens in Confluence. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Confluence as soon as it happens.

Confluence1Watch Blog Posts

Watch Blog Posts

Scheduled trigger

In Make“Triggers when a blog post is created or updated.”

Watch Blog Posts hands your scenario every blog post that was created or updated since the last check, one bundle per post, so announcements, release notes and team news can travel to other tools on their own.

How it fires
Scheduled: Make checks Confluence on the scenario's schedule, which is every 15 minutes by default on a new scenario, so nothing happens between two checks.
When to use it
a communications lead who wants each new blog post echoed in the company chat or added to a newsletter draft without copying the text.
Watch out
an edit counts as well as a new post, so add a filter after the trigger if you only want first publications, otherwise a typo fix sends the same post twice.
Confluence2Watch Pages

Watch Pages

Scheduled trigger

In Make“Triggers when a page is created or updated.”

Watch Pages picks up pages that appeared or changed in Confluence since the previous check and feeds them to the rest of the scenario. It is the natural entry point for a review task or a message to the page owner.

How it fires
Scheduled: Make asks Confluence for new or edited pages at the interval set on the scenario (every 15 minutes by default), and it is never instant on this app.
When to use it
a team that wants a reviewer pinged whenever a procedure page is rewritten, or an index sheet updated whenever someone adds a page.
Watch out
the brief notice of a change is rarely enough for the next app; chain Get a Page whenever a later module needs the full content of the page.
Modules

Every Confluence module, explained

Confluence gives you 13 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Confluence1

Create a Blog Post

Action

In Make“Creates a new blog post in the space specified by the space ID.”

Create a Blog Post writes a new entry in the blog of the space you pick, so updates born in another tool get published in Confluence without anyone opening the editor.

When to use it
a shipped ticket should become an announcement everyone reads.
Watch out
Make needs the target space, so agree with the team on the space it actually reads before you publish anything.
Confluence2

Create a Page

Action

In Make“Creates a page in the space.”

Create a Page adds a fresh page to a space, which turns a structured event elsewhere into documentation your team can find and edit later on.

When to use it
a new client, project or incident should come with its own page, filled from the data the previous modules collected.
Watch out
running the scenario twice on the same bundle creates two pages; test with Run once on a single item before you switch the schedule on.
Confluence3

Delete a Blog Post

Action

In Make“Removes a blog post by its ID.”

Delete a Blog Post removes one post by its ID. It helps you retire temporary announcements once they no longer apply, instead of leaving stale news in the blog.

When to use it
a campaign or an event is over and the post that promoted it should disappear once another app marks it closed.
Watch out
keep a filter in front of this module and test it on a throwaway post first, because the scenario acts on whatever ID it receives.
Confluence4

Delete a Page

Action

In Make“Deletes a page by ID.”

Delete a Page takes a page ID and removes that page from Confluence. Paired with a search, it lets you clear out drafts or duplicates the team already agreed to drop.

When to use it
a cleanup list lives in a spreadsheet and each approved row should delete the matching page in Confluence.
Watch out
a bad mapping wipes the wrong page, so run the scenario with Run once on one page you do not need before trusting it with a batch.
Confluence5

Get a Blog Post

Action

In Make“Returns a specific blog post.”

Get a Blog Post returns one specific post, so later modules can reuse its title, body or details without searching through the whole blog again.

When to use it
you already hold the post ID, from Watch Blog Posts or a stored record, and the next step needs the complete post rather than a summary.
Watch out
it reads a single post you point at; to find posts by criteria, Search Blog Posts is the module to pick.
Confluence6

Get a Page

Action

In Make“Returns a specific page.”

Get a Page fetches one page you identify, with its content, and passes it to the next module as a single bundle ready to be mapped anywhere.

When to use it
right after Watch Pages, when an AI summary, a chat message or an archive copy needs the full page and not only the notice that it changed.
Watch out
each call counts as one operation, Make's unit of usage on your plan, so filter the trigger first if you only care about a few spaces.
Confluence7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call reaches any endpoint of the Confluence API with the connection you already set up, which covers what the other listed modules do not.

When to use it
the action you need is missing from the list and the Confluence API documentation shows a way to do it.
Watch out
you write the request yourself, path and body included, so read the vendor documentation closely and test with Run once before you rely on it.
Confluence8

Update a Blog Post

Action

In Make“Updates a blog post by its ID.”

Update a Blog Post changes an existing post by its ID, so a correction made in a source tool ends up in Confluence without a manual edit.

When to use it
a release date or a price listed in a post moved in your project tool and readers should see the corrected version.
Watch out
you need the ID of the post, so place Search Blog Posts or Get a Blog Post before this module when the scenario does not already carry it.
Confluence9

Update a Page

Action

In Make“Updates a page by ID.”

Update a Page rewrites the content of a page identified by its ID, which keeps living documents such as status boards or contact lists in sync with the tool that owns the data.

When to use it
a status page, an on-call roster or a price sheet should mirror a database each time that database changes.
Watch out
map the content from the source you trust, since the scenario writes whatever it receives onto the page, including an empty value from a bad mapping.
Confluence10

List Blog Post Versions

Search

In Make“Returns the versions of the specific blog page.”

List Blog Post Versions returns the history of one blog post, one bundle per version, so you can see how it evolved before acting on it.

When to use it
an editor wants a record of every revision of an important announcement copied into a spreadsheet for review.
Watch out
a search sends several bundles, and every module after it runs once per version; add an aggregator if the next step expects a single list.
Confluence11

List Page Versions

Search

In Make“Returns the versions of the specific page.”

List Page Versions gives you the successive versions of a single page. It turns Confluence history into data you can filter, log or compare in the rest of the scenario.

When to use it
a compliance or quality team needs proof of how a procedure page evolved, stored outside Confluence in a sheet or a database.
Watch out
a long history means many bundles, and therefore many operations further down the chain; filter on the versions you actually need.
Confluence12

Search Blog Posts

Search

In Make“Returns a list of blog posts based on a specified criteria or lists all blog posts.”

Search Blog Posts finds posts that match the criteria you set, or lists all of them, and hands each result to the next module separately.

When to use it
you want an inventory of the blog in a spreadsheet, or you need to find the post to update before calling Update a Blog Post.
Watch out
it may return zero, one or many bundles; decide what should happen when nothing matches, or the scenario simply stops there.
Confluence13

Search Pages

Search

In Make“Returns all pages.”

Search Pages returns the pages Make can reach, one bundle each, which is the starting point for audits, exports and bulk fixes across a space.

When to use it
a team lead wants every page listed in a sheet with its title and link, to plan a documentation cleanup with the owners.
Watch out
one bundle per page adds up quickly on a large wiki; put a filter right after it so later modules only run on the pages that matter.
Need help

Need help automating Confluence with Make?

A person reads every message.

FAQ

Confluence and Make: common questions

01Is the Confluence Make integration free?
Yes, Confluence is a standard app, so it is available on the Free plan of Make. That plan allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run on one bundle.
02What do you need to connect Confluence to Make?
You need an active Confluence Cloud account. In Make, add a Confluence module, click Create a connection, give it a name if you like, then enter the credentials from your Confluence account or follow the on-screen instructions. Make supports basic auth, OAuth 2.0 and JWT. For OAuth 2.0 (3LO) with your own app, you configure it in the Confluence developer console, paste the callback URI given by the Make documentation, and copy the Client ID and Client secret into the connection.
03Does the Confluence Make trigger fire instantly?
No. Watch Pages and Watch Blog Posts are both scheduled triggers: Make checks Confluence on the scenario's schedule, which is every 15 minutes by default for a new scenario. On the Free plan, 15 minutes is also the shortest interval, while paid plans go down to 1 minute. The directory lists no instant Confluence trigger, so if another app must start the flow at once, put that app's instant trigger first and use the Confluence modules as actions afterwards.
04What if a Confluence module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Confluence API with the connection you already created, so tasks outside the 15 listed modules remain possible. You write the request path and body yourself, which means reading the Confluence API documentation first. Test the call with Run once and inspect the bundle it returns before mapping its output. The Make documentation for this app notes it is AI-generated from the vendor documentation, so check important details with Confluence directly.
05Should you use Make or n8n for Confluence?
It depends on how your team likes to build. Confluence has 15 modules in Make, including 2 scheduled triggers and Make an API Call for anything missing, and every step is configured in a visual editor with menus filled from your account. Confluence often has an n8n node too. The honest criterion is which tool your team already uses and maintains, since a scenario that nobody can edit becomes a liability. Compare the two in a small test on the same Confluence use case before you commit.
Same platform

Other docs you might need on this stack.

Browse all integrations