Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

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.

Practical examples include:

  • Removing a custom attribute from a customer profile in a CRM system.
  • Deleting a custom setting or flag previously assigned to an account.
  • Cleaning up legacy data fields during data maintenance workflows.

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 contains the response from the API after attempting to delete the custom field value. Typically, this will confirm whether the deletion was successful or provide error details if it failed.

No binary data output is expected from 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 node uses standard HTTP headers for JSON content negotiation.

Troubleshooting

  • Common issues:

    • Invalid or missing identifiers (Account Id, Custom Field Id, Custom Field Value Id) will cause the deletion to fail.
    • Authentication errors if the API key or credentials are not properly configured.
    • Network or connectivity issues preventing access to the API endpoint.
  • Error messages and resolutions:

    • "Unauthorized" or "Authentication failed": Verify that the API key credential is correctly set up and has necessary permissions.
    • "Not Found": Check that the provided IDs correspond to existing resources.
    • "Bad Request": Ensure all required properties are provided and valid.
    • Timeouts or network errors: Confirm network connectivity and API availability.

Links and References

  • Refer to the external API documentation for custom fields management for detailed information on identifiers and deletion behavior.
  • n8n documentation on configuring API credentials and HTTP request nodes may help with setup.

Discussion