Caspio icon

Caspio

Caspio API
Join our community

Actions10

Overview

The Caspio Row GetAll operation node retrieves multiple records from a specified Table or View in your Caspio account. It allows you to filter, sort, group, and paginate the results using various options. This node is useful for scenarios where you need to extract large datasets from Caspio for further processing, reporting, or integration with other systems.

Common use cases:

  • Exporting all customer records from a Caspio table for analysis.
  • Fetching filtered lists of orders based on status or date range.
  • Integrating Caspio data into other workflows by retrieving batches of rows.

Properties

Name Type Meaning
Table/View Name String Name of the Table or View from which to retrieve rows.
Is View Boolean If true, retrieves rows from a View instead of a Table.
Options Collection Additional query options (see below).
└ Select String Comma-separated list of fields to include in the result.
└ Where String SQL-like WHERE clause to filter records.
└ Group By String GROUP BY clause to aggregate results.
└ Order By String ORDER BY clause to sort results.
└ Limit Number Maximum number of records to return (max 1000, default 100).
└ PageNumber Number Page number for paginated results (used with PageSize).
└ PageSize Number Number of records per page (5–1000, used with PageNumber; default 25).

Output

  • The output is an array of items, each with a json property containing a single record from the Caspio Table or View.
  • Each json object contains key-value pairs corresponding to the fields of the retrieved row.
  • No binary data is produced by this operation.

Example output:

[
  {
    "json": {
      "ID": 1,
      "Name": "John Doe",
      "Email": "john@example.com"
    }
  },
  {
    "json": {
      "ID": 2,
      "Name": "Jane Smith",
      "Email": "jane@example.com"
    }
  }
]

Dependencies

  • External Service: Requires access to a Caspio account and the Caspio API.
  • Credentials: n8n Caspio credentials must be configured with appropriate API keys or tokens.
  • Environment: No special environment variables are required beyond 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. Double-check the spelling and existence in Caspio.
  • API Authentication Errors: If credentials are missing or invalid, authentication errors will occur. Ensure that Caspio credentials are correctly set up in n8n.
  • Limit Exceeded: If you request more than 1000 records without pagination, only up to 1000 will be returned due to API limits.
  • Malformed Query Clauses: Incorrect syntax in Where, Group By, or Order By may cause API errors. Validate your clauses before running.

Error messages:

  • "No binary data exists on item!": Not applicable for this operation, but may appear if misconfigured.
  • "No binary data property ... does not exists on item!": Not applicable for this operation.
  • Other errors will typically reflect Caspio API responses (e.g., authentication failures, invalid queries).

Links and References

Discussion