Actions4
- Generic Table Actions
Overview
This node allows users to interact with any table in the Perfex CRM system via its Won API module. Specifically, for the "Generic Table" resource and the "Get Record(s)" operation, it retrieves one or more records from a specified table. Users can fetch a single record by its ID, multiple records filtered by JSON query parameters, or perform a general search using a search term.
Common scenarios include:
- Retrieving client details by their unique ID.
- Fetching all active invoices filtered by status or user ID.
- Searching staff records using a keyword when no specific filters or IDs are provided.
Practical example:
- A user wants to get all clients who are currently active. They specify the table as "clients", leave the Record ID empty, and provide a filter JSON like
{"status": "active"}. The node returns all matching client records.
Properties
| Name | Meaning |
|---|---|
| Table Name | Name of the table in Perfex CRM (e.g., clients, invoices, staff). Do not include the tbl prefix. |
| Record ID | ID of the record to retrieve. If empty, all records are fetched respecting filters or search term. |
| Filters (JSON) | JSON object specifying query parameters to filter records (e.g., {"userid": 1, "status": "active"}). Used if Record ID is empty. |
| Search Term | A general search string used if both Record ID and Filters are empty to find matching records. |
Output
The output is an array of JSON objects representing the retrieved records from the specified table. Each object corresponds to a record with fields matching the table's columns.
If a single Record ID is provided, the output contains that specific record. If no Record ID is given, the output includes all records matching the filters or search term.
No binary data output is produced by this operation.
Dependencies
- Requires connection credentials to the Perfex CRM Won API, including:
- The base URL of the Perfex CRM instance.
- An API authentication token.
- These credentials must be configured in n8n before using the node.
Troubleshooting
- Missing Record ID for update/delete operations: The node throws an error if you attempt to update or delete without specifying a Record ID. For "get" operation, Record ID is optional.
- Invalid JSON in Filters: Ensure the Filters property contains valid JSON; otherwise, the request may fail or return unexpected results.
- Empty results: If no records match the filters or search term, the output will be an empty array.
- API connectivity issues: Verify that the Perfex CRM URL and API token are correct and that the API is accessible from your environment.
Links and References
- Perfex CRM Official Website
- Perfex CRM Won API Documentation (hypothetical link, replace with actual if available)