AppSheet

Interact with the AppSheet API to add, read, update, delete records, or invoke a custom action on table records.

Actions5

Overview

The AppSheet node for n8n allows you to interact with the AppSheet API, specifically to read records from a specified table using a selector expression. This is useful for retrieving filtered data from your AppSheet applications based on custom criteria.

Common scenarios:

  • Fetching all users over a certain age from a "People" table.
  • Retrieving orders that match specific status or date ranges.
  • Integrating AppSheet data into automated workflows for reporting or further processing.

Practical example:
Suppose you have an AppSheet app managing employee data. You can use this node to fetch all employees in a particular department or those who joined after a certain date, and then process or export that data within your n8n workflow.

Properties

Name Type Meaning
Region options The AppSheet region domain to use in the API URL (e.g., Global or EU).
Table Name string Name of the AppSheet table to query (should be URL-encoded if needed).
Selector string A valid AppSheet selector expression to filter which records are returned.
Locale string Locale used for formatting dates and numbers (e.g., en-US).
Location string Geographical coordinates for context (e.g., 47.623098, -122.330184).
Timezone string Timezone used for date/time formatting (e.g., Pacific Standard Time).

Output

The node outputs the result of the AppSheet API's "Find" action as an array of JSON objects, each representing a record from the queried table that matches the selector.

Output structure example:

[
  {
    "Column1": "Value1",
    "Column2": "Value2",
    "...": "..."
  },
  ...
]
  • Each object contains key-value pairs corresponding to the columns and values of the matching records in your AppSheet table.

Dependencies

  • External Service: Requires access to the AppSheet API.
  • API Key: You must provide AppSheet API credentials (appId and apiKey) via n8n's credential system.
  • n8n Configuration: No special environment variables required beyond standard credential setup.

Troubleshooting

Common issues:

  • Invalid JSON format in input fields: If the selector or other parameters are not formatted correctly, the node may throw errors.
  • Authentication errors: Incorrect or missing API credentials will prevent successful requests.
  • Selector syntax errors: An invalid selector expression will cause the API to return an error.

Error messages and resolutions:

  • "Operation \"read\" not supported!"
    Resolution: Ensure you selected a valid operation ("Read Records").
  • "Invalid JSON format in ..."
    Resolution: Double-check that any JSON input (if required) is properly formatted.
  • API returns empty results:
    Resolution: Verify your selector expression matches existing records in the table.

Links and References

Discussion