Webhooks
Webhooks send a signed message to an address of yours each time something you picked happens on the floor. Your ERP, a chat channel or a tool like Zapier, Make or n8n can react at once, without asking Floormode every few minutes. The messages follow Standard Webhooks.
You will find them in Settings → Apps & API → Webhooks. Like the REST API, they work on every plan.
On this page
Section titled “On this page”- Add an endpoint
- Events
- Only some warehouses or stores
- The signing secret
- Deliveries
- Not delivered
- Switched off
- Replay, Send again, Send a sample
- Event feeds
- See also
Add an endpoint
Section titled “Add an endpoint”Click Add endpoint, paste an https:// address, pick the events and click Add endpoint. An account can have up to 10 endpoints.
Floormode only sends to public addresses. An address on a private or local network is refused, before it is saved and again before every message. Your system should respond 2xx within 10 seconds.
Events
Section titled “Events”The events come in seven groups: Orders, Fulfilment, Shipping, Inventory, Returns, Warehouse and Alerts. Open a group to tick single events, or use Select group. Each event says in one sentence when it is sent, and search finds an event by its name or its API name (order.allocated). The event catalogue shows what each one carries, with an example.
Messages about the same order arrive in the order they happened, and each carries a sequence number. Every message has an id (webhook-id): if one ever arrives twice, skip it.
A message carries ids, short ids, order, warehouse and store names, statuses and counts. It never carries a customer’s name, email, address or phone, nor a note someone typed. Your system reads the details through the REST API with its own access.
Only some warehouses or stores
Section titled “Only some warehouses or stores”Open Only some warehouses or stores to receive events from some warehouses or stores only. Leave a field empty to receive from all of them. An event that has no warehouse (or no store) is never sent while that filter is set, and the event list greys it out and says why.
The signing secret
Section titled “The signing secret”When you add an endpoint, Floormode shows its signing secret (whsec_…) once. Copy it now: Floormode keeps only a locked copy and cannot show it again. Your system checks the webhook-signature header with it, so it knows each message came from Floormode.
Make a new secret (in the endpoint’s ⋯ menu) shows a new one, once. For 24 hours every message carries both signatures, so your system can switch over at its own pace. Making yet another new secret inside those 24 hours stops the oldest one at once.
Deliveries
Section titled “Deliveries”An endpoint’s page lists every event it was sent, newest first:
- Pending: waiting to be sent, or held while the endpoint is off.
- Retrying: your system did not accept it; Floormode tries again, on growing intervals, for up to 3 days.
- Delivered: your system responded 2xx.
- Failed: refused, or no try left. Send again sends it once more.
Search by event or by an order’s name. Floormode keeps events for 5 days. A page reads back a stretch of that time; Load older reads further back, and the line under the list says how far it has checked.
Not delivered
Section titled “Not delivered”When events could not be delivered before Floormode stopped keeping them, the list shows one Not delivered row with the period. Nothing is lost on your side silently: read what changed in that period through the REST API.
Switched off
Section titled “Switched off”You can switch an endpoint off in its ⋯ menu. Floormode switches it off by itself, and says why, when:
- 20 deliveries in a row were refused;
- the address responded
410 Gone; - no delivery succeeded for 3 days;
- the address points to a private or local network.
Switch on… asks where to start: Send what is still kept sends every event since it stopped (oldest first, then new ones), From now sends only new events. When the address itself was the fault, Edit address… comes first.
Replay, Send again, Send a sample
Section titled “Replay, Send again, Send a sample”- Replay from… sends every kept event since a time again, oldest first.
- Send again sends one failed delivery again.
- Send a sample sends a test message, marked
"test": true.
Replayed and resent events keep their ids (webhook-id), so your system can recognise an event it already has.
Event feeds
Section titled “Event feeds”An event feed lets an agent or a script read events through the API at its own pace, with no address of its own for Floormode to call. Choose a feed over an endpoint when nothing of yours is always online, or when an AI agent does the reading.
Open the Event feeds tab and click Add feed. Give it a name, pick the events and, if you want, Only some warehouses or stores, then choose where it starts:
- From now reads only events from this moment on.
- From the oldest kept event starts with what Floormode still keeps. Floormode keeps 5 days of the events an endpoint or feed receives. Events from before any endpoint or feed listened, or from while this feed had expired, were never kept, so no feed can read them.
Feed added shows the Feed URL. Copy it into your agent or script. It is an address, not a password: every read needs the reader’s own API login, and each reader sees only the events its own role and warehouses may see. A reader without access to orders reads no order events from the same feed.
A feed expires 30 days after its last read. The list shows Last read for each feed, and a badge when a feed ends within 7 days or has expired. Renew gives it 30 more days from now. Copy feed URL and Delete feed are in the row’s ⋯ menu. An account can have up to 10 feeds.
See also
Section titled “See also”- REST API — read the details a message points to.
- Integration health — the other apps Floormode talks to.
- Shopify Flow — the same events as triggers for your Flow workflows.