SUPPA 2.0 icon

SUPPA 2.0

Get data from Suppa API

SUPPA 2.0

AI-generated

Overview

This node integrates with the Suppa API to perform various data operations on selected tables. It supports actions such as creating a new 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 within the Suppa platform, such as syncing data, updating records based on external triggers, or querying data for further processing.

Use Case Examples

  1. Create a new record in a specified table with given JSON data.
  2. Retrieve a record by its unique ID and select specific fields to return.
  3. Update an existing record by ID with new data provided in JSON format.
  4. Delete a record by its ID from a specified table to maintain data hygiene.

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. Options include create, delete by ID, get by filter, get by ID, and update by ID.
Data JSON object containing data for creating or updating a record. Required for create and update actions.
ID запису Unique identifier of the record for get by ID, update by ID, or delete by ID actions.
Поля для отримання Fields to retrieve from the record(s). Can be selected from a list or specified by IDs using expressions. Applies to get by ID and get by filter actions.
Фільтри JSON object specifying filter criteria to find records. Used in get by filter action.
Ліміт Maximum number of results to return. Used in get by filter action.
Зміщення Number of records to skip before starting to return results. Used in get by filter action.
Sort Sorting rules for the results, specifying columns and direction (ASC or DESC). Used in get by filter action.

Output

JSON

  • json - The output data from the Suppa API action, which can be a single record or an array of records depending on the action performed.

Dependencies

  • Requires Suppa API credentials for authentication.

Troubleshooting

  • Ensure the Suppa API credentials are correctly configured and valid to avoid authentication errors.
  • Verify that the table name or ID specified exists in the Suppa schema to prevent errors when loading table fields or performing actions.
  • When using filters or fields, ensure the JSON syntax is correct to avoid parsing errors.
  • If an unsupported action is specified, the node will throw an error indicating an unknown action.

Discussion