xsoar-workflow-documentation

To generate Confluence-ready documentation for XSOAR playbooks, you need to provide a manifest containing the root playbook and its dependencies. The tool then automates the creation of a linked, deterministic document set with cross-referenced pages.

XSOAR playbook dependency documentation includes runbook-style pages for root playbooks, sub-playbooks, automations, and integrations. It also generates a glossary-linked index with cross-references to the Cortex XSOAR Playbook Design Guide for varying reader familiarity levels.

Yes, you need a manifest specifying the root playbook and its dependencies to document XSOAR playbook trees. This manifest drives the deterministic output structure, ensuring all sub-playbooks, automations, and integrations are accurately cross-referenced.

Yes, you can automate runbook creation for XSOAR automations and integrations. The generator processes the dependency tree from the provided manifest and outputs consistent, cross-referenced documentation pages for each component.

The best way to document an XSOAR automation dependency tree is to use an automated generator that applies a manifest of root and dependent components. This produces a consistent folder structure of linked, runbook-style pages and a glossary index.

XSOAR playbook documentation lacks cross-referenced links if it is not generated using a dependency manifest. Providing the manifest allows the generator to map the dependency tree and produce a defined folder structure with deterministic cross-links.