Perfex CRM (Won API)

Interact with Perfex CRM via the Won API module
Join our community

Actions4

Overview

This node allows interaction with any table in the Perfex CRM system via its Won API module. Specifically, for the Delete Record operation on a Generic Table, it deletes a record identified by its ID from a specified table in Perfex CRM.

Typical use cases include:

  • Automating cleanup of outdated or incorrect records in various tables such as clients, invoices, or staff.
  • Integrating Perfex CRM with other systems to synchronize deletions automatically.
  • Managing data lifecycle by programmatically removing entries based on business logic.

For example, deleting a client record with ID 123 from the clients table can be done by specifying the table name as clients and the record ID as 123.

Properties

Name Meaning
Table Name The name of the target table in Perfex CRM (e.g., clients, invoices, staff). Do not include the tbl prefix.
Record ID The unique identifier of the record to delete from the specified table. This is required for the delete operation.

Output

The node outputs an array of JSON objects representing the response from the Perfex CRM API after attempting the deletion. Typically, this will contain confirmation of the deletion or details about the deleted record depending on the API's response.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to a Perfex CRM instance via the Won API.
  • Needs an API authentication token credential configured in n8n to authorize requests.
  • The base URL of the Perfex CRM instance must be provided in the credentials.

Troubleshooting

  • Missing Record ID Error: If the Record ID is not provided for the delete operation, the node throws an error stating that the Record ID is required. Ensure you specify the correct record ID.
  • Invalid Table Name: Providing a non-existent or misspelled table name may cause API errors or no action. Verify the table name matches exactly what exists in Perfex CRM without the tbl prefix.
  • Authentication Failures: If the API token or URL is incorrect or expired, the node will fail to connect. Check your credentials and update them if necessary.
  • Record Not Found: Attempting to delete a record that does not exist may result in an error or no effect. Confirm the record ID is valid before running the node.

Links and References

Discussion