beehiivZapier moves your data between apps all day. A new sale goes to the spreadsheet, a new lead goes to the CRM, a form reply goes to Slack. What it does not do is show you the running total anywhere you would glance at.
Add one more step to a Zap and it can.
How a Zap sends data to the board
Add a Webhooks by Zapier step and choose the POST event. Paste your widget’s push address as the URL and set Payload Type to JSON. Under Data, add value and map the number from an earlier step. Under Headers, add Authorization with Bearer and your key.
It sends the same request as this curl.
curl -X POST https://board.contextbolt.com/v1/push/sales \
-H "Authorization: Bearer YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"value": 249, "unit": "$"}'The unit is optional. Send $ and the widget shows the number as money.
One thing to check first. Zapier lists Webhooks by Zapier on its paid plans, so the free plan cannot run this step.
Zaps worth starting with
- Every sale: a Zap on each new payment sends its amount. Every push becomes a point on the widget’s history, so a bars widget draws your sales as they come in.
- A morning count: a Zap on a schedule finds a number in another app, like open deals or new subscribers, and sends it. A chart grows by a day each morning.
- A short report: send
textinstead ofvalue, a few lines an earlier step wrote, and the widget shows them as a report. - A list: send
items, like your open deals with their stage and amount, and a list widget shows them. Each push replaces the list, so send the whole thing.
What the board does with it
Pushes land whether the board is open or not. A value the board cannot read is refused with a reason Zapier shows on the step, and the widget keeps its last good number. Nothing bad ever turns into a zero.
The key can only send. It cannot read your board, change a widget or reach any of your connections. You can see when each key last sent data, and remove one, in Connected.