Actions11
Overview
The "Contact Update" operation in this node allows users to update details of an existing contact associated with a prospect in the ProspectPro system. This is useful for keeping contact information current, such as updating names, email addresses, job titles, LinkedIn URLs, or phone numbers.
Typical use cases include:
- Correcting or adding missing contact information.
- Updating contact details after receiving new data from CRM or marketing tools.
- Synchronizing contact records between ProspectPro and other systems.
For example, if you have a contact whose job title has changed, you can use this operation to update that field without affecting other contact data.
Properties
| Name | Meaning |
|---|---|
| Prospect ID | The unique identifier of the prospect the contact belongs to. Required to specify which prospect's contact to update. |
| Contact ID | The unique identifier of the contact to update. You must provide either this or a derived ID from the prospect. |
| Fields to Update | A collection of fields that can be updated on the contact. Each field is optional; leave empty to skip updating it. Available fields: - Contact First Name - Contact Last Name - Email Address - Job Title - LinkedIn URL - Phone Number |
Output
The output JSON contains the updated contact data returned from the ProspectPro API after the PATCH request. It reflects the current state of the contact with all updated fields.
If the node supports binary data output (not indicated here), it would typically represent attachments or files related to the contact, but this operation focuses on JSON data only.
Dependencies
- Requires an active connection to the ProspectPro API via an API key credential.
- The base URL used for requests is
https://api.prospectpro.nl/v1.2. - The node uses HTTP PATCH method to update contact data at the
/contactsendpoint. - Proper permissions on the API key are necessary to perform update operations.
Troubleshooting
- Missing Required IDs: If either the Prospect ID or Contact ID is not provided, the update will fail. Ensure both are correctly set.
- Invalid Contact ID: Using an incorrect or non-existent Contact ID will result in errors or no changes. Verify the contact exists.
- Empty Update Fields: If no fields are specified to update, the request may succeed but make no changes. Always specify at least one field to update.
- API Authentication Errors: Invalid or expired API credentials will cause authentication failures. Check and refresh your API key if needed.
- Network Issues: Connectivity problems can prevent the request from completing. Confirm network access to the ProspectPro API endpoint.
Common error messages might include:
- Unauthorized or 401 errors indicating credential issues.
- 404 Not Found if the contact or prospect does not exist.
- 400 Bad Request if the input parameters are malformed.
Resolving these usually involves verifying input values, checking API credentials, and ensuring the contact and prospect IDs are valid.
Links and References
- ProspectPro API Documentation (for detailed API usage and field definitions)
- n8n Documentation on Creating Custom Nodes