Overview
This node integrates with the Creatio API, allowing users to perform various operations on Creatio data entities via OData endpoints. Specifically for the DELETE operation, it enables permanently deleting a record from a specified Creatio entity by its ID.
Common scenarios where this node is beneficial include:
- Automating cleanup of obsolete or incorrect records in Creatio.
- Integrating Creatio data management into broader workflows that require conditional deletion of records.
- Managing data lifecycle by programmatically removing entries based on external triggers.
For example, you might use this node to delete a customer record after a cancellation request is processed in another system, ensuring your Creatio database stays up-to-date without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Operation | The action to perform; here specifically "DELETE" to remove a record permanently. |
| Subpath | The Creatio entity (table) name from which to delete the record. This is selected from available OData entities. |
| ID | The unique identifier of the record to delete within the specified entity. |
| Specify Input Schema | Whether to enforce input schema validation for the function inputs. If enabled, the input must conform to the defined JSON schema. |
| Schema Type | How to specify the input schema: either generate automatically from a JSON example or define manually using JSON Schema format. |
| JSON Example | An example JSON object used to generate the input schema automatically (shown if "Generate From JSON Example" is selected). |
| Input Schema | A manually defined JSON Schema describing the expected input structure (shown if "Define using JSON Schema" is selected). |
| Append Request | (Not applicable for DELETE) Optionally append the original request parameters to the output response (used for GET, POST, PATCH operations). |
Output
The node outputs a JSON array containing the result of the DELETE operation for each input item. For the DELETE operation:
- If the deletion is successful and the API returns an empty response, the node outputs
{ "deleted": true }to indicate success. - Otherwise, it outputs the raw response from the Creatio API.
No binary data output is produced by this node.
Example output for a successful deletion:
[
{
"deleted": true
}
]
Dependencies
- Requires valid credentials for the Creatio API, including URL, username, and password.
- Uses session cookies and CSRF tokens obtained via authentication to authorize requests.
- Relies on n8n's HTTP request helper to communicate with Creatio's OData endpoints.
- No additional external dependencies beyond the Creatio API and n8n environment.
Troubleshooting
- Authentication failures: Errors during login to Creatio will prevent any operation. Ensure credentials are correct and the Creatio instance is reachable.
- Invalid or missing ID: The DELETE operation requires a valid record ID. Omitting or providing an incorrect ID will cause the request to fail.
- Permission issues: The authenticated user must have permission to delete records in the specified entity.
- HTTP errors: Non-401 errors from the API will be thrown as node errors. Check the error message for details.
- Empty response handling: The node treats an empty string response as a successful deletion and returns
{ deleted: true }.