ChargeKeep icon

ChargeKeep

Easy-to-use recurring and one-time payments software for Stripe & PayPal

Actions6

Overview

This node integrates with the ChargeKeep platform to manage contacts, invoices, products, and subscriptions related to recurring and one-time payments via Stripe and PayPal. Specifically, for the Contact - Get operation, it retrieves detailed information about a contact by their unique Contact ID.

Common scenarios where this node is beneficial include:

  • Fetching contact details to display or process in workflows.
  • Integrating customer data retrieval into automated billing or CRM processes.
  • Synchronizing contact information between ChargeKeep and other systems.

For example, you might use this node to get a customer's profile before generating an invoice or sending a personalized email.

Properties

Name Meaning
Contact ID The unique numeric identifier of the contact to retrieve. This is required to specify which contact's data to fetch.

Output

The output JSON contains the full data of the requested contact as returned by the ChargeKeep API endpoint /api/services/CRM/Contact/GetContactData. This typically includes personal information, business info, addresses, contact methods, and possibly custom fields associated with the contact.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the ChargeKeep API using an API key credential configured in n8n.
  • The node uses the ChargeKeep REST API endpoint /api/services/CRM/Contact/GetContactData with a GET request, passing the Contact ID as a query parameter.
  • Proper network access and valid credentials are necessary for successful API communication.

Troubleshooting

  • Common issues:

    • Invalid or missing Contact ID will cause the API call to fail or return no data.
    • Network connectivity problems or incorrect API credentials will result in authentication or connection errors.
    • If the contact does not exist, the API may return an error or empty response.

  • Error messages:

    • "Contact not found" or similar indicates the Contact ID does not correspond to any existing contact.
    • Authentication errors suggest invalid or expired API keys; verify and update credentials.
    • Timeout or network errors require checking internet connectivity and API endpoint availability.

To resolve these issues:

  • Ensure the Contact ID is correct and exists in ChargeKeep.
  • Verify that the API key credential is properly set up and has sufficient permissions.
  • Check network settings and retry the operation.

Links and References

Discussion