Overview
This node integrates with the FullFunnel (HighLevel) service to manage contacts. Specifically, for the Contact - Update operation, it updates an existing contact's details such as email, first name, last name, and phone number by sending a request to the FullFunnel API.
Typical use cases include:
- Keeping contact information up-to-date in your CRM or marketing platform.
- Automating updates when customer data changes in other systems.
- Synchronizing contact details across multiple platforms.
For example, if a customer's phone number changes, this node can update that contact record automatically without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to update. |
| Update Fields | A collection of fields to update on the contact. Options include: |
| - Email: The contact's email address. | |
| - First Name: The contact's first name. | |
| - Last Name: The contact's last name. | |
| - Phone: The contact's phone number. |
Output
The output is a JSON object representing the updated contact returned from the FullFunnel API. It contains the contact's current state after the update, including all fields managed by the API.
Example structure of the output JSON:
{
"contact": {
"id": "string",
"email": "string",
"firstName": "string",
"lastName": "string",
"phone": "string",
"locationId": "string",
// ... other possible contact fields returned by the API
}
}
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the FullFunnel (HighLevel) API.
- The node uses the FullFunnel API endpoint at
https://services.leadconnectorhq.com. - The API version header
"Version": "2021-07-28"is set in requests. - The user must configure the node with valid credentials containing an API key and location ID.
Troubleshooting
Common issues:
- Invalid or missing Contact ID will cause the update to fail.
- Providing no fields in "Update Fields" may result in no changes being applied.
- Network or authentication errors if the API key or location ID are incorrect or expired.
Error messages:
- Errors from the API will be thrown and can be caught if "Continue On Fail" is enabled.
- Typical error messages might include "Unauthorized" (invalid API key), "Not Found" (invalid Contact ID), or validation errors for malformed input fields.
Resolution tips:
- Verify the Contact ID exists before attempting an update.
- Ensure the API key and location ID credentials are correctly configured.
- Provide at least one field to update in the "Update Fields" collection.
- Enable "Continue On Fail" to handle errors gracefully in workflows.
Links and References
- FullFunnel (HighLevel) API Documentation (general reference, actual URL may vary)
- n8n Documentation on Creating Custom Nodes
- REST API concepts for updating resources: HTTP PUT Method