Skip to content
Flowdence Flowdence Docs

Build a Boomi Operations Runbook

Use this tutorial when a team wants one Confluence page that explains a Boomi integration and its operational posture.

Outcome

Section titled “Outcome”

The page gives readers enough Boomi context to inspect process health, deployment state, runtime/API dependencies, connector blast radius, and release-window changes without leaving the runbook for every question.

Where To Open

Section titled “Where To Open”

Open or create the Confluence runbook page, then insert BoomiSight macros from the editor.

Guided Flow

Section titled “Guided Flow”
  1. Add an Integration Landscape Summary near the top of the page for portfolio-level context.

Boomi architecture page with BoomiSight context

  1. Confirm the summary macro renders current space metrics before readers use the page for release review.

Integration Landscape Summary macro

  1. Add a Process Snapshot for the primary process.
  2. Configure the Process Snapshot from the editor. Prefer resource search and picker selection when the cache is current; use manual fallback only when the resource is known and search is unavailable.

Detailed Process Snapshot macro

  1. Add Atom Health for the runtime that matters to the runbook.

Atom Health macros

  1. Add Environment Summary when the page needs environment classification or attached runtime context.

Environment Summary macros

  1. Add API Snapshot when the integration exposes a Boomi API service.

API Snapshot macros

  1. Add Process Deployment History to show release and deployment chronology.
  2. Add Process Executions when recent process runs matter to support or incident response.

Process Deployment History and Process Executions macros

  1. Add Process Blast Radius before documenting a risky connector or credential change.

Process Blast Radius macro

  1. Add Release Notes for the relevant UTC date window when the runbook supports a release review.

Release Notes macro

Success Checklist

Section titled “Success Checklist”
  • Each macro has a clear reader-facing purpose.
  • The page uses detailed macros for primary evidence and compact/inline macros for dense status signals.
  • Every configured macro points to the intended Boomi resource or date window.
  • Empty states are explained as data state, permission state, or an intentional filter.
  • The page avoids exposing Boomi API tokens or admin-only credentials.

Video

Section titled “Video”

This walkthrough is a live Confluence browser recording of the runbook page. Deployment account columns are visually redacted for public documentation.

Download video: Runbook macro walkthrough