Overview
The Caspio node for n8n allows you to interact with Caspio's API, specifically to update rows in a specified Table or View. The "Row - Update" operation lets you modify existing records by specifying which fields to change and applying a WHERE clause to target the correct records.
Common scenarios:
- Updating user information in a Caspio table based on an email address.
- Bulk updating status fields for records that match certain criteria.
- Automating data corrections or enrichment in your Caspio database from other workflows.
Example use case:
You have a workflow where customer support updates ticket statuses in Caspio when a related event occurs in another system. This node can be used to find the relevant tickets (using the WHERE clause) and update their status field.
Properties
| Name | Type | Meaning |
|---|---|---|
| Table/View Name | String | Name of the Table or View in Caspio where the row(s) will be updated. |
| Is View | Boolean | If true, operates on a View instead of a Table. |
| Data to Send | Options | Determines how data is provided for the update; for this operation, only "Define Below for Each Column" is supported. |
| Where | String | SQL-like WHERE clause to specify which row(s) to update. |
| Fields to Send | FixedCollection | List of fields and their new values to set in the matched row(s). Each entry includes: - Field Name: The column to update. - Field Value: The new value to assign. |
Output
- The output is a JSON object containing the result of the update operation as returned by the Caspio API.
- The structure typically reflects the updated record(s), but the exact format depends on Caspio's response.
- Example output:
{
"Field1": "newValue1",
"Field2": "newValue2",
...
}
- No binary data is produced by this operation.
Dependencies
- External Service: Requires access to a Caspio account and its API.
- Credentials: You must configure Caspio API credentials in n8n under the name
caspio. - Environment: No special environment variables are required beyond standard n8n credential setup.
Troubleshooting
Common issues:
- Invalid Table/View Name: If the specified table or view does not exist, the node will throw an error.
- Incorrect WHERE Clause: If the WHERE clause is malformed or does not match any records, no rows will be updated.
- Missing Field Values: If no fields are specified to update, the request may fail or do nothing.
- Authentication Errors: Invalid or expired Caspio credentials will cause authentication failures.
Error messages and resolutions:
"No binary data exists on item!"– Not applicable for this operation, but indicates a missing binary property in other operations."No binary data property ... does not exists on item!"– Also not applicable here.- General API errors: Any error message from Caspio will be passed through; check the message for details such as permission issues or invalid input.