Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Custom Fields → Removes Managers For A Specific Custom Field Value

AI-generated

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 revoke managerial permissions or roles linked to particular custom field values, such as when updating user roles or cleaning up access rights based on dynamic criteria.

For example, if your system assigns managers to projects via custom fields, and a project’s status changes requiring removal of those managers, this operation automates that process by targeting the exact custom field value representing the project.

Properties

Name Meaning
Account Id Identifier of the account from which managers will be removed.
Custom Field Id Identifier of the custom field that holds the manager assignments.
Custom Field Value Id Identifier of the specific value within the custom field for which managers are removed.

Output

The node outputs JSON data reflecting 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 that managers linked to the specified custom field value have been removed.

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 base URL and headers (e.g., Accept and Content-Type set to application/json).
  • Proper configuration of credentials and API endpoint in n8n is necessary for successful execution.

Troubleshooting

  • Common Issues:

    • Invalid or missing Account Id, Custom Field Id, or Custom Field Value Id can cause the operation to fail.
    • Insufficient permissions or invalid API credentials may lead to authorization errors.
    • Network connectivity issues or incorrect base URL configuration can prevent API communication.
  • Error Messages:

    • "Unauthorized" or "Authentication failed": Check that the API key credential is correctly set and has required permissions.
    • "Not Found" or "Resource does not exist": Verify that the provided Account Id, Custom Field Id, and Custom Field Value Id are correct.
    • "Bad Request": Ensure all required parameters are provided and valid.

Resolving these usually involves verifying input parameters, checking credential validity, and confirming network/API endpoint accessibility.

Links and References

  • Refer to the external API documentation for managing accounts and custom fields to understand parameter requirements and response formats.
  • n8n documentation on setting up API credentials and HTTP request nodes for further customization.

Discussion