Actions10
- Lime Type Actions
- Lime Object Actions
- Query API Actions
Overview
The Lime CRM Node for n8n allows you to interact with the Lime CRM API. Specifically, when using the Resource: Lime Object and Operation: Update, this node updates an existing record (object) in your Lime CRM instance. This is useful for automating workflows where you need to modify customer data, update company information, or change any entity stored in Lime CRM based on triggers or other workflow logic.
Practical examples:
- Automatically updating a customer's phone number after receiving new information from another system.
- Changing the status of a sales opportunity when a related event occurs.
- Updating company details in bulk as part of a data synchronization process.
Properties
Name | Type | Meaning |
---|---|---|
LimeType | options | The type of entity (e.g., company, person, deal) to update in Lime CRM. |
Record ID | string | The unique identifier of the record you want to update. |
Input Type | options | Determines how you provide the fields to update: either via UI ("Simple Fields") or JSON. |
Data | json | Key-value pairs representing the fields and their new values (used if Input Type is JSON). |
Fields | fixedCollection | List of fields and their values to update (used if Input Type is Simple Fields). |
Output
The output will be a JSON object representing the updated Lime CRM record. The structure of this object depends on the entity type and the fields you updated, but typically includes all standard fields of the record after the update.
Example output:
{
"id": "123",
"name": "Updated Company Name",
"phone": "+987654321",
// ...other fields present in the record
}
If an error occurs and "Continue On Fail" is enabled, the output will include an error
field:
{
"error": "Error message here",
"json": {
"error": "Error message here"
}
}
Dependencies
- External Service: Requires access to a Lime CRM instance with API enabled.
- API Credentials: You must configure the
limeCrmApi
credential in n8n. - Environment Variables: None specified, but ensure network access to your Lime CRM server.
Troubleshooting
Common Issues:
- Invalid Record ID: If the provided Record ID does not exist, the node will throw an error indicating the record was not found.
- Field Name Mismatch: If you specify a field name that does not exist in the selected LimeType, the update may fail or the field will be ignored.
- Insufficient Permissions: The API credentials used must have permission to update records of the specified type.
- Malformed JSON: When using the JSON input method, ensure your JSON is valid and matches the expected field names.
Error Messages:
"The resource \"...\" is not supported!"
- Ensure you have selected a valid resource.
"Cannot find record with id ..."
- Double-check the Record ID.
"Field ... does not exist on type ..."
- Verify field names against your Lime CRM schema.