beehiivA Make scenario can do a lot in one run. Pull yesterday’s orders, sort them, update a sheet, ping a channel. Then the result disappears into a scenario history you never open.
Send the one number you care about to a board instead.
How a scenario sends data to the board
At the end of the scenario, add the HTTP app’s Make a request module. Set the method to POST and the URL to your widget’s push address. Add a header named Authorization with the value Bearer and your key. Choose application/JSON as the body content type and send the number, mapped from an earlier module.
It is the same request as this curl.
curl -X POST https://board.contextbolt.com/v1/push/orders \
-H "Authorization: Bearer YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"value": 1204}'Make lets you build the body as a data structure or type it as a JSON string. A data structure with one field called value is the easy one, because Make escapes it for you.
Scenarios worth starting with
- Orders every morning: a scheduled scenario counts yesterday’s orders from your store and sends the count. The chart gains a point each morning.
- Form replies: a scenario gathers the newest replies to your form and sends them as
items, each with a name and a line of detail. Each push replaces the list, so send the newest few every time. - Open tickets: a scenario counts open tickets in your help desk every hour and sends the number. Within a week it is a trend.
- A morning report: send
text, a few lines an earlier module wrote, and the widget shows them as a short report.
What the board does with it
Pushes land whether the board is open or not, and each number becomes a point on the widget’s history. A value the board cannot read is refused with a reason in the reply, which the module’s output shows. The widget keeps its last good number. It never shows a zero it did not get.
The key can only send. It cannot read your board, change a widget or reach your connections. Remove it in Connected any time, and anything using it stops at once.