Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

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 perform the replacement.

Output

The node outputs JSON data representing the result of the replace operation. This typically includes confirmation of the update, such as status messages or the updated list of managers for the specified custom field value. The output does not include binary data.

Dependencies

  • Requires an API key credential for authentication to the external service managing accounts and custom fields.
  • The node sends HTTP requests to the configured base URL of the external API.
  • The Body property must contain valid JSON that matches the expected schema of the API endpoint for replacing managers.

Troubleshooting

  • Invalid Identifiers: Errors may occur if the provided Account Id, Custom Field Id, or Custom Field Value Id do not exist or are incorrect. Verify these IDs before running the node.
  • Malformed JSON Body: If the JSON in the Body property is invalid or does not conform to the API's expected format, the request will fail. Use proper JSON syntax and ensure required fields are included.
  • Authentication Errors: Ensure that the API key or authentication token is correctly configured and has sufficient permissions.
  • API Endpoint Issues: Network errors or incorrect base URL configuration can cause failures. Confirm the API endpoint is reachable and correctly set in the node credentials.

Links and References

  • Refer to the external API documentation for details on the structure of the JSON body required to replace managers for a custom field value.
  • Consult n8n documentation on how to configure API key credentials and use JSON input properties.

Discussion