Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Custom Fields → Delete A Custom Field Value

AI-generated

Overview

This node operation deletes a specific custom field value associated with an account. It is useful in scenarios where you need to remove outdated or incorrect custom data entries linked to accounts, such as clearing deprecated tags, preferences, or metadata fields that are no longer relevant.

For example, if your system tracks customer preferences via custom fields and a particular preference value needs to be removed for compliance or data cleanup, this operation allows you to delete that specific custom field value by its identifier.

Properties

Name Meaning
Account Id Identifier of the account from which the custom field value will be deleted.
Custom Field Id Identifier of the custom field that contains the value to be deleted.
Custom Field Value Id Identifier of the specific custom field value to delete.

Output

The output JSON typically contains the response from the API confirming the deletion of the custom field value. This may include status information or confirmation messages indicating success or failure of the deletion request.

No binary data output is expected from this operation.

Dependencies

  • Requires an API key credential or similar authentication token configured in n8n to authorize requests.
  • The node interacts with an external API endpoint (base URL provided via credentials) to perform the deletion.
  • Proper configuration of the base URL and authentication credentials is necessary for successful execution.

Troubleshooting

  • Common Issues:

    • Invalid or missing identifiers (Account Id, Custom Field Id, Custom Field Value Id) will cause the operation to fail.
    • Authentication errors due to missing or incorrect API credentials.
    • Network connectivity issues preventing access to the external API.
  • Error Messages:

    • "Unauthorized" or "Authentication failed": Check that the API key or authentication token is correctly set up.
    • "Not Found" or "Resource does not exist": Verify that the provided IDs correspond to existing resources.
    • "Bad Request": Ensure all required properties are provided and valid.

Resolving these usually involves verifying input parameters, ensuring credentials are correct, and checking network connectivity.

Links and References

  • Refer to the external API documentation for details on deleting custom field values.
  • Consult n8n documentation on setting up API credentials and configuring HTTP request nodes for further customization.

Discussion