Description

Retrieve the content of a Confluence page by its URL. This action fetches the page content in HTML format along with any attachments, making it ideal for accessing runbooks and documentation during incident response.

During an incident, responders need quick access to runbooks, investigation procedures, and remediation steps. This action automatically retrieves relevant Confluence documentation and makes it available directly within your incident workflow. By pulling runbooks into the incident timeline, you can:

Accelerate triage and investigation by providing responders immediate access to documented procedures
Ensure consistency in incident response by following established runbooks
Reduce context switching by keeping documentation accessible without leaving PagerDuty
Guide remediation efforts with step-by-step instructions from your team's knowledge base
Onboard new responders faster by automatically surfacing relevant documentation

Common scenarios include retrieving service-specific runbooks when a particular service triggers an incident, pulling troubleshooting guides based on alert types, or accessing escalation procedures for high-severity incidents.

Inputs

Name	Description
Connection Input	Select a Confluence integration that has been configured in your PagerDuty account. This connection must have access to the Confluence instance containing the page you want to retrieve.
Page URL {+}	The full URL of the Confluence page to retrieve. This must be a valid HTTPS URL (e.g., https://yourcompany.atlassian.net/wiki/spaces/OPS/pages/123456/Incident+Runbook). The page must be accessible via the provided connection. You can use Field References to dynamically select pages based on incident properties.
Body Format	The format in which to retrieve the page content. Default: `export_view` Options: `storage` - Confluence storage format (raw markup) `atlas_doc_format` - Atlas document format `view` - View format (HTML) `export_view` - Export view format (HTML, recommended for most use cases) `anonymous_export_view` - Anonymous export view `styled_view` - Styled view with CSS `editor` - Editor format

Outputs

Name	Description
Page Content	The content of the Confluence page in HTML format. Reference this field in subsequent actions such as "Add Note to Incident" or "Send Slack Message" to share the runbook content with your team. The format returned depends on the Body Format input selected.
Attachments	A JSON object containing all page attachments with their base64 encoded content. Each attachment includes the title, media type, and encoded content, allowing you to process or reference attached files programmatically.
Result	Value that shows if the action was successful or not. Either "Success" or "Failed."
Result Summary	Brief description of what the action did or if it failed.
Error	Brief description that is populated if the action failed. Common errors include invalid URLs, inaccessible pages, or authentication issues with the Confluence connection.

📘
Tips

URL Format: Ensure your Confluence page URLs are complete and start with https://. The action extracts the page ID from the URL path automatically.

Connection Permissions: Verify that your Confluence integration has read access to the pages you want to retrieve. The connection must have appropriate permissions for the Confluence space containing the page.

Combining with Other Actions: Use the Page Content output with subsequent actions like "Add Note to Incident" to automatically post runbook content to the incident timeline, or "Send Slack Message" to share procedures with your response team.

Dynamic Page Selection: Use Field References in the Page URL input to dynamically select runbooks based on incident properties, such as service name or urgency.