Hi Juliano,
For us, it is usually a combination of both.
We try to keep as much business logic as possible within Architect because it is easier to maintain, troubleshoot, and hand over to other administrators.
However, when we need to integrate with external systems, perform complex lookups, or orchestrate multiple API calls, we typically use Data Actions (and occasionally Functions when additional processing is required).
A good example is our ITSM integrations, where Architect handles the call flow and decision making, while Data Actions/APIs are used to retrieve and update information in external platforms.
My general preference is to keep the orchestration in Architect and only move logic outside Genesys Cloud when there is a clear requirement that cannot be handled natively.
------------------------------
Phaneendra
Technical Solutions Consultant
------------------------------
Original Message:
Sent: 05-29-2026 16:52
From: Juliano Fernandes Mendes Pimentel De Paiva
Subject: Data Actions vs Native Logic
For orchestration projects, do you rely more on Data Actions/API integrations or native Architect logic?
I'm curious how different teams balance external integrations versus keeping everything inside Genesys Cloud.
Thank you in advance.
#General
------------------------------
Juliano Fernandes Mendes Pimentel De Paiva
Genesys Analyst
------------------------------