Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Storage

Store or retrieve data from key/value database

CategoryCore
AuthenticationNo authentication required
Version0.6.20
Published scopes0 published scopes
Last updatedSeptember 30, 2026

Overview

Connect Storage with Flows360

Store or retrieve data from key/value database

Use the Storage connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 6 actions and no declared triggers.

Available actions

  • Get
  • Put
  • Append
  • Remove
  • Add To List
  • Remove from List

Available triggers

  • No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Storage
  • Package: @activepieces/piece-store@0.6.20
  • Exact artifact digest: sha256:b48422058543c7a2a92c64e86515659c3f25510b3756b8a5e9e67c97d1cc58c0
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

No connection authentication is declared by the package. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Get (get), Get a value from storage Classification: read.
  • Put (put), Put a value in storage Classification: read.
  • Append (append), Append to a value in storage Classification: read.
  • Remove (remove_value), Remove a value from storage Classification: read.
  • Add To List (add_to_list), Add Items to a list. Classification: read.
  • Remove from List (remove_from_list), Remove Item from a list Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

AuthenticationNo authentication required
Supported objects6
Supported actions6
TriggersNone published

Authentication

Authentication method: No authentication required

Supported objects

ObjectReadWriteNotes
Get Yes No Get a value from storage
Put Yes No Put a value in storage
Append Yes No Append to a value in storage
Remove Yes No Remove a value from storage
Add To List Yes No Add Items to a list.
Remove from List Yes No Remove Item from a list

Supported actions

Get · Read

Get a value from storage

get · Risk: low · Retry: safe

Inputs

  • key · string · Required
  • defaultValue · string · Optional
  • store_scope · string · Required, The storage scope of the value.
Put · Read

Put a value in storage

put · Risk: low · Retry: safe

Inputs

  • key · string · Required
  • value · string · Required
  • store_scope · string · Required, The storage scope of the value.
Append · Read

Append to a value in storage

append · Risk: low · Retry: safe

Inputs

  • key · string · Required
  • value · string · Required
  • separator · string · Optional, Separator between added values, use for newlines
  • store_scope · string · Required, The storage scope of the value.
Remove · Read

Remove a value from storage

remove_value · Risk: low · Retry: safe

Inputs

  • key · string · Required
  • store_scope · string · Required, The storage scope of the value.
Add To List · Read

Add Items to a list.

add_to_list · Risk: low · Retry: safe

Inputs

  • key · string · Required
  • value · array · Required
  • ignore_if_exists · boolean · Optional
  • store_scope · string · Required, The storage scope of the value.
Remove from List · Read

Remove Item from a list

remove_from_list · Risk: low · Retry: safe

Inputs

  • key · string · Required
  • value · string · Required
  • store_scope · string · Required, The storage scope of the value.

Setup

Setup

  1. Add the Storage connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-store@0.6.20; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 0 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Storage connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-store@0.6.20 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com