Reusable workflows join channel context, governed MCP tools and visible approval steps. The channel changes; the capability contract does not.
Chains Jira issues and Confluence documentation into one combined status view with source attribution.
"project status", "blockers", "standup"Connect a Confluence decision to Jira delivery state and prepare a controlled action.
"decision", "link decision"Full analysis of an issue: details, linked issues, comments, and related Confluence pages in one view.
"investigate NAS-123", "deep dive", "everything about"Say 'tell me more' and the gateway remembers the last issue from your conversation history.
"tell me more", "expand on that"Try these prompts through any connected channel to invoke the live gateway workflows.
“Give me the project status and current blockers for the launch.”
Open Jira work and related Confluence context are combined into a source-linked status with suggested next actions.
“Find the latest launch decision and link it to the related Jira work.”
The gateway connects the decision to delivery state and prepares any write action for approval.
“Investigate NAS-123 and show me everything related to it.”
Issue details, links, comments and relevant Confluence pages are assembled into one investigation.
“Tell me more about that issue.”
Conversation memory resolves the previous issue and returns fresh details without asking for the key again.
Invoke MCPoppins in a launch thread where a blocker and decision already exist.
Show Confluence decision and linked Jira issue with citations and conflict handling.
Generate an OpenUI approval card for the exact Jira comment—no write yet.
Ask the same workflow in Teams to prove the governed core is portable.