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, the "Update a Record" operation allows users to modify an existing record by specifying the record ID, user email, and fields to update. This is useful in scenarios where data collected or stored in Ksaar needs to be programmatically updated based on external triggers or workflow automation.
Practical examples include:
- Updating customer information in a form submission record after receiving new data.
- Modifying status or other field values of a record as part of a multi-step automation process.
- Correcting or enriching data in a record without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Send Headers | Boolean flag to indicate whether custom HTTP headers should be sent with the request. |
| Headers | Collection of custom HTTP headers (name-value pairs) to send if "Send Headers" is enabled. |
| Application | The application context in which the record exists; can be selected from a list or specified by ID. Required. |
| Workflow | The workflow context related to the record; selectable from a list or specified by ID. Required. |
| Record ID | The unique identifier of the record to update. Required. |
| User | The user associated with the record, identified by email or selected from a list. Required. |
| Fields | A collection of fields to update on the record. Each field includes: |
| - Field: The specific field to update, selectable from a list or by ID. Required. | |
| - Value: The new value to set for the field. Required. |
Output
The output is a JSON array containing the response from the Ksaar API after updating the record. This typically includes the updated record's details reflecting the changes made.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Ksaar API.
- The node uses the Ksaar API base URL
https://api.ksaar.co/v1. - Proper configuration of resource locators for Application, Workflow, User, and Fields is necessary to correctly identify entities.
Troubleshooting
- Invalid IDs or Emails: The node validates UUID formats for IDs and proper email format for the user email. Errors will occur if these are invalid. Ensure correct formatting.
- Missing Required Parameters: All required fields such as Application, Workflow, Record ID, User Email, and Fields must be provided. Omitting any will cause errors.
- API Authentication Errors: If the API key credential is missing or invalid, authentication errors will occur. Verify that the API key is correctly configured.
- Field Update Failures: If a field ID does not exist or the value is incompatible with the field type, the API may reject the update. Confirm field existence and valid values.
- Network Issues: Connectivity problems to the Ksaar API endpoint will result in request failures. Check network access and proxy settings if applicable.
Links and References
- Ksaar API Documentation (Assumed official docs for further details)
- n8n Resource Locator documentation for configuring resource selectors in nodes.