Architect Data Action: Invoking Common Module Flow via REST Proxy

Architect & Flows
1

Quick question about invoking a shared Common Module flow from multiple inbound call flows using the Architect Data Action API.

Background

I need to trigger a reusable logic flow (UUID: a1b2c3d4-e5f6-7890-abcd-ef1234567890) from various inbound IVR scripts without duplicating the routing logic. I am attempting to use a Data Action to make a synchronous HTTP POST to the flow execution endpoint.

Issue

The request returns a 401 Unauthorized error despite using a valid OAuth token with architect:flows:execute scope. The payload structure seems correct, but the response indicates the flow UUID is not recognized in this context.

{
 "method": "POST",
 "endpoint": "https://api.mypurecloud.com/api/v2/architect/flows/a1b2c3d4-e5f6-7890-abcd-ef1234567890/execute",
 "headers": {
 "Authorization": "Bearer {{oauthToken}}",
 "Content-Type": "application/json"
 },
 "body": {
 "conversationId": "{{conversationId}}",
 "inputData": {
 "callerId": "{{callerId}}"
 }
 }
}

Troubleshooting

  • Verified the token has the correct scope via the token introspection endpoint.
  • Confirmed the flow UUID exists and is published in the Architect environment.
  • Tested the same UUID via Postman with the same token, which worked successfully.

Is there a specific limitation on invoking Common Module flows via the REST API from within a Data Action, or is the endpoint path incorrect for shared flows?