SUPPA
AI-generatedOverview
This node integrates with the Suppa API to perform CRUD operations on data tables. It supports actions such as creating a record, deleting a record by ID, retrieving records by filter or by ID, and updating records by ID. This node is useful for automating data management tasks in Suppa, such as syncing data, updating records based on external triggers, or querying data for further processing.
Use Case Examples
- Create a new record in a specified table with given data.
- Retrieve a record by its unique ID from a table.
- Update a record by ID with new data fields.
- Delete a record by its ID from a table after processing.
Properties
| Name | Meaning |
|---|---|
| Таблиця Name or ID | Select the table to perform the action on. You can choose from a list or specify an ID using an expression. |
| Action | The operation to perform on the selected table. |
| Data | JSON object containing data fields for creating or updating a record. Required for create and update actions. |
| ID запису | Unique identifier of the record for getById, updateById, or deleteById actions. |
| Фільтри | JSON object specifying filters to search records for the getByFilter action. |
| Поля для отримання | Fields to retrieve from the records when using getByFilter action. |
| Ліміт | Maximum number of results to return for getByFilter action. |
| Зміщення | Number of records to skip for getByFilter action. |
| Sort | Sorting rules for the getByFilter action, specifying columns and direction (ASC or DESC). |
Output
JSON
json- The JSON response from the Suppa API for the performed action, containing the resulting data or confirmation.
Dependencies
- Suppa API with API key authentication
Troubleshooting
- Common errors include invalid table ID or record ID, which result in API errors. Verify the IDs and ensure the API key has proper permissions.
- Malformed JSON in 'Data' or 'Filters' fields can cause request failures. Validate JSON syntax before execution.
- Network or authentication errors may occur if the API key or base URL is incorrect. Check credentials and connectivity.
Links
- n8n Expressions Documentation - Reference for using expressions in property fields.