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 obsolete tags, preferences, or metadata fields that were previously set.

Practical examples include:

  • Removing a deprecated custom attribute from a customer profile.
  • Cleaning up custom field values during data synchronization or migration processes.
  • Automating the removal of temporary custom data after certain workflows complete.

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 details about the deleted resource. The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating requests to the external service managing custom fields.
  • The base URL for the API must be configured in the node credentials.
  • The node depends on the external API's availability and correct configuration of authentication headers.

Troubleshooting

  • Common issues:

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

    • "Not Found" or similar indicates that one or more provided IDs do not exist.
    • "Unauthorized" or "Forbidden" suggests problems with API authentication.
    • Timeout or connection errors indicate network problems.
  • Resolutions:

    • Verify all IDs are correct and correspond to existing resources.
    • Ensure API credentials are valid and have necessary permissions.
    • Check network connectivity and API endpoint accessibility.

Links and References

  • Refer to the external API documentation for detailed information on custom field management and deletion endpoints.
  • n8n documentation on configuring API credentials and error handling best practices.

Discussion