Automations

Let the system do
the repetitive work.

Rules that react to every event —a sale, a receipt, a low-stock alert—, plus webhooks and an API to connect your stack. What you do by hand today, copying data from one screen to another, now happens on its own.

20-min personalized demo · No commitment · Works with n8n, Zapier and Make

Operations manager reviewing automated flows in her office
Active rules
Low stock → PO12
Sale → webhook12
Receipt → alert12

Last run 1s ago

No keying in data by hand

Retail brands already running on Stockagile

CrocsDon AlgodónLaagamMiinCallaghanEquivalenzaShon MottBlawYuxusOs2oValencia Basket ClubTwo JeysCrocsDon AlgodónLaagamMiinCallaghanEquivalenzaShon MottBlawYuxusOs2oValencia Basket ClubTwo Jeys

−15 h/wk

you stop copying data by hand

0

manual exports to feed your BI

+1,200

stores running

Rules & triggers

If this happens, do that. Defined once, run every time.

Build rules on the events in your operation: stock below minimum, sale closed, order created, receipt confirmed. Each rule reacts the moment it happens and fires the action —create a PO, alert the team, launch a flow— without anyone activating it.

Purchase order generated automatically when stock crosses the minimum
Active rules
Stock < min → create PO Sneaker Run · 3 units · below min PO
Sale closed → BI webhook BCN store · 2 min ago
Receipt → notify purchasing PO-1043 · 120 units received

1 rule fired now · stock below minimum

Example: presale → automatic purchase

From presale to purchase order, hands-free.

When a customer places a presale in ecommerce and there's no stock in the warehouse, Stockagile detects the event and automatically launches the purchase order to the right supplier. The stock arrives, it's received and the order is fulfilled — with no one deciding it manually.

Flow diagram: ecommerce presale → routing rules → no stock in warehouse → automatic supplier purchase → stock in transit → order fulfilled
Real-time events

Everything that happens in your store, logged as an event.

Sales, receipts, transfers, stock changes, online orders and customers — all recorded as an event with its type, author and time. It's the feed that powers your rules and your webhooks: what triggered each flow, when and with what result, always auditable.

See how it works
Movement history live
Sale closed · Blue Sweater · M POS BCN · BCN store · 1 min ago · webhook sent −1
Stock changed · Sneaker Run · 42 System · below min · rule → create PO −2
Receipt · Black Tee · L Marta R. · PO-1043 · webhook → ERP +120
Order created · Order #20471 Online · Ecommerce · webhook → CRM

Cada movimiento queda trazado: quién, qué, cuándo y por qué.

Sneaker Run · 42 rule
Event stock changed
Action create supplier PO
Status processed

Traced and auditable

Webhooks & API

Connect your stack. One event is enough for everything else to react.

Every event reaches your endpoint the instant it happens, with the full payload and the headers you define. They're standard HTTP: plug them into n8n, Zapier, Make or your microservice without a line of code. And when you need to go further, the documented REST API lets you read and write stock, orders and sales.

See how it works
Movement history live
POST /webhook · order.created Stockagile · 200 OK · 142 ms · → n8n
POST /webhook · product.stock_changed Stockagile · 200 OK · 98 ms · → BI
GET /api/stock · warehouse=MAD Power BI · 200 OK · company token
POST /webhook · sale.created Stockagile · 503 · retry 2/3 · requeued

Cada movimiento queda trazado: quién, qué, cuándo y por qué.

order.created webhook
Destination n8n · Zapier · Make
Headers Authorization, X-Env
Delivery with retries

Traced and auditable

Control & retries

If a flow fails, you'll know. And it gets processed again.

Every event stays in the integration log with its status —pending, processing, processed or failed—, its retries and the failure detail. If your endpoint was down, mark it as pending and Stockagile requeues it. Enable, pause or edit any webhook from the panel, without touching code.

See how it works
Event requeued · sale.created → ERP
2 3 corregido
Motivo: Endpoint down · manual retry

Ajustado y trazado

Integration event log live
Producto Status Retries Dif. order.created → CRM 1 0 stock_changed → BI 1 0 sale.created → ERP 0 2 error purchase.created → n8n 1 0

1 event failed · requeue with one click, without touching your stack

All the repetitive work in your operation. Automated and traced.

From rules to the API, every piece in one place. Open each block to see how it works.

Frequently asked questions

Do I need to know how to code to automate the basics?

No. Rules and webhooks are created from the Stockagile panel: you pick the event (low stock, sale closed, order created), the action or destination URL and any headers you need. Not a line of code. The REST API is there for when your technical team wants to build something custom, but you don't need it to get started.

What kind of rules can I set up?

Rules that react to the events in your operation. The most used one: if a product's stock drops below its minimum, create the purchase order to the supplier or alert the purchasing team. Also: when a sale closes, send the data to your BI; when an online order comes in, log it in your CRM; when a receipt is confirmed, notify the warehouse.

How do I connect Stockagile with n8n, Zapier or Make?

Stockagile's webhooks are standard HTTP endpoints. You copy the URL your automation tool gives you (n8n, Zapier, Make, Pipedream or your own stack), paste it into the webhook settings and pick the event that triggers it. From then on, every time that event happens, your flow runs. No proprietary connector, no middleware adapter.

Which events can I use as a trigger?

Retail sales, online orders, products (including 'stock changed'), purchase orders, transfers and customers — each domain with its variants (created, updated, deleted, restored). The 'stock changed' event is the most used one for keeping catalog feeds, ads and BI dashboards up to date without polling.

What's the point of the REST API if I already have webhooks?

Webhooks notify you when something happens (push); the API lets you read and write whenever you want (pull). With the documented REST API —per-company token authentication, docs in Swagger and Redoc— your team reads stock, orders, sales and products, connects your BI or builds custom integrations. The two pieces complement each other.

What happens if a flow fails or my endpoint is down?

Every event stays in the integration event log with its status (pending, processing, processed or failed). If the destination is down, the system retries with exponential backoff until the endpoint responds. If it keeps failing, you get an alert. You can review the log, see the exact payload that was attempted and relaunch it manually whenever you want.

Get started

Ready to stop keying in data by hand?

We'll show you how automations fit with your real operation, in a personalized 20-minute demo.

No lock-in · no per-sale commissions · migration included