Confluence Connector
Description
Confluence is an open and shared workspace platform provided by Atlassian. Use the Confluence component to manage spaces, pages, and content properties.
API Documentation
This component was built using the Confluence Cloud REST API v2.
Connections
Basic Authentication
key: basicBasic Authentication can be used to connect to both Confluence Cloud and self-hosted Confluence instances.
- For Confluence Cloud: Use the account email and an API token
- For Self-hosted Confluence: Use the account email and password
For Confluence Cloud, API tokens are required. Passwords are only accepted for self-hosted instances.
Prerequisites
- A Confluence account (Cloud or self-hosted)
- For Cloud: Access to Atlassian account management
- The Confluence site URL
Setup Steps
To generate an API token for Confluence Cloud:
- Log in to Atlassian API Token Management
- Select Create API token
- Enter a descriptive Label for the token and select Create
- Select Copy to clipboard to copy the generated token
For additional information on generating an API token, refer to the Atlassian documentation.
Configure the Connection
Add a Confluence action to the integration to automatically create a connection configuration variable.
Configure the Basic Auth connection:
- Email: Enter the email address associated with the Confluence account (e.g.,
example.user@confluence.com) - API Token: Enter the API token generated from the Atlassian account management page, or for self-hosted instances, enter the account password
- Host: Enter the Confluence site URL (e.g.,
your-domain.atlassian.netfor Cloud or the server hostname for self-hosted instances)
For self-hosted Confluence instances, API tokens may not be available. Use the account password instead.
| Input | Notes | Example |
|---|---|---|
| API Token | Your Confluence API token for authentication. Generate this from your Atlassian account settings. | ATATT3xFfGF0X1234567890abcdefghij |
Your Confluence account email address used for authentication. | john.doe@example.com | |
| Host | Your Confluence site URL. Only enter your domain without the protocol. | your-domain.atlassian.net |
OAuth 2.0
key: oauth2To connect to Confluence using OAuth 2.0, create an OAuth 2.0 integration in the Atlassian Developer Console and configure the appropriate scopes.
For more information on developing Confluence applications, refer to the Confluence Security Overview.
Prerequisites
- An Atlassian account with access to the Developer Console
- Admin access to the Confluence site to be connected
Setup Steps
- Navigate to the Atlassian Developer Console and select Create to create a new OAuth 2.0 (3LO) integration
- Provide a name for the integration
- Under the Settings tab, locate the Client ID and Client Secret values - copy these for later use
- Navigate to the Authorization section and select Configure under OAuth 2.0 (3LO)
- Add
https://oauth2.prismatic.io/callbackas the Callback URL - Navigate to the Permissions section and configure the required scopes:
- Select the Confluence API tab
- Choose either Classic scopes or Granular scopes based on requirements
- Add the necessary scopes for the actions to be used (see scope recommendations below)
- Save the integration configuration
Configure the Connection
Add a Confluence action to the integration to automatically create a connection configuration variable.
Configure the OAuth 2.0 connection:
- Enter the Client ID and Client Secret obtained from the Atlassian Developer Console
- For Scopes, enter the space-separated list of scopes. The default scopes (Granular) provide access to most Confluence actions:
offline_access delete:attachment:confluence read:attachment:confluence write:attachment:confluence read:custom-content:confluence write:custom-content:confluence delete:custom-content:confluence read:page:confluence write:page:confluence delete:page:confluence read:space:confluence
- Refer to the Confluence Scopes Documentation for additional scope information
- (Optional) If connecting to a specific Confluence site when multiple sites are available, enter the site name or full URL in API Site Override (e.g.,
exampleorhttps://example.atlassian.net)
Ensure the scopes configured in the connection match the scopes granted in the Atlassian Developer Console. Mismatched scopes will result in authentication failures.
Save the integration to connect and authenticate to Confluence.
| Input | Notes | Example |
|---|---|---|
| API Site Override | By default this connector connects to the first Confluence site this user has access to. If you have multiple Confluence sites, specify which one you would like to connect to using the site name or the full URL. | example or https://example.atlassian.net |
| Authorize URL | The OAuth 2.0 Authorization URL for Confluence. | https://auth.atlassian.com/authorize?audience=api.atlassian.com&prompt=consent |
| Client ID | The OAuth 2.0 Client ID. Obtain this from your Atlassian Developer Console. | 1MDP9i8hFPTf2RcT6mdYchLgOyB9DO |
| Client Secret | The OAuth 2.0 Client Secret. Obtain this from your Atlassian Developer Console. | |
| Scopes | A space-delimited set of one or more scopes to get the user's permission to access. See Confluence OAuth 2.0 Scopes for details. | offline_access delete:attachment:confluence read:attachment:confluence write:attachment:confluence read:custom-content:confluence write:custom-content:confluence delete:custom-content:confluence read:page:confluence write:page:confluence delete:page:confluence read:space:confluence |
| Token URL | The OAuth 2.0 Token URL for Confluence. | https://auth.atlassian.com/oauth/token |
Triggers
New and Updated Pages
Retrieves existing and ongoing pages from Confluence. Load history once, check for changes on a schedule, or both. | key: pagesPollingTrigger
| Input | Notes | Example |
|---|---|---|
| Connection | The Confluence connection to use. | |
| Look-back Date | Optional ISO 8601 date used as the initial cursor on first deploy, allowing pre-existing records created or updated after this date to be included on the first poll. When omitted the first poll seeds the cursor to now and emits nothing. | 2026-01-01 |
Retrieves existing and ongoing pages from Confluence. Load history once, check for changes on a schedule, or both.
This trigger monitors Confluence pages for changes using the Confluence Cloud REST API v2 pages endpoint. Pages are categorized as either newly created or updated based on their timestamps.
How It Works
- Runs on the configured schedule (e.g., every 5 minutes)
- Queries the Confluence API for pages sorted by modification date (
sort=-modified-date) - Filters pages by their version
createdAttimestamp against the stored cursor - Categorizes pages as created or updated relative to the cursor
- Advances the cursor to the poll's start time and stores it as polling state
Initial sync
Providing a Look-back Date seeds an initial sync: on the first recurrence the cursor starts at that date instead of the current time, so pages created or updated on or after it are emitted. With no Look-back Date the first recurrence seeds the cursor to the current time and emits nothing. The trigger has no change-narrowing inputs, so the sync suppresses none of its configuration.
The look-back window has no fixed upper bound: the trigger requests every page and filters client-side, so a page modified while the sync is running is included. Once the sync completes the cursor advances to the poll's start time; the next recurrence resumes from exactly there, and no field in the payload marks the handoff. The sync drains in a single recurrence.
Page-size and field-selection behavior is unaffected by the initial sync.
Batching
Batching is enabled per flow on this trigger: each changed page is dispatched as its own execution, or grouped by the configured batch size. Batch size and batch concurrency can both be overridden per instance. Raising concurrency increases the request volume sent to Confluence. When batching is enabled, the trigger requests smaller pages from Confluence (50 instead of 100).
To turn it on, select the flow's trigger, open the Flow control tab, and switch on Enable Batching. Under Batch Size, keep Trigger default or choose Custom batch size. Batch Concurrency is optional; leave it blank for no batch-level limit.
With batching off, a downstream step reads pages from body.data.createdRecords and body.data.updatedRecords. With batching on those fields do not exist; each execution receives a single page record instead. Any step reading the older shape must be updated before batching is enabled. Batching is enabled per flow, so the change is scoped to that flow, not to the component or to other flows using this trigger.
Returned Data
The trigger returns pages categorized by change type:
Example Response
{
"data": {
"createdRecords": [
{
"id": "12345678",
"title": "API Integration Guide",
"createdAt": "2026-01-27T10:30:00.000Z",
"version": {
"createdAt": "2026-01-27T10:30:00.000Z",
"message": "Initial version",
"number": 1,
"minorEdit": false,
"authorId": "user123"
}
}
],
"updatedRecords": [
{
"id": "87654321",
"title": "Architecture Overview",
"createdAt": "2026-01-20T09:00:00.000Z",
"version": {
"createdAt": "2026-01-27T11:15:00.000Z",
"message": "Updated deployment section",
"number": 5,
"minorEdit": false,
"authorId": "user456"
}
}
]
}
}
Fields shown are representative. The full response object includes additional properties.
Example Payload for New and Updated Pages⤓
New Spaces
Retrieves existing and ongoing spaces from Confluence. Load history once, check for changes on a schedule, or both. | key: newSpacesPollingTrigger
| Input | Notes | Example |
|---|---|---|
| Connection | The Confluence connection to use. | |
| Look-back Date | Optional ISO 8601 date used as the initial cursor on first deploy, allowing pre-existing records created or updated after this date to be included on the first poll. When omitted the first poll seeds the cursor to now and emits nothing. | 2026-01-01 |
Retrieves existing and ongoing spaces from Confluence. Load history once, check for changes on a schedule, or both.
This trigger monitors the Confluence site for newly created spaces using the Confluence Cloud REST API v2 spaces endpoint.
How It Works
- Runs on the configured schedule (e.g., every 5 minutes)
- Queries the Confluence API to retrieve spaces accessible to the authenticated user
- Filters spaces by their
createdAttimestamp against the stored cursor - Emits only spaces created on or after the cursor
- Advances the cursor to the poll's start time and stores it as polling state
Initial sync
Providing a Look-back Date seeds an initial sync: on the first recurrence the cursor starts at that date instead of the current time, so spaces created on or after it are emitted. With no Look-back Date the first recurrence seeds the cursor to the current time and emits nothing. The trigger has no change-narrowing inputs, so the sync suppresses none of its configuration.
The look-back window has no fixed upper bound: the trigger requests every space and filters client-side, so a space created while the sync is running is included. Once the sync completes the cursor advances to the poll's start time; the next recurrence resumes from exactly there, and no field in the payload marks the handoff. The sync drains in a single recurrence.
Page-size and field-selection behavior is unaffected by the initial sync.
Batching
Batching is enabled per flow on this trigger: each new space is dispatched as its own execution, or grouped by the configured batch size. Batch size and batch concurrency can both be overridden per instance. Raising concurrency increases the request volume sent to Confluence. When batching is enabled, the trigger requests smaller pages from Confluence (50 instead of 100).
To turn it on, select the flow's trigger, open the Flow control tab, and switch on Enable Batching. Under Batch Size, keep Trigger default or choose Custom batch size. Batch Concurrency is optional; leave it blank for no batch-level limit.
With batching off, a downstream step reads the flat body.data array of spaces. With batching on that shape does not exist; each execution receives a single space record instead. Any step reading the older shape must be updated before batching is enabled. Batching is enabled per flow, so the change is scoped to that flow, not to the component or to other flows using this trigger.
Returned Data
The trigger returns newly created spaces with the following structure:
Example Response
{
"data": [
{
"id": "12345678",
"name": "Engineering Team Space",
"createdAt": "2026-01-27T10:30:00.000Z"
},
{
"id": "87654321",
"name": "Product Documentation",
"createdAt": "2026-01-27T11:15:00.000Z"
}
]
}
Fields shown are representative. The full response object includes additional properties.
Example Payload for New Spaces⤓
Data Sources
List Attachments
A picklist of attachments in the Confluence instance. | key: listAttachments | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection | The Confluence connection to use. |
Example Payload for List Attachments⤓
List Pages
Returns all pages. | key: listPages | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection | The Confluence connection to use. | |
| Space ID | The space ID to list pages from. | 123456789 |
List Spaces
Returns all spaces. | key: listSpaces | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection | The Confluence connection to use. | |
| Sort by Name | When true, sorts the spaces by name. | false |
Actions
Create Content Property for Attachment
Creates a new content property for an attachment. | key: createContentPropertyForAttachment
| Input | Notes | Example |
|---|---|---|
| Attachment ID | The unique identifier of the attachment. | att123456789 |
| Body Data | The content property data to create or update. | |
| Connection | The Confluence connection to use. |
Example Payload for Create Content Property for Attachment⤓
Create Content Property for Custom Content
Creates a new content property for a Custom Content. | key: createContentPropertyForCustomContent
| Input | Notes | Example |
|---|---|---|
| Body Data | The content property data to create or update. | |
| Connection | The Confluence connection to use. | |
| Custom Content ID | The unique identifier of the custom content. | 123456789 |
Example Payload for Create Content Property for Custom Content⤓
Create Content Property for Page
Creates a new content property for a page. | key: createContentPropertyForPage
| Input | Notes | Example |
|---|---|---|
| Body Data | The content property data to create or update. | |
| Connection | The Confluence connection to use. | |
| Page ID | The unique identifier of the page. | 123456789 |
Example Payload for Create Content Property for Page⤓
Create Page
Creates a page in the space. | key: createPage
| Input | Notes | Example |
|---|---|---|
| Body | The page body content, as a representation object (e.g. storage format). | |
| Connection | The Confluence connection to use. | |
| Embedded | When true, tags the content as embedded and creates content in NCS. | false |
| Parent ID | The unique identifier of the parent page. | 987654321 |
| Private | When true, the page will be private and only the user who creates the page will have permission to view and edit it. | false |
| Query Parameters | Query parameters to pass in to the request. For example, key | |
| Space ID | The unique identifier of the space. | 123456789 |
| Status | The status of the page. | |
| Title | The title of the page. | Product Documentation |
Example Payload for Create Page⤓
Delete Attachment
Deletes a specific attachment. | key: deleteAttachment
| Input | Notes | Example |
|---|---|---|
| Attachment ID | The unique identifier of the attachment. | att123456789 |
| Connection | The Confluence connection to use. | |
| Purge | When true, permanently deletes the attachment instead of moving it to trash. | false |
Example Payload for Delete Attachment⤓
Delete Content Property for a Custom Content
Deletes a content property for a Custom Content by its id. | key: deleteContentPropertyForCustomContent
| Input | Notes | Example |
|---|---|---|
| Connection | The Confluence connection to use. | |
| Custom Content ID | The unique identifier of the custom content. | 123456789 |
| Property ID | The unique identifier of the content property. | content-prop-123 |
Example Payload for Delete Content Property for a Custom Content⤓
Delete Content Property for an Attachment
Deletes a content property for an attachment by its id. | key: deleteContentPropertyForAttachment
| Input | Notes | Example |
|---|---|---|
| Attachment ID | The unique identifier of the attachment. | att123456789 |
| Connection | The Confluence connection to use. | |
| Property ID | The unique identifier of the content property. | content-prop-123 |
Example Payload for Delete Content Property for an Attachment⤓
Delete Content Property for Page
Deletes a content property for a page by its id. | key: deleteContentPropertyForPage
| Input | Notes | Example |
|---|---|---|
| Connection | The Confluence connection to use. | |
| Page ID | The unique identifier of the page. | 123456789 |
| Property ID | The unique identifier of the content property. | content-prop-123 |
Example Payload for Delete Content Property for Page⤓
Delete Page
Delete a page by id. | key: deletePage
| Input | Notes | Example |
|---|---|---|
| Connection | The Confluence connection to use. | |
| Draft | When true, deletes a page that is in draft status. | false |
| Page ID | The unique identifier of the page. | 123456789 |
| Purge | When true, permanently deletes the page instead of moving it to trash. | false |
Example Payload for Delete Page⤓
Get Attachment
Returns a specific attachment. | key: getAttachment
| Input | Notes | Example |
|---|---|---|
| Attachment ID | The unique identifier of the attachment. | att123456789 |
| Connection | The Confluence connection to use. | |
| Query Parameters | Query parameters to pass in to the request. For example, key |
Example Payload for Get Attachment⤓
Get Attachments for Page
Returns the attachments of a specific page. | key: getPageAttachment
| Input | Notes | Example |
|---|---|---|
| Connection | The Confluence connection to use. | |
| Page ID | The unique identifier of the page. | 123456789 |
| Pagination | Cursor and page-size controls for paging through results. | |
| Query Parameters | Query parameters to pass in to the request. For example, key |
Example Payload for Get Attachments for Page⤓
Get Content Properties for Custom Content
Retrieves a specific Content Property by ID that is attached to a specified custom content. | key: getContentPropertiesForCustomContent
| Input | Notes | Example |
|---|---|---|
| Connection | The Confluence connection to use. | |
| Custom Content ID | The unique identifier of the custom content. | 123456789 |
| Property ID | The unique identifier of the content property. | content-prop-123 |
Example Payload for Get Content Properties for Custom Content⤓
Get Content Property for Attachment
Retrieves a specific Content Property by ID that is attached to a specified attachment. | key: getContentPropertiesForAttachments
| Input | Notes | Example |
|---|---|---|
| Attachment ID | The unique identifier of the attachment. | att123456789 |
| Connection | The Confluence connection to use. | |
| Property ID | The unique identifier of the content property. | content-prop-123 |
Example Payload for Get Content Property for Attachment⤓
Get Content Property for Page
Retrieves a specific Content Property by ID that is attached to a specified page. | key: getContentPropertiesForPage
| Input | Notes | Example |
|---|---|---|
| Connection | The Confluence connection to use. | |
| Page ID | The unique identifier of the page. | 123456789 |
| Property ID | The unique identifier of the content property. | content-prop-123 |
Example Payload for Get Content Property for Page⤓
Get Page
Returns a specific Page. | key: getPage
| Input | Notes | Example |
|---|---|---|
| Additional Fields | Additional optional fields: includes Body Format, Get Draft, Version, Include Labels, Include Properties, Include Operations, Include Likes, Include Versions, Include Version, and Include Favorited By Current User Status. | |
| Connection | The Confluence connection to use. | |
| Page ID | The unique identifier of the page. | 123456789 |
Example Payload for Get Page⤓
Get Space
Returns a specific space. | key: getSpace
| Input | Notes | Example |
|---|---|---|
| Connection | The Confluence connection to use. | |
| Query Parameters | Query parameters to pass in to the request. For example, key | |
| Space ID | The unique identifier of the space. | 123456789 |
Example Payload for Get Space⤓
List Attachments
Returns all attachments. | key: listAttachments
| Input | Notes | Example |
|---|---|---|
| Connection | The Confluence connection to use. | |
| Fetch All | When true, automatically fetches all pages of results. When false, returns a single page. | false |
| Pagination | Cursor and page-size controls for paging through results. | |
| Query Parameters | Query parameters to pass in to the request. For example, key |
Example Payload for List Attachments⤓
List Content Properties for Attachments
Retrieves all Content Properties tied to a specified attachment. | key: listContentPropertiesForAttachments
| Input | Notes | Example |
|---|---|---|
| Attachment ID | The unique identifier of the attachment. | att123456789 |
| Connection | The Confluence connection to use. | |
| Fetch All | When true, automatically fetches all pages of results. When false, returns a single page. | false |
| Pagination | Cursor and page-size controls for paging through results. | |
| Query Parameters | Query parameters to pass in to the request. For example, key | |
| Sort | Used to sort the result by a particular field. |
Example Payload for List Content Properties for Attachments⤓
List Content Properties for Custom Content
Retrieves Content Properties tied to a specified Custom Content. | key: listContentPropertiesForCustomContent
| Input | Notes | Example |
|---|---|---|
| Connection | The Confluence connection to use. | |
| Custom Content ID | The unique identifier of the custom content. | 123456789 |
| Fetch All | When true, automatically fetches all pages of results. When false, returns a single page. | false |
| Pagination | Cursor and page-size controls for paging through results. | |
| Query Parameters | Query parameters to pass in to the request. For example, key | |
| Sort | Used to sort the result by a particular field. |
Example Payload for List Content Properties for Custom Content⤓
List Content Properties for Page
Retrieves Content Properties tied to a specified page. | key: listContentPropertiesForPage
| Input | Notes | Example |
|---|---|---|
| Connection | The Confluence connection to use. | |
| Fetch All | When true, automatically fetches all pages of results. When false, returns a single page. | false |
| Page ID | The unique identifier of the page. | 123456789 |
| Pagination | Cursor and page-size controls for paging through results. | |
| Query Parameters | Query parameters to pass in to the request. For example, key | |
| Sort | Used to sort the result by a particular field. |
Example Payload for List Content Properties for Page⤓
List Pages
Returns all pages. | key: listPages
| Input | Notes | Example |
|---|---|---|
| Body Format | The content format types to be returned in the body field of the response. | |
| Connection | The Confluence connection to use. | |
| Fetch All | When true, automatically fetches all pages of results. When false, returns a single page. | false |
| Page IDs | Filter the results based on page IDs. Multiple page IDs can be specified as a comma-separated list. | 123456789,987654321 |
| Pagination | Cursor and page-size controls for paging through results. | |
| Sort | Used to sort the result by a particular field. | |
| Space IDs | Filter the results based on space IDs. Multiple space IDs can be specified as a comma-separated list. | 123456789,987654321 |
| Status | Filter the results to pages based on their status. By default, current and archived are used. Valid values: current, archived, deleted, trashed | current,archived |
| Title | Filter the results to pages based on their title. | Product Documentation |
Example Payload for List Pages⤓
List Pages in Space
Returns all pages in a space. | key: listPagesInSpace
| Input | Notes | Example |
|---|---|---|
| Body Format | The content format types to be returned in the body field of the response. | |
| Connection | The Confluence connection to use. | |
| Depth | Filter the results to pages at the root level of the space or to all pages in the space. | |
| Fetch All | When true, automatically fetches all pages of results. When false, returns a single page. | false |
| Pagination | Cursor and page-size controls for paging through results. | |
| Sort | Used to sort the result by a particular field. | |
| Space ID | The unique identifier of the space. | 123456789 |
| Status | The status of the page. | |
| Title | Filter the results to pages based on their title. | Product Documentation |
Example Payload for List Pages in Space⤓
List Spaces
Returns all spaces. | key: listSpaces
| Input | Notes | Example |
|---|---|---|
| Connection | The Confluence connection to use. | |
| Fetch All | When true, automatically fetches all pages of results. When false, returns a single page. | false |
| Pagination | Cursor and page-size controls for paging through results. | |
| Query Parameters | Query parameters to pass in to the request. For example, key |
Example Payload for List Spaces⤓
Raw GraphQL Request
Send raw GraphQL request to Confluence. | key: graphqlRequest
| Input | Notes | Example |
|---|---|---|
| Connection | The Confluence connection to use. | |
| Headers | Custom headers to send along with the request. | |
| Query or Mutation | ||
| Variables | Variables to pass in to the query or mutation. |
Raw Request
Send raw HTTP request to Confluence. | key: rawRequest
| Input | Notes | Example |
|---|---|---|
| Connection | The Confluence connection to use. | |
| Data | The HTTP body payload to send to the URL. | {"exampleKey": "Example Data"} |
| File Data | File Data to be sent as a multipart form upload. | [{key: "example.txt", value: "My File Contents"}] |
| File Data File Names | File names to apply to the file data inputs. Keys must match the file data keys above. | |
| Form Data | The Form Data to be sent as a multipart form upload. | [{"key": "Example Key", "value": new Buffer("Hello World")}] |
| Header | A list of headers to send with the request. | User-Agent: curl/7.64.1 |
| Max Retry Count | The maximum number of retries to attempt. Specify 0 for no retries. | 0 |
| Method | The HTTP method to use. | |
| Query Parameter | A list of query parameters to send with the request. This is the portion at the end of the URL similar to ?key1=value1&key2=value2. | |
| Response Type | The type of data you expect in the response. You can request json, text, or binary data. | json |
| Retry On All Errors | If true, retries on all erroneous responses regardless of type. This is helpful when retrying after HTTP 429 or other 3xx or 4xx errors. Otherwise, only retries on HTTP 5xx and network errors. | false |
| Retry Delay (ms) | The delay in milliseconds between retries. This is used when 'Use Exponential Backoff' is disabled. | 0 |
| Timeout | The maximum time that a client will await a response to its request | 2000 |
| URL | Input the path only (/wiki/api/v2/attachments/attachments), The base URL is already included (https://{your-domain}). For example, to connect to https://{your-domain}/wiki/api/v2/attachments, only /wiki/api/v2/attachments/attachments is entered in this field. | /wiki/api/v2/attachments/attachments |
| Use Exponential Backoff | Specifies whether to use a pre-defined exponential backoff strategy for retries. When enabled, 'Retry Delay (ms)' is ignored. | false |
Update Content Property for Attachment
Update a content property for attachment by its id. | key: updateContentPropertyForAttachment
| Input | Notes | Example |
|---|---|---|
| Attachment ID | The unique identifier of the attachment. | att123456789 |
| Body Data | The content property data to create or update. | |
| Connection | The Confluence connection to use. | |
| Property ID | The unique identifier of the content property. | content-prop-123 |
Example Payload for Update Content Property for Attachment⤓
Update Content Property for Custom Content
Update a content property for a Custom Content by its id. | key: updateContentPropertyForCustomContent
| Input | Notes | Example |
|---|---|---|
| Body Data | The content property data to create or update. | |
| Connection | The Confluence connection to use. | |
| Custom Content ID | The unique identifier of the custom content. | 123456789 |
| Property ID | The unique identifier of the content property. | content-prop-123 |
Example Payload for Update Content Property for Custom Content⤓
Update Content Property for Page
Update a content property for a page by its id. | key: updateContentPropertyForPage
| Input | Notes | Example |
|---|---|---|
| Body Data | The content property data to create or update. | |
| Connection | The Confluence connection to use. | |
| Page ID | The unique identifier of the page. | 123456789 |
| Property ID | The unique identifier of the content property. | content-prop-123 |
Example Payload for Update Content Property for Page⤓
Update Page
Update a page by id. | key: updatePage
| Input | Notes | Example |
|---|---|---|
| Body | The page body content, as a representation object (e.g. storage format). | |
| Connection | The Confluence connection to use. | |
| Page ID | The unique identifier of the page. | 123456789 |
| Parent ID | The unique identifier of the parent page. | 987654321 |
| Space ID | The unique identifier of the space. | 123456789 |
| Status | The status of the page. | |
| Title | The title of the page. | Product Documentation |
| Version | The page version object, including the new version number and an optional change message. |
Example Payload for Update Page⤓
Changelog
2026-09-30
- Grouped the pagination inputs on the List Pages, List Pages in Space, List Spaces, List Attachments, Get Attachments for Page, List Content Properties for Page, List Content Properties for Attachments, and List Content Properties for Custom Content actions into a Pagination object, and grouped the optional retrieval and expansion inputs on the Get Page action into an Additional Fields object
- Added inline action calling support to 31 actions for improved example output during configuration
- Added output schemas to 22 actions for improved field mapping during configuration
- Added opt-in batching to the New and Updated Pages and New Spaces triggers, dispatching each changed record individually or in configured batches so large backlogs drain in one poll cycle; enabling it changes the shape a downstream step receives
- Added an optional Look-back Date input for performing an initial sync of records on the New and Updated Pages and New Spaces triggers. The initial sync backfills every record modified on or after the specified date, seeding each once; later recurrences are unaffected. Leave it empty to start from the first recurrence with no backfill
2026-04-30
Updated spectral version
2026-03-31
Various modernizations and documentation updates
2026-02-26
Added inline data source for attachments to enable dynamic dropdown selection
2026-01-27
Added polling triggers for monitoring Confluence content:
- New Spaces - Polling trigger that checks for new spaces on a configured schedule
- New and Updated Pages - Polling trigger that monitors pages for new and updated content on a configured schedule, categorizing changes by type