What changed
Architect workflows can now be started by external events from systems outside Genesys Cloud. Administrators configure a trigger that checks incoming external events against defined conditions and timing criteria and invokes a selected workflow when they are met. The workflow receives the event data in the format configured on the trigger and can do anything Architect supports, such as enriching customer profiles or calling custom data actions.
Vendor documentation (opens in a new tab)Why it matters
This turns external activity, such as an order update, a booking change or a CRM event, into automation inside Genesys Cloud without a middleware layer for each downstream step. It also means a noisy or badly filtered event source can start a lot of workflows, so trigger conditions and data action limits deserve the same design attention as flows.
CxCave practical context
Who should care
- Architects
- Developers
- Administrators
Implementation considerations
REVIEWList the external systems whose events currently reach Genesys Cloud through custom middleware, pick one low-risk use case to move onto a trigger, and set tight conditions and timing criteria before enabling it. Watch workflow and data action volume after go-live.
CxCave recommendation, not a vendor mandate unless explicitly stated.
