How I Built an Embedded Chatwoot Dashboard App for 1-Click Webhook Runbooks & Ticket Spikes

Description and use

ProfitPilot is an embedded Chatwoot dashboard app that enables 1‑click runbooks to automatically apply labels, attributes, messages, and external webhooks in a deterministic order with retries, while giving managers real‑time metrics during ticket spikes.

Problem

High-volume ticket spikes expose three bottlenecks: no outbound webhooks in native macros, lack of deterministic execution order with retries, and limited spike triage visibility.

Outcome

ProfitPilot enables 1‑click runbooks that automatically apply labels, set attributes, post notes, and trigger external webhooks in a deterministic, retry‑enabled order, while providing real‑time spike triage metrics—all embedded within Chatwoot’s UI.

Workflow

• Open ticket in Chatwoot
• ProfitPilot receives conversation context
• Agent selects a 1‑click runbook
• Runbook job queued in BullMQ
• Worker executes steps in order: add_label → set_attribute → send_message → http_webhook
• If a step fails, subsequent steps resume without duplication
• Runbook completes and logs metadata
• Managers view real‑time metrics via embedded dashboard

Evidence

During high-volume ticket spikes—like a product launch, a billing issue, or a server outage—support teams quickly run into three workflow bottlenecks

Source

ProfitPilot uses Chatwoot's Dashboard App architecture to render directly inside the agent conversation view

Source

BullMQ + Redis Worker Queue (Ordered step execution + idempotent retries)

Source

ProfitPilot never stores customer conversation bodies or message text

Source