Is it possible to bypass OAuth scope validation for Architect flow triggers from AppFoundry?

Architect & Flows
1

Is it possible to bypass the strict OAuth scope validation when invoking an Architect flow via the platform API from our AppFoundry integration? We are hitting a 403 Forbidden error despite the client having the flows:write scope, suggesting a hidden permission layer for external triggers.

Environment details:

  • AppFoundry Premium App v2.1.0
  • Node.js SDK 2.4.1
  • Operation: Triggering a flow execution via the platform API
  • Error: 403 Forbidden (insufficient permissions for external invocation)
2

It depends, but generally…

  1. Check client ID permissions in Admin > OAuth.
  2. Ensure architect:flow:trigger is added. flows:write is insufficient for execution.
  3. Rotate credentials to apply scope changes.

The 403 indicates missing execution rights, not just write access.

3 Likes