Skip to content
← Back to documentation
Technical Reference

Confluence

Confluence integration for Flows360 workflows.

CategoryContent And Files
Authenticationcustom
Version0.3.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Confluence with Flows360

Confluence integration for Flows360 workflows.

Use the Confluence connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 21 actions and 5 triggers.

Available actions

  • Get Page Content
  • Get Page by URL
  • Find Page by Title
  • Search Content (CQL)
  • Create Page
  • Create Page from Template
  • Update Page
  • Delete Page
  • Plus 13 additional declared actions.

Available triggers

  • New Page
  • Updated Page
  • New Comment on Page
  • New Attachment
  • New Blog Post

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Confluence
  • Package: @activepieces/piece-confluence@0.3.0
  • Exact artifact digest: sha256:7f391fd97c5938409019b0e180af977ae785933dd1045b3bd443412c8daade12
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Get Page Content (getPageContent), Get page content and optionally all its descendants Classification: read.
  • Get Page by URL (get-page-by-url), Fetches a page by its Confluence web URL (extracts the page ID automatically). Classification: read.
  • Find Page by Title (find-page-by-title), Finds a page by exact title, optionally scoped to a space. Classification: read.
  • Search Content (CQL) (search-pages), Search Confluence content with CQL (Confluence Query Language). Example: type = "page" AND space = "DOCS" AND title ~ "release". Classification: read.
  • Create Page (create-page), Creates a new page in a space with the given title and body. Classification: read.
  • Create Page from Template (create-page-from-template), Creates a new page from a template with the given title and variables. Classification: read.
  • Update Page (update-page), Updates the title, body, or status of an existing page. Classification: read.
  • Delete Page (delete-page), Trashes or permanently deletes a page. Classification: read.
  • Move Page (move-page), Moves a page to a new parent as a child, sibling, or to the top of the parent. Classification: read.
  • Publish Draft (publish-draft), Publishes a draft page (changes status from draft to current). Classification: read.
  • Add Comment to Page (add-comment), Adds a footer comment to a page. Classification: read.
  • Reply to Comment (reply-to-comment), Replies to an existing footer comment on a page. Classification: read.
  • List Comments (list-comments), Lists footer and/or inline comments on a page. Classification: read.
  • Upload Attachment (upload-attachment), Uploads a file as an attachment to a page. Classification: read.
  • Download Attachment (download-attachment), Downloads an attachment file by its ID and returns it as a file. Classification: read.
  • List Attachments (list-attachments), Lists all attachments on a page. Classification: read.
  • Add Label to Page (add-label), Adds one or more labels to a page. Classification: read.
  • Remove Label from Page (remove-label), Removes a label from a page. Classification: read.
  • Find User (find-user), Looks up Confluence users by name, email, or keyword. Classification: read.
  • List Spaces (list-spaces), Lists all spaces the authenticated user can access. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Page, polling.
  • Updated Page, polling.
  • New Comment on Page, polling.
  • New Attachment, polling.
  • New Blog Post, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objectsNot published
Supported actionsNot published
Triggers5

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Account Email Required
  • API token Required · protected credential
  • Confluence Domain Required

Triggers

New Page · Poll

Triggers when a new page is created.

Inputs

  • spaceId · string
Updated Page · Poll

Triggers when an existing page is updated (version > 1).

Inputs

  • spaceId · string
New Comment on Page · Poll

Triggers when a new footer comment is added to the selected page.

Inputs

  • spaceId · string
  • pageId · string
New Attachment · Poll

Triggers when a new attachment is uploaded to the selected page.

Inputs

  • spaceId · string
  • pageId · string
New Blog Post · Poll

Triggers when a new blog post is published in the selected space.

Inputs

  • spaceId · string

Setup

Setup

  1. Add the Confluence connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Account Email (username), required.
  • API token (password), required; stored as a sensitive connection value.
  • Confluence Domain (confluenceDomain), required.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-confluence@0.3.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 21 actions and 5 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Confluence connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-confluence@0.3.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.