Simple Counter

It includes a dashboard with one large counter value and three actions: increment, decrement, and reset. The counter is stored with plugin_context.store so the value persists per business instead of resetting on every reload. This template is meant to demonstrate a minimal read/write pattern, not a full workflow app.

Use it when you want a very small starter example for key-value persistence, button actions, and a single dashboard state. It is useful for validating plugin behavior, testing save/load logic, or creating a lightweight shared counter. If you need records, permissions, notifications, or audit history, this template is too small for that use case.

The counter persists whenever a user clicks one of the buttons and the app writes the updated value to the store. Because the template is scoped per business, everyone in that business sees the same saved value unless you customize the storage key. Access control is not the focus here, so if you need role-based editing you should add permissions before rollout.

No. Simple Counter does not track regulated records, personal data workflows, or audit-heavy operational events. It is a demo of state persistence and should not be used for incident logs, visitor records, or other compliance-sensitive processes without major redesign.

The most common mistake is treating it like a production workflow app when it only stores one number. Another pitfall is forgetting to define the default value, which can make the dashboard look broken on first open. Teams also sometimes overwrite the same key from multiple places without deciding who owns the counter.

Yes. You can change the label, add limits, rename the buttons, or use the same storage pattern for other single-value states such as a queue count or availability tally. If you need multiple counters, define separate keys and make sure the UI clearly shows which value each control affects.

The template itself is focused on local key-value persistence, but you can wire the counter value into notifications or downstream automations if your app platform supports them. A common extension is to trigger a message when the value reaches a threshold. Keep the first version simple so you can confirm the store behavior before adding integrations.

Start by assigning one owner to confirm the expected default value, storage key, and reset behavior. Then test increment, decrement, and refresh across a few users to verify the saved state is shared the way you expect. Once that works, decide whether the counter is informational only or whether it needs permissions and change tracking.