Check something in your system
template.
The Check something in your system template is a ready-made Dazza workflow for status questions only your own system can answer. Dazza sends reference and email to your own system, once the customer has proved who they are, 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 about something only your system knows, such as the status of a request. You can change that sentence, and Dazza follows the new one.
“What’s the status of my application?”
“Has my claim been processed?”
“Is my repair booked in yet?”
“Reference REQ-1182: any news?”
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 |
|---|---|---|---|
| Reference | Short text | Required | — |
| Required | — |
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 something in your system"
},
"run": {
"id": "run_…",
"test": false
},
"inputs": {
"reference": "REQ-1182",
"email": "jamie@example.com"
},
"conversation": {
"id": "cnv_…",
"pageUrl": "https://yourbusiness.com/…"
},
"customer": {
"email": "jamie@example.com",
"name": "Jamie",
"verified": {
"email": "jamie@example.com",
"via": "code",
"userId": null
}
},
"sentAt": "2026-10-27T10:42:00.000Z"
}{
"message": "Application REQ-1182 was approved on 24 October. The welcome pack is in the post."
}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 | On. The customer proves who they are with an email code or your site’s signed login before it runs. 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. It runs once the customer is verified, such as a sender whose domain passes DMARC. |
| 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
- Businesses with their own system for applications, claims, repairs or memberships
- Teams with a developer, or a Make or n8n account
- Anyone whose customers ask “where are we with…?”
Tips for adapting it
- Rename Reference to what customers actually have, such as “Application number” or “Membership ID”.
- Reply with a
messagefor the customer and the facts behind it. Dazza explains both in your tone. - Return only what that customer may see: compare
customer.verified.emailwith your record first. - Use Send a test before going live, and reply within 10 seconds.
What does my system receive?
A signed JSON request with the details collected, the conversation and, when the customer has proved who they are, customer.verified. See Call your own system.
What if my system is down?
Any reply that isn’t a success counts as a failure, and Dazza offers to bring in the team instead.
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.