|
This article covers the following: |
Overview
Building a Wingz workflow from scratch requires configuring each node individually: the trigger, one or more Agent nodes, and any logic nodes the automation requires.
For a common reporting, monitoring, or analysis requirement, a template provides a faster starting point. Examples include summarizing a campaign's results, alerting about a conversion drop, or turning session recordings into new test ideas. Instead of an empty workflow canvas, a template opens with a working Start node, Agent node, and End node already connected. Additionally, it is configured for a specific use case, so you only have to customize an existing setup rather than build one from scratch.
All workflow templates are available on the Workflows dashboard, alongside the option to start from scratch. For more information on where templates appear and how choosing one differs from starting from scratch, see Create a Workflow.
Every time a template runs, it consumes credits. Each template listed below shows an estimated average credits used per run, so you can weigh a template's usefulness against its ongoing cost before publishing it. See Manage Wingz Credits for how credits are consumed across Wingify and how to check your remaining balance.
This article lists the available templates by category and covers what to check before you publish one.
Available Templates to Create Workflows
Reporting and Summary
| Template | What it does | Trigger | Average Credits Used per Run (Estimated) |
| Automated Campaign Debrief | When a campaign reaches a decision, Wingz summarizes the winner, metric trade-offs, segment breakdown, and recommended next test, then emails the team. | On decision |
50 |
| Weekly Experiment Status Digest |
Every week, Wingz lists all running campaigns with status, traffic split, and which ones reached significance this week.
|
Weekly |
50 |
| Campaign and Session Recording Snapshot | When a campaign reaches a decision, Wingz analyzes the campaign's performance data and its session recordings at the same time, then combines both analyses into a single email. | On decision |
100 |
| Daily Active Campaign Summary | Every day, Wingz sends a short summary of all active campaigns and what changed since yesterday. | Daily |
150 |
| Post-Test Stakeholder Report | When a campaign concludes, Wingz writes a non-technical summary in business impact language for stakeholders outside the optimization team. | On decision |
50 |
| Monthly Executive Program Report | Every month, Wingz runs velocity, learnings, and underperformer analysis in parallel and merges them into an executive-ready report. | Monthly |
500 |
Monitoring and Alerting
| Template | What it does | Trigger | Average Credits Used per Run (Estimated) |
| Conversion Drop Alert | Every day, Wingz compares conversion rates against a rolling baseline, set to 7 days by default and adjustable when you customize the workflow. It runs a diagnosis and emails it only when it detects a material drop. | Daily |
200 |
| Weekly Heatmap Friction Scan | Every week, Wingz scans heatmaps across active pages and ranks the top friction points by page and severity. | Weekly |
200 |
| Guardrail Metric Check | After a campaign concludes, Wingz reviews the winning variant to see if a guardrail metric got worse. An email is sent only in that case. | On decision |
50 |
| Underperformer Flag Weekly Sweep | Every week, Wingz reviews running campaigns for stalled or underperforming tests and emails only if any are found. | Weekly |
150 |
Ideation and Test Creation
| Template | What it does | Trigger | Average Credits Used per Run (Estimated) |
| Weekly Test Backlog Refresh | Every week, Wingz synthesizes learnings from recently concluded campaigns into a ranked backlog of what to test next. | Weekly |
150 |
| Heatmap and Recording to Three Test Ideas | Every week, Wingz analyzes heatmaps (with a refinement pass) and session recordings in parallel, merges both, exits silently if neither yielded usable data, otherwise generates 3 test ideas, drafts a full brief for each, and routes the lead brief to one inbox with the other two merged into a second. | Weekly |
400 |
Knowledge Management
| Template | What it does | Trigger | Average Credits Used per Run (Estimated) |
| Winning Test Knowledge Entry | When a campaign reaches a decision, Wingz builds a structured learning document combining the performance summary with the behavioural story of the losing variation. | On decision |
150 |
QA and Governance
| Template | What it does | Trigger | Average Credits Used per Run (Estimated) |
| Launch QA Check | When a campaign starts running, Wingz checks targeting logic, page configuration, success metrics, and audience overlap, and emails a checklist only if it finds a problem. | On launch |
50 |
| Experiment Governance Audit | Every week, Wingz audits running campaigns for missing hypotheses, undefined success metrics, or no clear owner, and emails only if gaps are found. | Weekly |
50 |
Diagnosis
| Template | What it does | Trigger | Average Credits Used per Run (Estimated) |
| Regression Response Workflow | When a campaign reaches a decision, Wingz checks guardrails and, on a breach, drafts a root cause note and a rollback recommendation in parallel before emailing them together. | On decision |
150 |
| Segment Divergence Analysis | When a campaign reaches a decision, Wingz analyzes mobile and desktop in parallel, compares them, and emails only if the two segments disagree. | On decision |
100 |
Product and Feature Flags
| Template | What it does | Trigger | Average Credits Used per Run (Estimated) |
| Feature Rollout Health Check | When a feature rollout starts, Wingz checks rollout configuration and targeting and emails a summary for the product team. | On launch |
50 |
| Feature Test Debrief | When a feature test reaches a decision, Wingz summarizes the result in product terms for the engineering and product teams. | On decision |
50 |
Personalization
| Template | What it does | Trigger | Average Credits Used per Run (Estimated) |
| Personalization Experience Performance | When a personalization experience reaches a decision, Wingz analyzes targeted versus untargeted performance in parallel and merges the results of both into one email. | On decision |
100 |
Use a Template
Opening a template takes you to the same Workflow editor you would use to build a workflow from scratch. It has the same canvas, node palette, and settings panel as described in Understand the Workflows Canvas Layout.
From here, you can customize the template's nodes manually on the canvas, or use the Wingz Workflow Assistant to describe the changes you want and update the configuration. Both approaches work on a template the same way they work on a workflow built from scratch.
Once you are done customizing, follow the steps outlined in Save, Test, and Publish the Workflow to activate the workflow.
Before You Publish a Template
A template's End node comes with the Notify action already configured, but without a recipient email address. Before you publish the workflow, open the End node and add a recipient. This field is required. Without a recipient email address, the End node's Notify action has no destination, so no one receives the workflow's output when it runs.
Need more help?
For more information or further assistance, contact Wingify Support.