What is it?
Customers can now trigger Conversational Processes (CPs) via Compound Actions (CAs) without publishing them as standalone conversational plugins.
Why we built it?
Previously, customers building Ambient Agents had to publish CPs as “dummy” plugins with random triggering examples just so system-triggered flows could invoke them in a CA. This was confusing, error-prone, and in some cases caused incorrect plugin routing in user conversations.
How it works?
- A Conversational Process can now be published for system-triggered execution only and the webhook → plugin → CA → CP flows now reliably work!
- No need for the old “dummy CP plugin with random blabber” workaround.
Key dates:
- Preview: January 2026