How it works
Use the latest revision and an Idempotency-Key. Member changes take effect on the next permission check, including gates already waiting. Removing a member does not undo an earlier decision. Group IDs and published flow definitions stay fixed. Integration keys cannot administer approval permissions. needsMemberReview signals a pre-existing assignment: saving replaces it with exactly the selected people.
Request body
namestringrequiredmin length 1 · max length 80accessScopestringoptionalmin length 1 · max length 60 · default "general"memberIdsarrayoptionalmax items 1000 · default []revisionintegerrequiredmin 1 · max 9007199254740991Request essentials
- Authorization
- Bearer $FLOWG8_ACCESS_TOKEN
- X-Organization-Id
- Your workspace UUID
- Idempotency-Key
- Stable per operation; 8–128 characters

