Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Custom Fields → Replaces Managers For A Specific Custom Field Value

AI-generated

Overview

This node operation allows users to replace managers associated with a specific custom field value within an account. It is useful in scenarios where management responsibilities tied to particular custom field values need to be updated or reassigned in bulk. For example, if a company uses custom fields to categorize projects or clients and assigns managers accordingly, this operation can update the manager assignments when organizational changes occur.

Properties

Name Meaning
Account Id Identifier of the account where the custom field exists.
Custom Field Id Identifier of the custom field for which managers are being replaced.
Custom Field Value Id Identifier of the specific value of the custom field whose managers will be replaced.
Body JSON object containing the details of the new managers or related data to replace existing ones.

Output

The node outputs JSON data representing the result of the replacement operation. This typically includes confirmation of success, details of the updated managers, or any relevant metadata returned by the API. The output does not include binary data.

Dependencies

  • Requires an API key credential for authentication with the external service managing accounts and custom fields.
  • The node depends on a REST API endpoint that supports replacing managers for a given custom field value.
  • Proper configuration of the base URL and authentication credentials in n8n is necessary.

Troubleshooting

  • Common Issues:
    • Invalid or missing identifiers (Account Id, Custom Field Id, Custom Field Value Id) may cause the operation to fail.
    • Incorrectly formatted JSON in the Body property can lead to parsing errors.
    • Authentication failures due to missing or invalid API keys.
  • Error Messages:
    • "Unauthorized" or "Authentication failed": Check API credentials and permissions.
    • "Not Found" or "Invalid identifier": Verify that the provided IDs exist and are correct.
    • "Bad Request" or "Invalid JSON": Ensure the Body property contains valid JSON matching the expected schema.

Links and References

  • Refer to the external API documentation for managing custom fields and their values.
  • Consult n8n documentation on how to configure API credentials and use JSON input properties.

Discussion