3aa7199503
- Add Activepieces fork with SmoothSchedule custom piece - Create integrations app with Activepieces service layer - Add embed token endpoint for iframe integration - Create Automations page with embedded workflow builder - Add sidebar visibility fix for embed mode - Add list inactive customers endpoint to Public API - Include SmoothSchedule triggers: event created/updated/cancelled - Include SmoothSchedule actions: create/update/cancel events, list resources/services/customers 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
45 lines
1.3 KiB
Plaintext
45 lines
1.3 KiB
Plaintext
---
|
|
title: "Persistent Storage"
|
|
icon: 'database'
|
|
description: "Learn how to store and retrieve data from a key-value store"
|
|
---
|
|
|
|
The `ctx` parameter inside triggers and actions provides a simple key/value storage mechanism. The storage is persistent, meaning that the stored values are retained even after the execution of the piece.
|
|
|
|
By default, the storage operates at the flow level, but it can also be configured to store values at the project level.
|
|
|
|
<Tip>
|
|
The storage scope is completely isolated. If a key is stored in a different scope, it will not be fetched when requested in different scope.
|
|
</Tip>
|
|
|
|
## Put
|
|
|
|
You can store a value with a specified key in the storage.
|
|
|
|
**Example:**
|
|
|
|
```typescript
|
|
ctx.store.put('KEY', 'VALUE', StoreScope.PROJECT);
|
|
```
|
|
|
|
## Get
|
|
|
|
You can retrieve the value associated with a specific key from the storage.
|
|
|
|
**Example:**
|
|
|
|
```typescript
|
|
const value = ctx.store.get<string>('KEY', StoreScope.PROJECT);
|
|
```
|
|
|
|
## Delete
|
|
|
|
You can delete a key-value pair from the storage.
|
|
|
|
**Example:**
|
|
|
|
```typescript
|
|
ctx.store.delete('KEY', StoreScope.PROJECT);
|
|
```
|
|
|
|
These storage operations allow you to store, retrieve, and delete key-value pairs in the persistent storage. You can use this storage mechanism to store and retrieve data as needed within your triggers and actions. |