SinergiaCRM icon

SinergiaCRM

Perform operations on any module in SinergiaCRM (SuiteCRM API).
Join our community

Actions6

Overview

This node integrates with SinergiaCRM, a CRM system based on SuiteCRM API, allowing users to perform various operations on any module within SinergiaCRM. The "Update" operation specifically updates an existing record in a selected module by its ID with new data provided as JSON.

Common scenarios for this node include:

  • Modifying customer or contact information in the CRM.
  • Updating sales opportunities or leads with new status or details.
  • Changing custom fields in any module dynamically without needing separate nodes per module.

Practical example: You have a workflow that processes incoming form submissions and needs to update the corresponding lead record in SinergiaCRM with the latest contact info and notes.

Properties

Name Meaning
Module Select a module from SinergiaCRM where the record exists (e.g., Contacts, Leads, Accounts)
Record ID The unique identifier of the record you want to update
Data (JSON) JSON object containing the fields and their new values to update in the record

Output

The output is an array of items, each containing a json field representing the updated record returned from SinergiaCRM. The structure corresponds to the CRM's API response for the updated resource, typically including:

  • id: The record's unique identifier.
  • type: The module name.
  • attributes: An object with the updated fields and their values.

Example output snippet:

{
  "id": "123",
  "type": "Contacts",
  "attributes": {
    "first_name": "John",
    "last_name": "Doe",
    "email": "john.doe@example.com"
  }
}

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to SinergiaCRM via an API authentication credential (an API key or token).
  • The node uses the SinergiaCRM SuiteCRM-compatible REST API v8 endpoints.
  • Proper configuration of the domain URL and credentials in n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing Record ID will cause the update to fail.
    • Malformed JSON in the "Data (JSON)" property can cause parsing errors.
    • Network or authentication failures if the API credentials are incorrect or expired.
    • Attempting to update a record in a non-existent or misspelled module.

  • Error messages and resolutions:

    • "Record not found": Verify the Record ID and Module are correct.
    • "Invalid JSON": Ensure the JSON input is well-formed and valid.
    • "Authentication failed": Check API credentials and permissions.
    • "Request failed" or HTTP 4xx/5xx errors: Inspect API endpoint URL and network connectivity.

  • Enabling "Continue On Fail" allows the workflow to proceed even if some updates fail, useful for batch processing.

Links and References

Discussion