Marketing Campaign Approval & Launch
A campaign is ready to go, but launching it still means pinging a manager for sign-off, flipping it live, and remembering to tell the team — a small chain, but one that stalls campaigns for hours over a single missing approval.
The Goal
What you'd actually type to Dendr AI
Natural-language input
“Launch the Q3 upsell campaign for existing customers once approved.”
The Ecosystem
Agents & MCP servers orchestrated
Marketing automation
Adobe Experience Cloud
Illustrative vendor
Holds and launches the campaign.
Collaboration
Slack
Illustrative vendor
Routes the campaign for manager approval.
Communication
Graph / SMTP MCP
Notifies the marketing team once live.
How It Works
How the Dynamic Planner builds the chain
The Intent Engine structures the goal above into an intent graph. The Dynamic Planner grounds each step against the live Agent Capability Graph and assembles the coordination path at request time — no one pre-authored this exact sequence.
Submit the campaign for approval, routed to the marketing manager in Slack.
On approval, launch the campaign in Adobe Experience Cloud.
Email the marketing team confirming the campaign is live, with the launch timestamp.
Semantic Routing in Action
The right agent, every time
campaign.launch exact-matches Adobe Experience Cloud as the only registered marketing-automation agent with launch permissions — no semantic ambiguity.
collaboration.approve matches Slack directly — the same capability tag used for access requests, showing how one registered capability gets reused across very different business processes.
Approve Once. Use Anytime.
Chain-level authorization, reused on every run
- Marketing leadership approves the “campaign launch” pattern once, covering approval routing and launch as a single authorized chain.
- Every future campaign that follows the same review process launches under that same standing authorization the moment a manager approves it in Slack — no separate platform-access request per campaign.
- Intentionally one of the simplest chains in the set — a good “first five minutes” example for visitors who aren't yet ready for the high-complexity use cases.
Dynamic Replanning & Resilience
What happens when reality doesn't match the happy path
If the manager rejects the campaign in Slack, the planner ends the chain there and notifies the submitter — Adobe Experience Cloud is never invoked on a rejected campaign.
Business Outcome
What the marketing team gets
Campaigns launch within minutes of approval instead of waiting on someone to remember to flip them live.
A clear, simple record of who approved each campaign and when it went live.
Demonstrates that Dendr AI scales down to simple, everyday approvals just as well as it scales up to complex chains.
Related
More Cross-Industry use cases
See how marketing teams launch faster with Dendr AI.
Get a demo and see the campaign-launch chain run against your own registered agents.
Adobe Experience Cloud and Slack are referenced above as illustrative, recognizable examples of the enterprise systems Dendr AI can orchestrate through A2A, MCP, vendor adapters, or OpenAPI manifests. These are reference architectures, not case studies of named customers, and do not imply a partnership, integration certification, or endorsement by those vendors.