Hi Roberto,
If the feature is already enabled in Beta/LA for your org and the integration was installed successfully, then the most likely cause is that the Digital Bot Connector integration is not fully configured/activated yet.
In Genesys Cloud, the Call Digital Bot Connector action only appears in Architect after:
- the feature is enabled for the org
- the integration is properly configured
- and the integration status is Active/ready
Since you are testing in an Inbound Message Flow (which is the correct flow type), and only the legacy block appears, I would verify:
- Integration configuration completed
- Connector authentication/settings saved correctly
- Integration status = Active
- User re-login after setup
Usually when the action is missing but the feature is already available in the org, it points to incomplete connector configuration rather than an Architect issue.
------------------------------
Gabriel Garcia
NA
------------------------------
Original Message:
Sent: 05-07-2026 09:08
From: Roberto Rahamut
Subject: Issues with Genesys Digital Bot Connector for Inbound Message Flow
Hi.
We have some issues with the Genesys Digital Bot Connector which was activated today for this ORG as a LA (limited access) approach.
First and foremost, in Architect there is no block for Call Digital Bot Connector, only the legacy is available.
I checked the documentation and the permissions and prereqs indicated on
https://help.genesys.cloud/articles/call-digital-bot-connector-action/
I tried to use the one I setup in Architect with an Inbound Message Flow.
Regards,
Robert R.
#Unsure/Other
------------------------------
Roberto Rahamut
Project Manager
------------------------------