Calling shared flow from Architect inbound flow failing with 404

Architect & Flows
1

Hey folks,

I’m trying to reuse a common module for WFM adherence checks across multiple inbound call flows in Genesys Cloud Architect. The shared flow is published and visible, but when I trigger it via a Data Action, I get a 404.

Here’s the JSON payload I’m using in the Data Action:

{
 "type": "flow",
 "flowId": "abc-123-def",
 "inputs": {
 "agentId": "{{conversation.participant.id}}"
 }
}
  • Genesys Cloud US1
  • Shared flow status: Published
  • Inbound flow: Active
  • Data Action: Call Flow

It’s weird because the flow ID is definitely correct. Any ideas?

2

The 404 usually isn’t about the ID being wrong, it’s about visibility. Shared flows are scoped to specific organizations or groups, and just because you can see it in the UI doesn’t mean the runtime engine has permission to execute it from that specific inbound flow’s context.

Check if the shared flow is actually published to the same environment where your inbound flow is running. It’s a common gotcha. Also, verify the flowId matches the internal ID, not the external one if you’re using CX as Code.

If you’re managing this via Terraform, make sure the genesyscloud_flow resource for the shared flow has the correct routing_settings and is explicitly marked as published. Sometimes the state file gets out of sync with the actual API state.

resource "genesyscloud_flow" "shared_wfm_check" {
 name = "WFM Adherence Check"
 enabled = true
 published = true # Critical for runtime access
 
 flow_type = "shared"
 
 # Ensure proper organization or group scoping if applicable
}

Double-check the publish status in the Architect UI. If it says “Draft” or “Unpublished”, the runtime will throw a 404 regardless of your JSON payload.