VanAnTravel Connector

VanAnTravel advanced connector with dynamic field loading and smart filtering
Join our community

Actions5

Overview

This node interacts with the VanAnTravel Connector API to manage records in a table within an application. It supports operations such as creating, retrieving (single or multiple), updating, and deleting records. It is useful for automating data management tasks in applications that use the VanAnTravel platform, such as syncing data, updating records based on external triggers, or fetching records for processing.

Use Case Examples

  1. Create a new record in a specified table by mapping fields dynamically or sending raw JSON data.
  2. Retrieve a specific record by its ID to use its data in subsequent workflow steps.
  3. Fetch multiple records with advanced filtering, sorting, and pagination options for bulk processing.
  4. Update an existing record by specifying the record ID and new field values, either dynamically or as raw JSON data.

Properties

Name Meaning
Tenant Access Token The tenant access token for authentication (starts with t-)
App Token The app token for the application (starts with app)
Table ID The ID of the table (starts with tbl)
Record ID The ID of the record (starts with rec), required for get, update, and delete operations

Output

JSON

  • code - Response status code from the API, 0 indicates success
  • msg - Response message from the API, typically 'success' if no error
  • data
    • items
      * ``
      * record_id - The unique identifier of the record
      * fields - The fields and their values of the record
    • has_more - Indicates if there are more records available when fetching multiple records
    • page_token - Token for pagination to fetch the next set of records
    • total - Total number of records returned in a getAll operation

Dependencies

  • Requires an API authentication token (tenant access token) and an application token for authorization to the VanAnTravel API.

Troubleshooting

  • Ensure that the tenant access token and app token are correctly provided and valid; invalid tokens will cause authentication errors.
  • When providing JSON in the 'fields' parameter for create or update operations, ensure the JSON is valid to avoid parsing errors.
  • If the record ID is missing or incorrect for get, update, or delete operations, the API will return an error indicating the record was not found.
  • For getAll operation, improper filter expressions or invalid field names in filters may cause the API to reject the request.
  • Network or API endpoint issues may cause request failures; verify connectivity and API availability.

Links

Discussion