ChargeKeep icon

ChargeKeep

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

Actions6

Overview

This node operation updates an existing contact record in the ChargeKeep system, a recurring and one-time payments software integrated with Stripe & PayPal. It allows users to modify detailed contact information including personal details, addresses, business info, subscriptions, and custom fields. The update can either match an existing contact by email and full name or use a specific contact ID for precise targeting.

Common scenarios include:

  • Keeping customer records up-to-date with new personal or business information.
  • Managing client relationships by updating contact preferences, notes, and lead sources.
  • Synchronizing subscription details and user account settings.
  • Automating CRM workflows where contact data changes frequently.

Practical example:
A sales team uses this node to update a client's phone number, address, and subscription status after receiving updated information from the client, ensuring the CRM reflects the latest data.

Properties

Name Meaning
Contact Type Type of contact: Lead, Client, or Partner.
Match Existing Contact Whether to find and update an existing contact using Email and Full Name ("Yes" or "No").
Contact ID Unique identifier of the contact in the system, used to locate the exact record to update.
Additional Field Collection of options including:
- Ignore Invalid Values (save even if validation errors)
- Override Lists (replace lists instead of merging)
- Create User (create a user account)
- Send Welcome Email
- Contact XREF (external reference string)
- User Password (password for created user, auto-generated if empty)
Personal Info Collection of personal details such as:
- Prefix, First/Middle/Last Name, Nickname, Suffix
- Gender (Male/Female)
- Date of Birth
- Phone numbers and extensions
- SSN, Bank Code
- Emails (up to three)
- Preferred Time of Day to contact
- Driving License and State
- Military Duty and US Citizenship status
- Professional Experience and Profile Summary
- Affiliate Code
Home Address Collection of home address fields:
- Street, Address 2, City, State Name/Code, Zip, Country Name/Code
Web Url Collection of URLs related to the contact:
- Website, Facebook, LinkedIn, Instagram, Twitter, Google Reviews, AngelList, Zoom, Photo URL
Custom Field Up to five additional custom string fields for extra data.
Business Info Company-related information:
- Company Name (mandatory if no personal name)
- Organization Type (Inc, LLC, LLP, etc.)
- Job Title
- Employment status and start date
- Employee count
- Date Founded
- EIN
- Annual Revenue
- Industry
- Company phone/fax/email
- Company Affiliate Code
Company Address Company address fields similar to Home Address.
Company Links URLs related to the company:
- Website, Facebook, LinkedIn, Instagram, Twitter, Google Reviews, Crunchbase, BBB, Zoom, Calendly, Logo URL
Work Info Work contact details:
- Work phones and extensions (two numbers)
- Work emails (three addresses)
Work Address Work address fields similar to Home Address.
Other Field Miscellaneous fields:
- Assigned User (preferably unique user email)
- Follow Up Date (creates follow-up task)
- Notes
- Date Created
- Lead Stage Name
- Lead Source Code
- Lead Deal Amount
- Affiliate Code
- Campaign ID
- Channel Code
- Google Click ID
- Referer URL
- Entry URL
- Applicant ID
- IP Address
- User Agent
- Site ID and URL
- Application ID
- Rating (1 to 10)
UTM Parameters Field Marketing tracking parameters:
- UTM Source, Medium, Campaign, Term, Content, Keyword, AdGroup, Name
Request Custom Field Five additional custom request fields for contact record.
Subscription 1 Field Subscription details for first subscription:
- Product Code, Payment Period Type (Annual, LifeTime, Monthly), System Type, Code, Name, Level, Start/End Dates, Amount
Subscription 2 Field Same as Subscription 1 but for second subscription.
Subscription 3 Field Same as Subscription 1 but for third subscription.

Output

The node outputs JSON data representing the response from the ChargeKeep API after attempting to update the contact. This typically includes the updated contact record details or error information if the update failed.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the ChargeKeep API.
  • The node calls the /api/services/CRM/Import/ImportContact endpoint via POST to perform the update.
  • Proper configuration of the API credentials in n8n is necessary.

Troubleshooting

  • Common issues:

    • Providing incomplete or invalid contact identifiers (e.g., missing Contact ID when required).
    • Validation errors on fields like dates, emails, or enumerated options.
    • Conflicts when matchExisting is set to "Yes" but no matching contact is found.
    • Incorrect formatting of nested collections (addresses, subscriptions).

  • Error messages:

    • Validation errors may indicate which fields are invalid; setting "Ignore Invalid Values" to "Yes" can bypass some errors but may result in partial updates.
    • Authentication errors if API credentials are missing or incorrect.
    • Network or API endpoint errors if the ChargeKeep service is unreachable.

  • Resolutions:

    • Ensure all required fields are correctly filled.
    • Use valid date formats (YYYY-MM-DD or MM-DD-YYYY).
    • Verify API credentials and network connectivity.
    • Use "Override Lists" carefully to avoid unintended data loss.

Links and References

Discussion