SinergiaCRM icon

SinergiaCRM

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

Actions6

Overview

This node integrates with SinergiaCRM, allowing users to perform various operations on any module within the SinergiaCRM system via its SuiteCRM-compatible API. The "Delete" operation specifically enables the removal of a record from a selected module by specifying the record's ID.

Common scenarios for using this node include automating CRM data management tasks such as cleaning up outdated or incorrect records, integrating deletion workflows triggered by external events, or synchronizing data deletions across systems.

For example, you might use this node to delete a contact record from the "Contacts" module when it is marked as inactive in another system, ensuring your CRM stays up-to-date automatically.

Properties

Name Meaning
Module Selects the SinergiaCRM module where the record exists (e.g., Contacts, Accounts).
Record ID The unique identifier of the record to delete within the selected module.

Output

The output JSON contains a confirmation of the deletion:

  • success: A boolean indicating whether the deletion was successful (true).
  • id: The ID of the deleted record.

Example output JSON:

{
  "success": true,
  "id": "record-id-value"
}

No binary data is produced by this operation.

Dependencies

  • Requires an active connection to SinergiaCRM via an API authentication credential.
  • The node uses the SinergiaCRM API endpoint constructed from the domain URL provided in the credentials.
  • Proper permissions are needed in SinergiaCRM to delete records in the specified module.

Troubleshooting

  • Common Issues:

    • Invalid or missing Record ID: Ensure the ID corresponds to an existing record in the chosen module.
    • Insufficient permissions: The API user must have delete rights for the target module.
    • Network or authentication errors: Verify that the API credentials are correct and the SinergiaCRM instance is reachable.

  • Error Messages:

    • Errors returned from the API will be thrown unless "Continue On Fail" is enabled.
    • Typical error messages may include "Record not found," "Unauthorized," or "Invalid module."

  • Resolution Tips:

    • Double-check the module name and record ID inputs.
    • Confirm API credentials and access rights.
    • Enable "Continue On Fail" to handle errors gracefully in workflows.

Links and References

Discussion