Apitable icon

Apitable

Interact with Apitable API

Actions11

Record → Record Create

AI-generated

Overview

The node enables creating new records in a specified datasheet within the Apitable platform. It is useful for automating data entry tasks, integrating external data sources, or programmatically adding information to an Apitable datasheet.

Typical use cases include:

  • Automatically adding form submission data as new records.
  • Syncing data from other applications into Apitable.
  • Batch creation of multiple records based on JSON input.

Properties

Name Meaning
Datasheet Id The unique identifier of the target Apitable datasheet where records will be created.
Records JSON array representing one or more records to create. Each record includes field keys and values.
Field Key Specifies the key type used to identify fields when querying or returning them. Options: "Name" or "Id".
Additional Fields Optional extra parameters. Currently supports:
• View Id: Limits the scope to a specific view within the datasheet.

Output

The node outputs JSON data representing the result of the record creation operation. This typically includes details about the newly created records such as their IDs and field values as stored in Apitable.

No binary data output is involved.

Dependencies

  • Requires an API authentication token credential to connect to the Apitable API.
  • Needs the base URL of the Apitable instance configured in credentials.
  • Uses internal methods to load options dynamically for Datasheets and Views.

Troubleshooting

  • Invalid Datasheet Id: If the provided datasheet ID does not exist or is incorrect, the API call will fail. Verify the datasheet ID is correct and accessible with your credentials.
  • Malformed Records JSON: The Records property expects valid JSON. Errors parsing this JSON will cause failures. Ensure the JSON syntax is correct.
  • Field Key Mismatch: Using an incorrect field key ("name" vs "id") may lead to unexpected results or errors. Confirm which key type your datasheet fields use.
  • Missing API Credentials: The node requires valid API credentials. Missing or invalid credentials will prevent successful execution.
  • View Id Issues: Specifying a non-existent or unauthorized view ID may cause errors or empty results.

Links and References

Discussion