Fix ServiceNow action argument names and document allowed-domains scope - #428
Merged
Conversation
![c1-dev-bot[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
…omains scope The enable_user and disable_user connector actions document the argument as `user_id`, but the connector expects `userId` — using the documented name always fails with "missing required argument userId". This corrects the argument name in the actions table. Also updates the allowed-domains documentation to reflect that the field now filters group and role membership grants in addition to account syncing.
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
johnallers
approved these changes
Jul 30, 2026
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fix action argument names: The
enable_useranddisable_userconnector actions document the argument asuser_id, but the connector expectsuserId. Using the documented name always fails withmissing required argument userId. This corrects both entries in the actions table.Document allowed-domains scope change: The
allowed-domainsfield now filters group and role membership grants in addition to account syncing. The docs previously described it as only affecting account sync. Updated the cloud-hosted setup description and the self-hosted YAML comments to reflect the broader scope.Test plan
userIdinstead ofuser_iduser_idor outdated allowed-domains descriptions remainAutomated PR Notice
This PR was automatically created by c1-dev-bot as a potential documentation update.
This documentation requires: