Overview
This node integrates with the Creatio platform via its OData API, enabling users to perform various operations on Creatio data tables. It supports retrieving table names, fetching records, creating, updating, and deleting records, as well as obtaining metadata about table fields.
Common scenarios where this node is beneficial include:
- Automating data synchronization between Creatio and other systems.
- Building workflows that query or manipulate Creatio CRM data dynamically.
- Extracting metadata for dynamic form generation or validation.
- Managing Creatio records programmatically without manual intervention.
For example, a user can fetch all available tables in Creatio, select specific records from a table with filters, update a record by ID, or delete a record permanently.
Properties
| Name | Meaning |
|---|---|
| Operation | The action to perform. Options: DELETE (delete a record), GET (retrieve records), METADATA (get field names for a table), PATCH (update a record), POST (create a record), TABLES (list all tables). |
| Subpath Name or ID | The target table name or ID for operations like GET, POST, PATCH, METADATA. Loaded dynamically from Creatio's OData entities. |
| Select Field Names or IDs | Fields to retrieve when performing a GET operation. Loaded dynamically based on the selected table. |
| Top | Number of records to return in a GET operation. |
| Filter | OData filter expression to limit records returned in a GET operation (e.g., Name eq 'John'). |
| Expand | Comma-separated list of related entities to expand in a GET operation. |
| ID | Record ID used for PATCH (update) or DELETE operations. |
| Body | JSON body content for POST (create) or PATCH (update) operations. Required for these operations. |
| Append Request | Boolean flag indicating whether to append the request parameters to the response output for GET, POST, and PATCH operations. |
| Specify Input Schema | Whether to specify an input schema for validating the function input format. |
| Schema Type | How to specify the input schema: generate from a JSON example or define manually using JSON Schema. |
| JSON Example | Example JSON object used to generate the schema automatically (shown if "Generate From JSON Example" is selected). |
| Input Schema | JSON Schema definition to validate inputs manually (shown if "Define using JSON Schema" is selected). |
Output
The node outputs an array of JSON objects representing the result of the performed operation:
- For TABLES operation: An array of objects each containing a
tableNameproperty listing available Creatio tables (excluding system and view tables). - For GET operation: An array of records retrieved from the specified table, optionally filtered and limited.
- For METADATA operation: An array of objects each with a
fieldNameproperty representing the fields of the specified table. - For POST, PATCH, and DELETE operations: The response from Creatio after creating, updating, or deleting a record. For DELETE, if the response is empty, it returns
{ deleted: true }. - If the "Append Request" option is enabled, the output includes the original request parameters alongside the response for GET, POST, and PATCH operations.
The node does not output binary data.
Dependencies
- Requires valid credentials for the Creatio API, including URL, username, and password.
- Uses Creatio's OData API endpoints for all operations.
- Requires proper authentication cookies obtained via a login request to Creatio.
- Needs network access to the configured Creatio instance.
- No additional external dependencies beyond standard HTTP requests.
Troubleshooting
- Authentication failures: Errors during login to Creatio will throw messages like "Failed to authenticate with Creatio". Ensure credentials are correct and the Creatio URL is reachable.
- Permission issues: 401 Unauthorized errors may occur if the API user lacks permissions. Verify user roles and API access rights.
- Invalid table or field names: Selecting non-existent tables or fields will result in empty responses or errors. Use the TABLES operation to list valid tables and METADATA to get valid fields.
- Malformed OData queries: Incorrect filter or expand syntax can cause errors. Validate OData expressions carefully.
- Empty DELETE response: The node treats an empty string response from DELETE as a successful deletion and returns
{ deleted: true }. - Network errors: Timeouts or connectivity issues will cause request failures. Check network settings and Creatio server status.