Actions13
Overview
This node integrates with the Tulip API to update a specific record in a chosen table. It is useful when you want to modify existing data entries programmatically within Tulip tables, such as updating inventory counts, changing status fields, or correcting data errors.
Practical examples include:
- Updating a product's stock quantity after a sale.
- Changing the status of a work order in a manufacturing process.
- Correcting user information stored in a table.
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 table to update by name or ID. |
| Columns | Define one or more columns to update with new values. Each column requires: |
| - Column Name or ID | The name or ID of the column to update. |
| - Value | The new value to set for the specified column. |
Output
The node outputs JSON data representing the updated record from the Tulip table. This typically includes the record's fields with their new values reflecting the update operation.
If the node supports binary data output (not indicated here), it would represent any file or media 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 being accessible and the provided credentials having permission to update records.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common Issues:
- Invalid or missing Table ID or Record ID will cause the update to fail.
- Providing incorrect column names or IDs that do not exist in the selected table will result in errors.
- Insufficient permissions on the API key can prevent updates.
- Network connectivity issues may cause timeouts or failures.
Error Messages:
- "Record not found" indicates the specified record ID does not exist in the table.
- "Invalid column name" means one or more specified columns are not recognized.
- Authentication errors suggest problems with the API key or its permissions.
Resolutions:
- Verify table and record identifiers are correct and exist.
- Double-check column names against the table schema.
- Ensure the API key has update permissions.
- Confirm network connectivity and API endpoint availability.
Links and References
- Tulip API Documentation (general reference for API capabilities)
- n8n Expressions Documentation (for dynamic property values)