Overview
This node integrates with the Creatio platform via its OData API, enabling users to perform various data operations such as retrieving, creating, updating, and deleting records. It supports fetching metadata about entities and listing available tables as well.
Common scenarios where this node is beneficial include:
- Automating data synchronization between Creatio and other systems.
- Querying specific records or datasets from Creatio using OData filters.
- Managing Creatio records programmatically without manual UI interaction.
- Extracting metadata for dynamic workflows that adapt to Creatio schema changes.
Practical examples:
- Retrieve a list of contacts filtered by city.
- Create a new sales opportunity record.
- Update an existing account's details.
- Delete obsolete records based on certain criteria.
- Fetch field names of a specific entity to build dynamic forms.
Properties
| Name | Meaning |
|---|---|
| Operation | The action to perform: GET (retrieve records), POST (create record), PATCH (update record), DELETE (delete record), METADATA (get field names for an entity), or TABLES (list available tables). |
| Subpath Name or ID | The target entity/table name or ID within Creatio to operate on. This is required for most operations and can be selected from a dynamically loaded list or specified via expression. |
| Select Field Names or IDs | For GET operation: specify which fields to retrieve from the entity. Multiple fields can be selected or specified via expression. |
| Top | For GET operation: limits the number of records returned. Defaults to 10. |
| Filter | For GET operation: an OData filter expression to narrow down results (e.g., "Name eq 'John'"). |
| Expand | For GET operation: comma-separated related entities to expand in the response. |
| Append Request | For GET, POST, and PATCH operations: whether to append the original request parameters to the output alongside the response. |
| Specify Input Schema | Whether to specify a JSON schema for input validation of the function. When enabled, the input must conform to the defined schema. |
| Schema Type | How to specify the input schema: generate from a JSON example or define manually using JSON Schema format. |
| JSON Example | When generating schema from example: provide a sample JSON object to infer the schema. |
| Input Schema | When defining schema manually: provide a JSON Schema describing the expected input structure. |
| ID | For PATCH and DELETE operations: the ID of the specific record to update or delete. |
| Body | For POST and PATCH operations: the JSON body containing data to create or update the record. |
Output
The node outputs an array of JSON objects representing the response from the Creatio API:
- For
GEToperations, it returns the retrieved records as JSON objects. If no specific subpath is provided, it returns a list of tables. - For
POSToperations, it returns the created record's data. - For
PATCHoperations, it returns the updated record's data. - For
DELETEoperations, it returns a confirmation object{ deleted: true }if successful. - For
METADATAoperations, it returns an array of field names for the specified entity. - For
TABLESoperation, it returns an array of table names excluding system/internal tables.
If "Append Request" is enabled, the output includes both the request parameters and the response for better traceability.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Creatio API.
- Needs valid Creatio URL, username, and password credentials to authenticate and obtain session cookies.
- Uses OData protocol endpoints exposed by Creatio.
- Requires n8n HTTP Request helper for making authenticated requests with proper headers and cookies.
- No additional external libraries beyond those bundled with n8n are needed.
Troubleshooting
- Authentication failures: Errors during login usually indicate incorrect credentials or connectivity issues. Verify the Creatio URL, username, and password.
- 401 Unauthorized errors: May occur if session cookies expire or are invalid. Re-authenticate or check credential validity.
- Invalid OData filter syntax: Ensure filter expressions follow OData standards; otherwise, the API will reject the query.
- Missing or incorrect Subpath: Selecting or specifying an invalid entity/table name will cause errors. Use the dynamic options to pick valid entities.
- Empty responses: Could mean no matching records found or insufficient permissions.
- Schema validation errors: When specifying input schemas, ensure the input matches the defined JSON Schema exactly.
- Network or timeout issues: Check network connectivity and Creatio server availability.