Confluence Cloud Trigger icon

Confluence Cloud Trigger

Poll for new/updated Confluence content

Overview

This node is a trigger for Confluence Cloud that polls for new or updated content based on user-defined criteria. It allows monitoring of Confluence pages by either selecting predefined templates (such as new pages, updated pages, or both) or by writing custom Confluence Query Language (CQL) expressions. This trigger is useful for automating workflows that depend on changes in Confluence content, such as notifying teams about document updates, syncing content with other systems, or triggering reviews.

Practical examples:

  • Automatically notify a Slack channel when new pages are created in specific Confluence spaces.
  • Trigger an approval workflow when pages labeled "urgent" are updated.
  • Sync recently modified documentation pages to an external knowledge base.

Properties

Name Meaning
Query Type How to define what content to monitor. Options: Templates (use predefined filters), Custom CQL (write your own Confluence Query Language expression).
Template (Shown if Query Type = Templates) What type of content changes to monitor. Options: New Pages, Updated Pages, New or Updated Pages.
Space Keys (Optional) (Shown if Query Type = Templates) Comma-separated list of space keys to monitor (e.g., DOCS, TEAM). Leave empty to monitor all spaces.
Labels (Optional) (Shown if Query Type = Templates) Comma-separated list of labels to filter by (e.g., urgent, review). Leave empty to include all labels.
Author (Optional) (Shown if Query Type = Templates) Confluence Account ID of the author to filter by. Leave empty to include all authors.
Initial Lookback (Shown if Query Type = Templates) How far back to look for content on the first run. Options range from 1 hour to 1 month.
CQL Query (Shown if Query Type = Custom CQL) Write your own Confluence Query Language expression to define which content to monitor.
Additional Options Collection of extra settings:
Result Limit: Maximum number of results per poll (1–250, default 50).
Include Drafts: Whether to include draft pages.
Reset Trigger State: Reset state to re-trigger all matching content.

Output

The node outputs an array of items where each item represents a Confluence page matching the query. Each item's json property contains:

  • id: The unique identifier of the page.
  • title: The title of the page.
  • type: The content type (always "page" for filtered results).
  • status: The status of the page (e.g., current, draft).
  • space: An object with details about the space containing the page:
    • key: Space key.
    • name: Space name.
    • id: Space ID.
  • version: Version information of the page.
  • links: Links related to the page:
    • webui: URL to view the page in the web UI.
    • self: API URL for the page.
  • pollTime: ISO timestamp of when the poll was performed.
  • triggerEvent: Indicates the event type that triggered this result, e.g., "created", "updated", "created_or_updated", or "custom_cql".

The node does not output binary data.

Dependencies

  • Requires an API authentication credential for Confluence Cloud with appropriate permissions to read content.
  • The node makes REST API calls to the Confluence Cloud content search endpoint.
  • No additional environment variables or configurations are required beyond the API credential.

Troubleshooting

  • Common issues:
    • Invalid or expired API credentials will cause authentication failures.
    • Incorrect CQL syntax in the custom query option will result in API errors.
    • Overly broad queries may return large result sets, potentially causing performance issues or hitting API limits.
  • Error messages:
    • "Confluence API request failed: <error message>" indicates a problem with the API call. Check network connectivity, API credentials, and query correctness.
    • Parsing errors or empty results might indicate malformed CQL or no matching content.
  • Resolutions:
    • Verify and update the API credential.
    • Test CQL queries directly in Confluence's query interface before using them in the node.
    • Use the "Result Limit" option to control the number of returned items.
    • Use the "Reset Trigger State" option to clear stored state if the trigger stops detecting changes.

Links and References

Discussion