Actions13
Overview
This node interacts with a table resource to increment or decrement the value of a specific numeric field in a record. It is useful when you need to programmatically adjust counters, quantities, or any numeric data stored in a table without manually retrieving and updating the entire record.
Practical examples include:
- Increasing the stock quantity of an item after receiving new inventory.
- Decreasing a counter each time an event occurs.
- Adjusting scores or points in a gamification system.
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. |
Column Name or ID | Choose the numeric column (field) whose value will be incremented or decremented. |
Value | The numeric amount to add (positive) or subtract (negative) from the current field value. |
Output
The node outputs JSON data representing the updated record after the increment or decrement operation. This typically includes the record's fields with their new values reflecting the change.
If the node supports binary data output, it would generally relate to attachments or files associated with the record, but this operation focuses on numeric field updates and does not produce binary output.
Dependencies
- Requires connection to the external service managing tables and records (e.g., Tulip API).
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The node dynamically loads options for tables, records, and columns based on prior selections, relying on the external service's API.
Troubleshooting
- Invalid Table/Record/Column IDs: Ensure that the selected table, record, and column exist and are accessible with the provided credentials.
- Non-numeric Field: The increment/decrement operation requires a numeric field; selecting a non-numeric column will cause errors.
- API Authentication Errors: Verify that the API key or token is valid and has sufficient permissions.
- Value Not Provided or Invalid: The "Value" property must be a number; missing or invalid input will prevent execution.
- Network Issues: Connectivity problems with the external API can cause timeouts or failures.
Links and References
- n8n Expressions Documentation
- Relevant external API documentation for managing tables and records (specific to the connected service).