Actions6
Overview
This node updates contact records in the Sperse CRM system. It allows users to modify detailed information about a contact, including personal details, addresses, business info, subscriptions, and custom fields. The node supports matching existing contacts by email and full name to update them or updating directly by contact ID.
Common scenarios include:
- Keeping customer or partner contact information up-to-date.
- Synchronizing contact data from other systems into Sperse CRM.
- Managing detailed contact profiles with multiple addresses, social links, and subscription data.
- Automating user creation and sending welcome emails when updating contacts.
Practical example:
- A marketing automation workflow that updates lead information after a form submission, enriching the contact record with new phone numbers, addresses, and subscription details.
Properties
| Name | Meaning |
|---|---|
| Contact Type | Type of contact: Lead, Client, or Partner. |
| Match Existing Contact | Whether to try finding an existing contact by Email and Full Name to update it ("Yes" or "No"). |
| Contact ID | Unique identifier of the contact in Sperse CRM used for direct lookup. |
| 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 3) - Preferred Time of Day to contact - Driving License and State - Military Duty status - US Citizenship - 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 and social profile IDs: - Website, Facebook, LinkedIn, Instagram, Twitter, Google Reviews, AngelList, Zoom, Photo URL |
| Custom Field | Up to 5 additional custom string fields for extra data. |
| Business Info | Company-related info: - Company Name (mandatory if no personal names) - Organization Type (Inc, LLC, LLP, etc.) - Job Title - Employment status and start date - Employee count - Date Founded - EIN - Annual Revenue - Industry - Company phones, fax, email - Company Affiliate Code |
| Company Address | Company address fields similar to Home Address. |
| Company Links | Company social and web links: - Website, Facebook, LinkedIn, Instagram, Twitter, Google Reviews, Crunchbase, BBB, Zoom, Calendly, Logo URL |
| Work Info | Work phone numbers and emails (primary and alternatives). |
| Work Address | Work address fields similar to Home Address. |
| Other Field | Miscellaneous fields: - Assigned User (preferably unique 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-10) |
| UTM Parameters Field | Marketing UTM parameters: - Source, Medium, Campaign, Term, Content, Keyword, AdGroup, Name |
| Request Custom Field | Up to 5 additional custom request fields for extra data. |
| Subscription 1 Field | Subscription details: - Product Code, Payment Period Type (Annual, LifeTime, Monthly), System Type, Code, Name, Level, Start and End Dates, Amount |
| Subscription 2 Field | Same as Subscription 1 but for a second subscription. |
| Subscription 3 Field | Same as Subscription 1 but for a third subscription. |
Output
The node outputs JSON data representing the updated contact record as returned by the Sperse CRM API. This includes all fields sent in the update request along with any additional metadata or identifiers assigned by the system.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Sperse CRM API.
- The node uses the
/api/services/CRM/Import/ImportContactendpoint via POST to update contact data. - Proper configuration of the API credential in n8n is necessary for successful requests.
Troubleshooting
Common issues:
- Missing required fields like Contact Type or insufficient identification (no Contact ID or match criteria) may cause errors.
- Validation errors on fields (e.g., invalid date formats) can cause the API to reject the update unless "Ignore Invalid Values" is enabled.
- Incorrect API credentials or network issues will result in authentication or connection errors.
Error messages:
- Validation error messages typically indicate which field failed and why; enabling "Ignore Invalid Values" can bypass some of these.
- Authentication errors suggest checking the API key credential setup.
- Not found errors occur if the Contact ID does not exist and "Match Existing Contact" is set to "No".
Resolution tips:
- Ensure all mandatory fields are provided.
- Use correct date formats (YYYY-MM-DD or MM-DD-YYYY).
- Verify API credentials and network connectivity.
- Enable "Match Existing Contact" to update by email and name if Contact ID is unknown.
Links and References
- Sperse CRM API documentation (refer to your Sperse CRM provider's official docs)
- n8n documentation on creating and using API credentials
- General best practices for managing contact data in CRMs