SeaTable icon

SeaTable

Consume the SeaTable API

Base → API Call

AI-generated

Overview

This node allows users to make custom API calls to the SeaTable Base API. It supports HTTP methods such as POST, GET, PUT, and DELETE, enabling users to interact with SeaTable's Base operations programmatically. Typical use cases include fetching data, updating records, deleting entries, or creating new data within a SeaTable base by specifying the API endpoint, query parameters, and request body as needed.

Use Case Examples

  1. A user wants to retrieve a list of rows from a specific table by making a GET request to the appropriate SeaTable API endpoint with query parameters.
  2. A user needs to update a record in SeaTable by sending a PUT request with a JSON body containing the updated data.
  3. A user wants to delete a specific entry by making a DELETE request to the corresponding API endpoint.

Properties

Name Meaning
HTTP Method The HTTP method to use for the API call (POST, GET, PUT, DELETE). This determines the type of operation performed on the SeaTable API.
URL The API endpoint URL to call. It must start with /api-gateway and corresponds to the SeaTable Base API operations that use Base-Token authentication.
Query String Parameters Key-value pairs to be URL-encoded and appended to the API request URL. Used to filter or specify parameters for the API call.
Body The JSON body to send with the request. Must be valid JSON and can include variables from n8n. Used mainly for POST and PUT requests to send data.
Response Object Parameter Name Optional parameter name to extract a specific object from the API response. If left empty, the entire response is returned.

Output

JSON

  • response - The full JSON response from the SeaTable API call, or a specific object within it if a response object parameter name is provided.

Dependencies

  • Requires an API key credential for SeaTable Base authentication (Base-Token).

Troubleshooting

  • Ensure the URL starts with /api-gateway as required by the SeaTable Base API.
  • Verify that the HTTP method matches the intended operation and that the request body is valid JSON when required.
  • Check that the Base-Token authentication is correctly configured and included automatically as noted.
  • If the response object parameter name is specified, ensure it matches a valid key in the API response to avoid empty or undefined outputs.

Links

Discussion