Financial Cents

Interact with the Financial Cents API
Join our community

Actions21

Overview

This node integrates with the Financial Cents API to manage contacts associated with clients. Specifically, the Delete Contact operation allows users to remove a contact from a selected client in their Financial Cents account.

Typical use cases include:

  • Automating cleanup of outdated or incorrect contact information.
  • Managing client contact lists by programmatically removing contacts no longer relevant.
  • Integrating with other workflows where contact deletion is triggered by external events (e.g., CRM updates).

Example: Automatically delete a contact when they unsubscribe or are marked inactive in another system.

Properties

Name Meaning
Debug: Include Raw Response If enabled, includes the full raw JSON response from the API under the __raw field.
Client The parent client under which the contact exists. Select from available clients.
Contact The specific contact to delete under the selected client. Select from available contacts.

Output

The output contains a JSON object representing the result of the delete operation. Typically, this will include a success confirmation. If debug mode is enabled, the raw API response is included under the __raw property.

Example output JSON structure:

{
  "success": true,
  "__raw": { /* full API response JSON */ }
}

No binary data is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Financial Cents API.
  • The node uses HTTP requests to the Financial Cents API endpoints.
  • The user must have appropriate permissions to delete contacts within their Financial Cents account.
  • The node depends on n8n's ability to load clients and contacts dynamically for selection.

Troubleshooting

  • Missing Contact ID Error:
    If the Contact ID is not provided when attempting to delete, the node throws:
    "Contact ID is required to delete a contact. Please select a Contact."
    Resolution: Ensure you select a valid contact from the dropdown or provide a valid contact ID.

  • API Authentication Errors:
    If the API key credential is missing or invalid, the node will fail to authenticate.
    Resolution: Verify that the API key credential is correctly configured in n8n.

  • Permission Denied or Not Found:
    If the contact does not exist or the user lacks permission, the API may return errors.
    Resolution: Confirm the contact exists under the specified client and that your API key has sufficient rights.

  • Network or Timeout Issues:
    Network problems can cause request failures.
    Resolution: Check network connectivity and retry.

Links and References

This summary focuses exclusively on the Contact - Delete operation as requested.

Discussion