Tulip icon

Tulip

Consume Tulip API

Actions13

Table → Update a Record

AI-generated

Overview

This node interacts with a Table resource in the Tulip API, specifically allowing users to update an existing record within a specified table. It is useful when you need to modify data entries dynamically based on workflow logic, such as updating inventory counts, changing status fields, or correcting information in a database table.

For example, you might use this node to update a customer record with new contact details after receiving updated information from a form submission, or to change the status of a work order in a manufacturing process.

Properties

Name Meaning
Table Name or ID Select the target table by name or ID where the record exists.
Record Name or ID Select the specific record within the chosen table to update by name or ID.
Columns Define one or more columns to update in the selected record. For each column:
- Column Name or ID Choose the column to update by name or ID.
- Value Specify the new value to set for the selected column.

The "Table Name or ID", "Record Name or ID", and "Column Name or ID" fields support dynamic expressions and loading options based on previous selections, ensuring that only valid tables, records, and columns are selectable.

Output

The node outputs JSON data representing the updated record after the operation completes successfully. This typically includes the record's ID and the new values of the updated columns, reflecting the changes made.

If the node supports binary data output (not indicated here), it would represent any file or media content associated with the record, but this node focuses on JSON data updates.

Dependencies

  • Requires an active connection to the Tulip API via an API key credential.
  • The node depends on the Tulip API endpoints for tables, records, and columns to fetch options and perform updates.
  • Proper permissions on the API key are necessary to read tables/records and perform update operations.

Troubleshooting

  • Common Issues:

    • Selecting a non-existent table, record, or column will cause errors; ensure IDs or names are correct.
    • Insufficient API permissions can result in authorization errors.
    • Providing invalid data types or empty values for required columns may cause the update to fail.

  • Error Messages:

    • "Record not found" — Verify the record ID or name is correct and belongs to the selected table.
    • "Unauthorized" or "Forbidden" — Check that the API key has the necessary permissions.
    • "Invalid input" — Ensure all required columns have valid values and data types.

Resolving these usually involves verifying input parameters, checking API credentials, and confirming the existence of referenced resources.

Links and References

Discussion