Overview
This node integrates with the Creatio API, enabling users to perform various operations on Creatio data entities via OData endpoints. It supports creating, reading, updating, and deleting records, as well as retrieving metadata about tables and fields.
Common scenarios include:
- Automating data synchronization between Creatio and other systems.
- Fetching specific records or lists of records based on filters.
- Creating new records in Creatio from external data sources.
- Updating existing records programmatically.
- Deleting records when no longer needed.
- Retrieving metadata to dynamically build workflows or validate data structures.
For example, a user might use this node to create a new contact record in Creatio by specifying the target entity and providing the JSON body with contact details. Alternatively, they could fetch a list of accounts filtered by region or retrieve the schema of a particular table to understand its fields.
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 available tables). |
| Subpath Name or ID | The target Creatio entity/table name or ID to operate on. This is selected from a dynamic list loaded from Creatio's OData metadata. Required for GET, POST, PATCH, METADATA operations. |
| Select Field Names or IDs | For GET operations, specify which fields to retrieve. Can select multiple fields or provide expressions. |
| Top | For GET operations, limits the number of records returned. |
| Filter | OData filter expression to narrow down GET query results (e.g., "Name eq 'John'"). |
| Expand | Comma-separated related entities to expand in GET queries. |
| ID | For PATCH and DELETE operations, specifies the ID of the record to update or delete. |
| Body | JSON object representing the data to send in POST (create) or PATCH (update) requests. Required for these operations. |
| Append Request | Boolean flag indicating whether to append the request parameters to the response output. Useful for debugging or logging. |
| Specify Input Schema | Boolean flag to enable input schema validation for the function. When enabled, the node expects inputs to conform to a specified JSON schema. |
| Schema Type | How to specify the input schema: either generate from a JSON example or define manually using JSON Schema format. |
| JSON Example | Example JSON object used to generate the input schema automatically (shown if "Generate From JSON Example" is selected). |
| Input Schema | Manually defined JSON Schema describing the expected input structure (shown if "Define using JSON Schema" is selected). |
Output
The node outputs an array of JSON objects corresponding to the results of each input item processed.
- For GET operations, the output contains the retrieved records as JSON objects. If multiple records are returned, they are output as an array.
- For POST operations, the output includes the newly created record as returned by Creatio.
- For PATCH operations, the output contains the updated record or confirmation of the update.
- For DELETE operations, the output confirms deletion with
{ deleted: true }or returns the response from Creatio. - For METADATA and TABLES operations, the output provides arrays of field names or table names respectively.
- If the "Append Request" property is enabled, the output objects also include the original request parameters alongside the response under a
responsekey.
The node does not output binary data.
Dependencies
- Requires valid credentials for the Creatio API, including URL, username, and password.
- Uses session-based authentication with cookies and CSRF tokens managed internally.
- Relies on Creatio's OData API endpoints for all operations.
- Requires n8n HTTP Request helper for making authenticated API calls.
Troubleshooting
- Authentication failures: Errors during login usually indicate incorrect credentials or connectivity issues. Verify the API URL, username, and password.
- 401 Unauthorized errors: May occur if session cookies expire or are invalid. Re-authenticate or check credential validity.
- Invalid subpath or entity names: Selecting or specifying an incorrect entity/table name will cause errors. Use the dynamic dropdown to ensure valid values.
- Malformed JSON body: For POST and PATCH, ensure the JSON body is correctly formatted and matches the expected schema if input schema validation is enabled.
- OData filter syntax errors: Filters must follow OData syntax; invalid filters will cause request failures.
- Empty responses: Could indicate no matching records or incorrect query parameters.
- Network or timeout issues: Ensure the Creatio server is reachable and responsive.