Skip to main content

Zapier Supported Storage

Zapier Supported Storage is the REST interface for Storage by Zapier, a lightweight key-value store used to persist records and share data across integrations. Its API at store.zapier.com lets you read, create, update, and delete stored records with standard GET, POST, PATCH, and DELETE requests. This connector lets Nexla ingest storage records as a data source and write records to storage as a destination.

Zapier Supported Storage icon

Power end-to-end data operations for your Zapier Supported Storage API with Nexla. Our bi-directional Zapier Supported Storage connector is purpose-built for Zapier Supported Storage, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Zapier Supported Storage or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Zapier Supported Storage workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites​

Before creating a Zapier Supported Storage credential, you need the base URL for the Storage by Zapier REST API and a store secret that identifies the storage bucket you want to work with. The API is served from https://store.zapier.com, and records are accessed under the /api/records path.

To obtain your Storage by Zapier details, follow these steps:

  1. Sign in to your Zapier account.

  2. Generate or retrieve your Storage by Zapier secret. This secret identifies your storage bucket and must use UUID formatting (32 hexadecimal characters in five hyphen-separated groups). You can create a secret when you first use the Storage by Zapier app in a Zap, and reuse the same secret to reference the same set of records.

  3. Confirm the base URL for the API. For the standard hosted service this is https://store.zapier.com, which the connector uses to construct the records endpoint.

  4. Keep your store secret confidential. Anyone with the secret can read and modify the records it protects. Each secret can hold up to 500 keys, each key can store up to 25 KB, and keys expire after three months of inactivity.

For more information about the Storage by Zapier REST API and how storage secrets and records work, see the Storage by Zapier documentation.

Authenticate​

Credentials required​

FieldRequiredSecretDescription
Base URLYesNoThe base URL for the Zapier Supported Storage API.

Create a credential in Nexla​

  1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

  2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

  3. Enter the API host in the Base URL field. For the standard hosted Storage by Zapier service, this is https://store.zapier.com. Nexla appends the /api/records path to this base URL when making requests.

  4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Your Storage by Zapier secret grants read and write access to the records it protects and should be kept confidential. For more information about the Storage by Zapier REST API, see the Storage by Zapier documentation.

Use as a data source​

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Zapier Supported Storage connector tile, then select the credential that will be used to connect to the storage API, and click Next; or, create a new Zapier Supported Storage credential for use in this flow.

Endpoint templates​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Zapier Supported Storage endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] List Storage Records

Returns a list of storage records available in the Zapier storage API. Use this template when you need to read stored key-value data for analysis, reporting, or integration purposes.

  • This endpoint issues a GET request to the records endpoint and returns the records held for the storage secret configured in your credential. Nexla organizes the returned records into one or more Nexsets.

For more information about reading records through the Storage by Zapier REST API, see the Storage by Zapier documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration​

Zapier Supported Storage data sources can also be manually configured to ingest data from any valid storage API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Zapier Supported Storage data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination​

Click the + icon on the Nexset that will be sent to the Zapier Supported Storage destination, and select the Send to Destination option from the menu. Select the Zapier Supported Storage connector from the list of available destination connectors, then select the credential that will be used to connect to the storage API, and click Next; or, create a new Zapier Supported Storage credential for use in this flow.

Endpoint templates​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Zapier Supported Storage endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

[Rest API] Set Storage Record

Create or update a storage record in the Zapier storage API. Use this template when you need to write records to storage based on data from your Nexla flows.

  • This endpoint sends each record from your Nexset as a JSON POST request to the records endpoint to create or update a stored record. The request body carries the record data in the format required by the storage API.

For more information about writing records through the Storage by Zapier REST API, see the Storage by Zapier documentation.

[Rest API] Update Storage Record

Update an existing storage record in the Zapier storage API. Use this template when you need to modify records that already exist in storage using data from your Nexla flows.

  • This endpoint sends each record from your Nexset as a JSON PATCH request to the records endpoint to update an existing stored record. The request body carries the fields to be updated in the format required by the storage API.

For more information about updating records through the Storage by Zapier REST API, see the Storage by Zapier documentation.

[Rest API] Delete Storage Record

Delete a storage record from the Zapier storage API. Use this template when you need to remove records from storage as part of your Nexla flows.

  • This endpoint issues a DELETE request to the records endpoint to remove a stored record. Use this template with care, as deleting a record permanently removes it from storage.

For more information about deleting records through the Storage by Zapier REST API, see the Storage by Zapier documentation.

Manual configuration​

Zapier Supported Storage destinations can also be manually configured to send data to any valid storage API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Save & activate​

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Zapier Supported Storage endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Zapier Supported Storage endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.