Zapier
ProSend live values and menu changes from any of Zapier’s apps, and start a Zap when a screen goes offline.
Dislab’s own Zapier app is on its way. Until then, Zapier’s built-in “Webhooks by Zapier” does the same with a few more fields to fill in.
Send a live value
- Make an API key that can do Live values (see API keys).
- In your Zap, add an action: Webhooks by Zapier, event Custom Request.
- Method
PUT; URLhttps://dqeiiqecdxqguwrilond.supabase.co/functions/v1/api/v1/values/YOUR_VALUE_KEY. - Data:
{"value": 42}, with the number (or text) mapped from your trigger. - Headers:
Authorization=Bearer dsk_YOUR_KEY, andContent-Type=application/json.
The value’s own How to send it › Zapier tab in Live values has these filled in for you.
Change a menu item
The same Custom Request, with a key that can do Menus: method POST, URL https://dqeiiqecdxqguwrilond.supabase.co/functions/v1/api/v1/menus/MENU_ID/items, and Data such as {"items": [{"code": "SKU-T", "sold_out": true}]}. See Menus from your till.
Start a Zap when a screen goes offline
- In Zapier, start a Zap with the trigger Webhooks by Zapier, event Catch Hook, and copy the address it gives you.
- In Dislab, add that address under Webhooks in Settings with the events you want (such as Screen offline), and press Send a test so Zapier sees an example.
Zapier can’t check Dislab’s signature, so keep the Catch Hook address private. See Webhooks: events and signatures.
Thanks for telling us. If something’s missing, tell us what and we’ll add it.
Still stuck?
Email support@dislab.app, or send us a message. If it’s about a screen, tell us its name. We answer within one business day.