GuidePlatformv1
Keyvalue Storage
Persistent key/value storage between runs — for dedup keys, counters, cross-system ID maps, and caches.
Between-run persistence. Write a value, read it the next time the automation runs, delete it when you're done. Scoped to the automation, account, tenant, or system.
Use cases
- Dedup keys — record what you've processed (order IDs, record hashes) so you don't process the same thing twice.
- Counters — running totals, rate-limit tallies, per-day usage.
- Cross-system ID maps — pair entity IDs across systems (HubSpot contact ID ↔ Salesforce account ID, etc.) so later runs can resolve them without re-querying.
- Small caches — any run-to-run state that doesn't belong in an external database.
Actions
- Get — read a key; returns empty if not set.
- Set — write a key. Optionally with an expiration (TTL) after which the key auto-deletes.
- Delete — remove a key explicitly.
Scope
| Scope | Visibility | Use when |
|---|---|---|
| Automation | Only this automation | Per-automation state (dedup keys, run counters) |
| Account | All automations in the account | Shared state across automations (cross-system ID maps) |
| Tenant | All accounts in the tenant | Tenant-wide counters |
| System | Everything on the server | Platform-level shared state (rare) |
Pick the narrowest scope that covers your use case.
Related docs
Last updated May 4, 2026