Genesys Cloud
Deprecation: Webhooks
| Announced on | Effective date | Aha! idea |
|---|---|---|
| 2021-02-17 | 2021-05-19 | - |
On May 19, 2021, Genesys removed the “webhooks” action type. Genesys Architect is more powerful than webhooks and easier to configure. The “Architect flows” action can trigger all use cases possible through webhooks and centralize webhook processing to the one action type.
What does this mean?
Any current webhook APIs from Genesys Predictive Engagement no longer work.
Am I affected?
If your organization created action maps that use the “webhooks” action to send a webhook from Genesys Predictive Engagement to a third-party system, this deprecation affects you.
How can I prepare for this deprecation?
To migrate from webhook actions to Architect flow actions:
- Ensure that you have the appropriate Architect flow permissions in Genesys Cloud CX, including Architect > UI > View for accessing Architect.
- In Genesys Cloud CX Architect, create and publish your workflows.
- In Genesys Predictive Engagement, edit your existing action maps that use the webhooks action and change the action type to Architect flows. Then, override the default variables with visitor-specific data.
What if I need help or have questions?
Contact My Support.
