Modify User

Modifies a user's role in the organization.

Options

User Id

The ID of the user.

Body

The new user role to modify. This must be one of owner or member.

The JSON request body. Pre-filled with an example which is derived from the schema.

Validate JSON

Checks “Body” against the JSON schema of the API. This happens on demand only, i.e. a failed check does not prevent the node from being executed — ultimately, the API itself decides what it accepts.

Body: Validation

Result of the last “Validate JSON” run, i.e. a confirmation or the list of schema violations. Not saved with the node settings.

Result Format

Specify how the response should be mapped to the table output. The following formats are available:

Structured Table: Returns a parsed table with data split into rows and columns.

• Object: The object type, which is always organization.user
• Id: The identifier, which can be referenced in API endpoints
• Name: The name of the user
• Email: The email address of the user
• Role: owner or reader
• Added At: The Unix timestamp (in seconds) of when the user was added.
• Is Default: Whether this is the organization's default user.
• Created: The Unix timestamp (in seconds) of when the user was created.
• User: Nested user details.
• Is Service Account: Whether the user is a service account.
• Is Scale Tier Authorized Purchaser: Whether the user is an authorized purchaser for Scale Tier.
• Is Scim Managed: Whether the user is managed through SCIM.
• Api Key Last Used At: The Unix timestamp (in seconds) of the user's last API key usage.
• Technical Level: The technical level metadata for the user.
• Developer Persona: The developer persona metadata for the user.
• Projects: Projects associated with the user, if included.

Raw Response: Returns the raw response in a single row with the following columns:

• body: Response body
• status: HTTP status code

Views

This node has no views

Workflows

• No workflows found

Links

• No links available

Developers