Pulse

What's inside

KPIs, orders and revenue charts that move with every order. Live order feed with one-click next steps. Incidents: report, acknowledge, resolve. Who is on shift, manager announcements. A rush simulation and an every-2-minutes order stream.

How its workflows run

Each one is a server workflow in your project: it runs on its trigger, with retries, and its runs show in the builder's log.

1. Keep the floor moving: new orders and next steps every two minutes

   On a schedule: schedule every 2m over order. Then: Look up region, then Create order, then Update order.

2. Simulate a rush: a burst of orders across every region

   When the app calls it: server function (manager). Then: Look up region, then Create order.

3. Alert the managers to a high or critical incident

   When a row changes: incident created. Then: Look up region, then Notify.

Set it up

It starts a new project, with its data, roles and sign-in ready.

1. Start the project

   Use the button above, or ask your coding agent with the Appbricx MCP server connected (quickstart).

2. Sign in as each role

   The demo logins open each role's home. Change what you like in plain words or in the contract.

3. Deploy

   When dev looks right, deploy. Production gets a snapshot first, so you can roll back.

Use it with your coding agent

The agent creates the project, builds it and signs in as each role.

Start a new Appbricx project from the Pulse template (slug "pulse") with use_template. Call it "My Pulse", then sign in as each role, verify it and tell me what to change first.

{
  "tool": "use_template",
  "arguments": {
    "slug": "pulse",
    "name": "My Pulse"
  }
}

appbricx templates use pulse --name "My Pulse"