Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node operation allows you to add managers for a specific custom field value within an account. It is useful in scenarios where you want to assign or update managerial roles linked to particular custom field values, enabling fine-grained control over access or responsibilities based on custom data attributes.

For example, if you have a custom field representing project teams and want to designate certain users as managers for a specific team (custom field value), this operation facilitates that assignment programmatically.

Properties

Name Meaning
Account Id Identifier of the account where the custom field exists.
Custom Field Id Identifier of the custom field to which managers will be added.
Custom Field Value Id Identifier of the specific value within the custom field for which managers are assigned.
Body JSON object containing additional data required by the API to add managers. This typically includes details about the managers being added.

Output

The node outputs JSON data representing the response from the API after attempting to add managers to the specified custom field value. This output usually contains confirmation of the operation's success, details of the updated custom field value, or error information if the operation failed.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authentication with the external service managing custom fields.
  • The node expects a base URL configuration for the API endpoint.
  • The request uses JSON content type and requires proper formatting of the body property as JSON.

Troubleshooting

  • Common Issues:

    • Missing or incorrect Account Id, Custom Field Id, or Custom Field Value Id can cause the operation to fail.
    • Improperly formatted JSON in the Body property may lead to request errors.
    • Authentication failures due to invalid or missing API credentials.
  • Error Messages:

    • "Unauthorized" or "Authentication failed": Check API key validity and ensure credentials are correctly configured.
    • "Not Found" or similar: Verify that the provided IDs correspond to existing resources.
    • "Bad Request": Inspect the JSON body for syntax errors or missing required fields.

Links and References

  • Refer to the API documentation of the external service managing custom fields for detailed schema and examples of the JSON body structure.
  • n8n documentation on how to configure API credentials and use JSON input properties effectively.

Discussion