Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node operation removes managers associated with a specific custom field value within an account. It is useful in scenarios where you need to update or clean up managerial assignments linked to particular custom field values, such as when organizational roles change or when certain custom field values become obsolete.

For example, if your system uses custom fields to tag users with specific roles or responsibilities, and you want to revoke manager privileges from all users assigned a certain custom field value, this operation automates that process.

Properties

Name Meaning
Account Id Identifier of the account where the custom field exists.
Custom Field Id Identifier of the custom field from which managers will be removed.
Custom Field Value Id Identifier of the specific value of the custom field for which managers are to be removed.

Output

The node outputs JSON data representing the result of the removal operation. This typically includes confirmation of success or details about the affected managers. The exact structure depends on the API response but generally confirms which managers were removed or if the operation was successful.

No binary data output is expected from this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the external service managing accounts and custom fields.
  • The node relies on a REST API endpoint configured via the base URL provided in the credentials.
  • Proper permissions must be granted to the API key to modify custom field manager assignments.

Troubleshooting

  • Common Issues:

    • Invalid or missing identifiers (Account Id, Custom Field Id, Custom Field Value Id) will cause the operation to fail.
    • Insufficient permissions for the API key may result in authorization errors.
    • Network connectivity issues can prevent the node from reaching the external API.
  • Error Messages:

    • "Unauthorized" or "Forbidden": Check API key validity and permissions.
    • "Not Found": Verify that the Account Id, Custom Field Id, and Custom Field Value Id are correct and exist.
    • "Bad Request": Ensure all required properties are provided and correctly formatted.

Resolving these usually involves verifying input parameters, checking API credentials, and ensuring network access.

Links and References

  • Refer to the external service's API documentation for managing custom fields and their values.
  • Consult n8n documentation on setting up API credentials and handling HTTP request nodes for more context on authentication and error handling.

Discussion