Use a WhatFlow Inbox Workflow when an event starts in a system that can call your workflow endpoint. For example, a repair portal could notify a customer on WhatsApp when a repair is ready for pickup. For a Shopify-native event, start by checking whether Shopify Flow already has the trigger you need.
Inbox Workflows and WhatsApp Flows are different. Inbox Workflows run steps and decisions in the background. WhatsApp Flows are forms customers fill out inside WhatsApp.
Start with one example event
Create a workflow in Team Inbox and open Configure Triggers. Enable the API call trigger with an API key for your server-side integration. Keep the key on the server and out of screenshots, spreadsheets, storefront JavaScript and example documentation.
Use the workflow builder’s sample JSON mapping. A test event might contain these fields:
recipient: a WhatsApp test number you controlreference: a sample repair reference, such asTEST-1048stage: the event state, such asreadylocation: the pickup point shown in the customer message
Map the recipient field and use the example values to preview the rest. These are illustrative field names. Use the endpoint and request format shown for your workflow rather than assuming a universal payload.
Branch before sending
Add a decision that checks whether the repair is ready. End the other branch without sending a message. On the ready branch, choose an approved template for the pickup update and map the reference and pickup location to its variables. For business-initiated messaging, follow WhatsApp’s policy and check that the recipient can receive the message.
If the timing matters, the builder offers waits. Check whether a short delay, a scheduled timestamp, or an event from your own system makes sense. Start with no wait while you verify the mapping.
