Email support triage with approved draft replies
Label every support email, draft a reply from your knowledge base, and send it only after an approver clicks Approve in their inbox.
When any workflow fails, get an email that explains the failure in plain English, rates how serious it is and suggests the fix.
Included in Pro and aboveStarter workspaces can read this template but not deploy it.
Workflows fail for ordinary reasons: an expired login, an empty field, a service that was briefly down. The slow part is not the fix, it is working out what the error message means and whether it matters. This template does that first reading for you.
It starts from an Error Trigger. When another workflow in your workspace fails, the platform hands this one the workflow name, the step that failed, the error message and the execution id. An AI step turns that into a short plain-English explanation, a severity rating, the most likely cause and an ordered list of things to check. A small code step lays it out as a tidy email, and Gmail sends it to the person you name.
Use it as the workspace-wide error workflow so one alert flow covers everything, or attach it to a single important workflow. It never touches the failed workflow or its data, and it only emails the address you set, so it is safe to leave switched on. It suggests fixes; a person still decides what to change. The error text is sent to the AI model through OpenRouter and by email, and error messages can contain fragments of your data, so point the alert at a trusted address. There is no de-duplication: a workflow that fails every minute sends an email every minute, so fix or pause a noisy workflow quickly.
The platform starts this workflow whenever a workflow that points to it as its Error Workflow ends in an error. It receives the workflow name, the failed step, the error message and the execution id.
An AI step reads only those four facts and writes a plain-English summary, a severity (critical, high, medium or low), the most likely cause, whether a re-run may be enough, and two to five fix steps in the order to try them.
A code step builds a clear alert email: a coloured header showing the severity, the summary, a small table of details, the suggested fix and the original error underneath.
Gmail sends the alert to the address you set in the variable. Nothing else is sent and nothing is changed in the failed workflow.
Anyone can read this page. Deploying the template into your workspace needs a Pro, Team or Enterprise plan. Starter workspaces can browse the library but cannot deploy templates. See plans.
You will connect OpenRouter API key, Google account (Gmail) and fill in a few settings. Setup takes about 10 minutes. Your credentials stay in your own workspace.
Yes. Using the template creates a normal workflow in your workspace on the visual canvas. Rename it, edit any step, add approvals, test it and run it like any other workflow. It counts toward your plan’s workflow limit.
Yes. This workflow can send or write to external systems. Review the steps and test it with sample data before you activate it, and consider adding an approval step.
More workflows teams use alongside this one.
Label every support email, draft a reply from your knowledge base, and send it only after an approver clicks Approve in their inbox.
Score every web-form lead against your ideal customer, log it to Google Sheets, create it in your CRM and alert sales about hot ones.
Detect Arabic or English (including Arabizi), answer in the customer's language from your knowledge base, and hand over to your team when needed.
Every template is open to read. Deploying one into your workspace needs a Pro, Team or Enterprise plan; Starter workspaces can browse the whole library.