Actions13
- Users Actions
- Applications Actions
- Workflows Actions
- Records Actions
Overview
This node interacts with the Ksaar API to manage records within workflows and applications. Specifically, for the Records resource and the Delete a Record operation, it deletes a record identified by its unique Record ID.
Typical use cases include:
- Automating cleanup of outdated or incorrect records in a workflow.
- Removing test or temporary data after processing.
- Managing data lifecycle by programmatically deleting records based on business logic.
For example, you might use this node to delete a user submission record from a form workflow once it has been processed or archived elsewhere.
Properties
| Name | Meaning |
|---|---|
| Send Headers | Whether to send custom HTTP headers with the request (true/false). |
| Headers | If "Send Headers" is true, specify one or more HTTP headers as key-value pairs. |
| Record ID | The unique identifier of the record to delete (required). |
Output
The output JSON contains the response from the Ksaar API after attempting to delete the specified record. Typically, this will be an object indicating success or failure of the deletion operation. The exact structure depends on the Ksaar API's delete record endpoint response.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Ksaar API via an API authentication credential configured in n8n.
- The node uses the base URL
https://api.ksaar.co/v1for all requests. - Proper permissions are needed on the Ksaar API side to delete records.
Troubleshooting
- Invalid Record ID: If the provided Record ID does not exist or is malformed, the API will likely return an error. Verify the Record ID format and existence.
- Authentication Errors: Ensure the API credential is valid and has permission to delete records.
- Network Issues: Connectivity problems can cause request failures; check network access to the Ksaar API.
- Missing Required Parameters: The Record ID is mandatory; omitting it will cause errors.
- Custom Headers Misconfiguration: If using custom headers, ensure they are correctly formatted and required by your API setup.
Common error messages may include unauthorized access, not found, or bad request errors. Review the API response message for details and adjust parameters accordingly.
Links and References
- Ksaar API Documentation (assumed official docs for further details)
- n8n documentation on Creating Custom Nodes