Tulip icon

Tulip

Consume Tulip API

Actions13

Table → Create a Record

AI-generated

Overview

This node integrates with the Tulip API to create a new record in a specified table. It is useful when you want to programmatically add data entries into Tulip tables as part of an automated workflow. For example, you might use this node to log sensor readings, track production metrics, or store user input collected from other systems.

Properties

Name Meaning
Table Name or ID Select the target table by name or ID where the new record will be created.
Columns Define one or more columns and their corresponding values to set in the new record. Each column requires specifying the column name or ID and the value to assign.
  • The "Table Name or ID" property offers a dropdown list loaded dynamically from available tables.
  • The "Columns" property allows adding multiple column-value pairs, each specifying which column to populate and with what data.

Output

The node outputs JSON data representing the newly created record in the specified table. This typically includes all fields of the record as stored in Tulip after creation, such as assigned IDs and the values set for each column.

No binary data output is indicated.

Dependencies

  • Requires an active connection to the Tulip API via an API key credential.
  • The node depends on dynamic loading methods to fetch available tables and columns, so proper API access permissions are necessary.
  • No additional environment variables or external services beyond the Tulip API are required.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will prevent the node from connecting to Tulip.
    • Specifying a non-existent table or column name/ID will cause errors.
    • Providing invalid data types or empty values for required columns may result in failed record creation.

  • Error messages:

    • Authentication failures usually indicate incorrect or expired API keys; reconfigure credentials.
    • "Table not found" or "Column not found" errors suggest that the selected table or column does not exist or the user lacks permission.
    • Validation errors on column values mean the data format does not meet Tulip's requirements; verify data types and constraints.

Links and References

Discussion