Glide Apps icon

Glide Apps

Interact with Glide Apps API
Join our community

Actions17

Overview

The "Set Stash Chunk" operation for the "Stashes" resource allows users to store or update a chunk of data within a stash in Glide Apps via the Big Tables API (OpenAPI). This operation is useful when dealing with large datasets that need to be uploaded or updated incrementally in chunks. Each chunk is identified by a unique serial identifier, enabling ordered assembly of the full stash data.

Typical use cases include:

  • Incrementally uploading large JSON objects or records split into manageable parts.
  • Overwriting specific chunks of data within an existing stash without affecting other parts.
  • Managing data synchronization where partial updates are frequent.

For example, if you have a large invoice dataset, you can send it in multiple chunks labeled 1, 2, 3, etc., and the system will assemble them in order.

Properties

Name Meaning
API Type Choose which Glide API to use for this operation:
- Big Tables API (OpenAPI)
- Glide Npm Api (@glideapps/Tables)
Stash ID The identifier of the stash to set the chunk in. If the stash does not exist, it will be created automatically. Example: "20240215-job32"
Serial A unique serial identifier for the chunk of data. Chunks with the same serial overwrite previous data. Ordering of chunks is determined by sorting these serials, so use ordered values like "1", "2", etc., if order matters. Otherwise, unique random strings like "c2a4567" can be used if order is irrelevant.
Body The JSON object representing the chunk's data. It should conform to the table schema, where keys are column IDs and values are the corresponding column values. Example:
json<br>{<br> "fullName": "Alex Bard",<br> "invoiceDate": "2024-07-29T14:04:15.561Z",<br> "totalAmount": 34.5,<br> "amountPaid": 0<br>}

Output

The node outputs JSON data representing the result of setting the stash chunk. This typically includes confirmation of the stored chunk or any metadata returned by the Glide API about the stash or chunk status.

If binary data were involved (not indicated here), it would represent file contents or attachments related to the stash chunk, but this operation deals solely with JSON data.

Dependencies

  • Requires an API key credential for authenticating with the Glide Apps API.
  • Uses the Glide Big Tables API (OpenAPI) endpoint at https://api.glideapps.com.
  • The user must configure the node with appropriate credentials and select the correct API type (openapi or npm).
  • For the OpenAPI method, the node sends HTTP requests with JSON bodies.
  • For the npm method, additional usage tips are provided, but this operation is shown only for the OpenAPI type in the properties.

Troubleshooting

  • Error: Invalid Stash ID — Ensure the stash ID is correctly formatted and exists or can be created.
  • Error: Duplicate Serial Without Overwrite Intention — If overwriting is unintended, verify that serial identifiers are unique per chunk.
  • Error: Malformed JSON Body — Confirm that the JSON body matches the expected schema of the target table; invalid keys or types may cause failures.
  • Authentication Errors — Verify that the API key credential is valid and has sufficient permissions.
  • Network or API Endpoint Issues — Check connectivity to https://api.glideapps.com and ensure no firewall or proxy blocks the request.

Links and References

Discussion