Overview
The Caspio node for n8n allows you to interact with Caspio's API, specifically to retrieve records (rows) from a specified Table or View within your Caspio account.
With the Row → Get operation, you can fetch one or more records from a chosen Table or View, optionally filtering and customizing the returned data using various query options.
Common scenarios:
- Fetching specific records from a Caspio Table or View based on custom filters.
- Integrating Caspio data into automated workflows for reporting, synchronization, or further processing.
- Building dashboards or notifications that rely on up-to-date Caspio data.
Practical example:
You might use this node to retrieve all customer records where the status is "Active" from a "Customers" table, then send personalized emails or update another system.
Properties
| Name | Type | Meaning |
|---|---|---|
| Table/View Name | String | Name of the Table or View in Caspio from which to retrieve rows. |
| Is View | Boolean | If enabled, retrieves rows from a View instead of a Table. |
| Options → Select | String | Comma-separated list of fields to return in the result. |
| Options → Where | String | SQL-like WHERE clause to filter which records are retrieved. |
| Options → Group By | String | GROUP BY clause to group results by specified fields. |
| Options → Order By | String | ORDER BY clause to sort the results. |
| Options → Limit | Number | Maximum number of records to return (default 100, max 1000). |
| Options → PageNumber | Number | Page number for paginated results (used if PageSize is set; default 1). |
| Options → PageSize | Number | Number of records per page (5–1000; used with PageNumber for pagination; default 25 if PageNumber is set). |
Output
- The output is an array of items, each with a
jsonproperty containing the data for a single record retrieved from the specified Table or View. - Each
jsonobject contains key-value pairs corresponding to the fields of the Table or View. - No binary data is produced by this operation.
Example output:
[
{
"json": {
"ID": 123,
"Name": "John Doe",
"Status": "Active"
}
},
{
"json": {
"ID": 124,
"Name": "Jane Smith",
"Status": "Active"
}
}
]
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. - n8n Configuration: No special environment variables required beyond standard credential setup.
Troubleshooting
Common issues:
- Invalid Table/View Name: If the specified Table or View does not exist, the node will throw an error.
- Authentication Errors: Incorrect or missing Caspio credentials will prevent the node from connecting.
- Query Syntax Errors: Malformed WHERE, GROUP BY, or ORDER BY clauses may cause errors from the Caspio API.
- Limit Exceeded: Setting the Limit above 1000 will not return more than 1000 records due to API constraints.
Error messages and resolutions:
"No binary data exists on item!": This should not occur for the Row/Get operation, but indicates a misconfiguration if seen."No binary data property ... does not exists on item!": Not applicable for this operation.- API Error Messages: Any error message returned by Caspio (e.g., invalid field names, authentication failure) will be shown in the
errorfield of the output if "Continue On Fail" is enabled.