Partially icon

Partially

Partially Payment Plans API

Actions37

Overview

This node integrates with the Partially Payment Plans API to manage customer data and related payment plan operations. Specifically, for the Customer resource with the GDPR Remove operation, it allows users to remove a customer's personal data in compliance with GDPR regulations by sending a request to the API endpoint responsible for data removal.

Common scenarios where this node is beneficial include:

  • Automating GDPR compliance workflows by programmatically removing customer data upon request.
  • Integrating customer data management into broader automation pipelines.
  • Ensuring that customer privacy requests are handled efficiently without manual intervention.

Practical example:

  • A business receives a GDPR data removal request from a customer. Using this node configured with the "Customer" resource and "GDPR Remove" operation, the workflow can automatically trigger the removal of that customer's data from the Partially system by providing the customer's ID.

Properties

Name Meaning
Customer ID The unique identifier of the customer whose data should be removed for GDPR compliance.

Output

The node outputs an array of JSON objects representing the response from the Partially API after attempting the GDPR removal. The structure typically includes confirmation or status details about the removal operation. The exact fields depend on the API's response but generally confirm successful removal or provide error information.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the Partially Payment Plans API.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • The node uses the internal helper function partiallyApiRequest to communicate with the API endpoints.

Troubleshooting

  • Common issues:

    • Invalid or missing Customer ID: The operation requires a valid customer identifier; ensure the ID is correct and exists in the system.
    • Authentication errors: Ensure the API key or token credential is correctly set up and has sufficient permissions.
    • Network or API downtime: Temporary connectivity issues may cause failures; retry or check API status.

  • Error messages:

    • Errors returned from the API will typically indicate if the customer was not found or if the removal failed due to permission issues.
    • If the node logs show no response or timeouts, verify network connectivity and API availability.

Links and References

Discussion