Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node operation allows you to replace the managers associated with a specific custom field value within an account. It is useful in scenarios where you need to update or reassign managerial responsibilities linked to particular custom field entries, such as changing the team leads responsible for a project or department identified by a custom field.

For example, if your system tracks projects using custom fields and each project has assigned managers, this operation lets you update the list of managers for a given project (custom field value) efficiently.

Properties

Name Meaning
Account Id Identifier of the account where the custom field exists.
Custom Field Id Identifier of the custom field whose value's managers you want to replace.
Custom Field Value Id Identifier of the specific value of the custom field for which managers are replaced.
Body JSON object containing the new manager assignments or related data to update.

Output

The node outputs JSON data representing the result of the replacement operation. This typically includes confirmation of the updated managers for the specified custom field value or details about the affected entities. The exact structure depends on the API response but generally confirms success or provides error information.

No binary data output is involved.

Dependencies

  • Requires an API key credential for authentication with the external service managing accounts and custom fields.
  • The node uses a base URL configured in credentials to send HTTP requests.
  • The operation depends on the external API defined in the bundled OpenAPI specification (payhawk.api.json), which must be accessible and properly configured.

Troubleshooting

  • Common Issues:

    • Invalid or missing identifiers (Account Id, Custom Field Id, Custom Field Value Id) will cause errors.
    • Incorrectly formatted JSON in the Body property can lead to request failures.
    • Authentication failures if the API key or credentials are not set up correctly.
    • Network or API endpoint issues may prevent successful updates.
  • Error Messages:

    • "Unauthorized" or "Authentication failed": Check API key credentials and permissions.
    • "Not Found" errors: Verify that the provided IDs exist and are correct.
    • "Bad Request": Ensure the JSON body is valid and matches the expected schema.

Links and References

  • Refer to the external API documentation for detailed information on the custom fields and manager replacement endpoints.
  • n8n documentation on how to configure API credentials and use JSON input properties.

Discussion