Aitable icon

Aitable

Interact with the Aitable API
Join our community

Actions6

Overview

This node interacts with the Aitable API to manage records within datasheets. Specifically, the Record - Get All operation retrieves multiple records from a selected datasheet. It supports fetching either all records or a limited number of them, making it useful for scenarios where you need to process or analyze bulk data stored in Aitable datasheets.

Common use cases:

  • Exporting all records from a datasheet for reporting or backup.
  • Fetching a subset of records for batch processing or integration with other systems.
  • Automating workflows that require reading large datasets from Aitable.

Example:
You want to retrieve all customer entries from a "Customers" datasheet to sync with your CRM system. Using this node, you can select the datasheet and choose to return all records or limit the number fetched per execution.

Properties

Name Meaning
Datasheet Select the datasheet to operate on (loaded dynamically from available datasheets).
Additional Options Collection of optional parameters:
- Limit Maximum number of records to return (minimum 1).
- Return All Boolean flag to return all records regardless of the limit set.

Output

The output is an array of JSON objects, each representing a record retrieved from the specified datasheet. Each record object contains fields as defined in the datasheet, with field names as keys and their corresponding values.

Example output structure:

{
  "json": {
    "recordId": "rec123",
    "FieldName1": "Value1",
    "FieldName2": "Value2",
    ...
  }
}

No binary data is output by this operation.

Dependencies

  • Requires an API authentication token credential for the Aitable API.
  • The node makes HTTP requests to the Aitable API endpoints to fetch datasheets and records.
  • No additional environment variables are required beyond the API credential.

Troubleshooting

  • API Errors: If the API returns an error message, it will be surfaced as Aitable API Error: <message>. Common causes include invalid API tokens, incorrect datasheet IDs, or network issues.
  • Empty Results: If no records are found, the output will be empty. Verify the datasheet ID and ensure records exist.
  • Limit vs Return All: Setting "Return All" to true ignores the "Limit" value and attempts to paginate through all records up to a maximum of 1000 due to internal limits.
  • Rate Limits: Excessive requests may hit API rate limits; consider adding delays or limiting the number of records fetched per execution.

Links and References

Discussion