Check stock and lead times
template.
The Check stock and lead times template is a ready-made Dazza workflow for live stock and lead-time questions. Dazza sends product code and quantity to your own system and answers with what your system replies. Every detail, check and message can be changed.
The questions
it answers.
Dazza uses it when the customer asks if a product is in stock, how many are available, or the lead time. You can change that sentence, and Dazza follows the new one.
“Have you got 200 of SKU 4471?”
“What’s the lead time on the 4471?”
“Is this in stock?”
“How many can you ship this week?”
What it asks for.
Nothing more.
Dazza asks only for what’s missing, never for what it’s already been told, and checks emails, numbers and dates as it goes. Add, remove or reorder details, up to 10.
| DETAIL | TYPE | REQUIRED | CHOICES OR HELP |
|---|---|---|---|
| Product code | Short text | Required | — |
| Quantity | Number | Optional | — |
Where the job
goes next.
This template uses Call your system. Switch to another way to finish, or add decisions that choose between them.
Send to your team
The request lands in the Team queue of your inbox with every detail, and your team gets an email.
SWITCH TO IT ANY TIMEShare a link
Dazza shows a button to a page, such as your booking page or a form, with details filled into the address.
SWITCH TO IT ANY TIMECall your system
Dazza sends a signed request to your system and answers from the reply. Scale and above.
AS IT COMESPOST https://your-system.example/dazza
content-type: application/json
x-dazza-event: action.run
x-dazza-timestamp: 1793097720
x-dazza-signature: sha256=9f2c…
{
"event": "action.run",
"action": {
"id": "act_…",
"name": "Check stock and lead times"
},
"run": {
"id": "run_…",
"test": false
},
"inputs": {
"product_code": "4471",
"quantity": "200"
},
"conversation": {
"id": "cnv_…",
"pageUrl": "https://yourbusiness.com/…"
},
"customer": {
"email": null,
"name": null,
"verified": null
},
"sentAt": "2026-10-27T10:42:00.000Z"
}{
"message": "1,240 units of SKU 4471 are in stock. Orders placed by 1pm ship today on a 48-hour service."
}The checks,
out of the box.
Every check runs in code before the workflow does, so none of them rely on the AI behaving. Change any of them per workflow.
| Check | As it comes |
|---|---|
| Customer confirms first | Off. It runs as soon as the details are complete. |
| Customer verifies their email first | Off. Turn it on for anything about a customer’s own account (Growth and above). |
| Team approves before it goes ahead | Off. Turn it on to have your team approve or decline each one in the inbox (Growth and above). |
| Starts in | Test, so it only runs in your preview until you set it to Live. |
| Email and messaging apps | Used as it comes, since it needs no button. |
| Plan | Scale and above. |
Who it suits.
How to adapt it.
The groups are a guide, not a rule. Any business can use any template, renamed to fit.
Who it suits
- B2B distributors and wholesalers
- Manufacturers with an ERP
- Stores whose stock lives in a spreadsheet or system
Tips for adapting it
- It doesn’t need a verified customer, because stock isn’t personal. Turn verification on if you reply with customer-specific prices.
- Reply with the quantity available, the lead time and a
message. - If your stock is in a spreadsheet, a Make or n8n scenario can look it up and reply.
Why doesn’t it need verification?
Stock levels aren’t personal, so anyone can ask. If your reply includes account prices, turn on Customer verifies their email first.
What does my system receive?
A signed JSON request with product_code and quantity in inputs. Reply with JSON within 10 seconds.
Can I use Zapier?
Zapier’s Catch Hook always replies with the same short receipt, so it can’t hand order details back. For lookups through Zapier, connect Zapier’s MCP server in Connections instead. Make (with a Webhook response module), n8n (with a Respond to Webhook node) and your own API can reply with data.