AI Flowi Workflow templates (tested)
Start with two downloadable workflows tested in production, or the website lead-capture use case built on the validated recipe. Tests used synthetic requests in Ai Flowi’s own workspace, running AI Flowi Workflow 1.9.2. The dates and limits below describe those recorded tests.
By Ai Flowi · Published · Updated
Delivery formats: Downloadable template means an importable file link exists on the linked page; Tested recipe means production-tested steps to rebuild, with no importable file; Documentation only means instructions without production-test evidence. Configuration JSON and setup guides are not workflow imports.
Difficulty rule: Beginner = up to five saved workflow nodes and at most one decision router (two branches); Intermediate = more than five nodes or more than one decision router. Count all saved nodes, including unused response branches, rather than node runs. Both levels require the configuration skills listed on the linked page.
Tested templates and recipe-based use case
-
Validated webhook to Google Sheets
Delivery format: Downloadable template. Category: Data intake and validation. Difficulty: Intermediate (7 nodes, 1 decision router).
Production-tested and imported/re-tested: . Universal Webhook receives a POST; JSON Operations validates and prepares the row; Verification Router routes it to Append Rows and a Webhook Response. A valid authenticated request returned 200 and added one row. Invalid input returned 422; missing or invalid API keys returned 403. These rejected requests added no rows.
Download the validated workflow (ZIP) · Related tutorial: setup and required configuration · Recorded test results
After import, select your Google Account, set your Spreadsheet ID and the
Sheet1!A:Crange withname,email,requestcolumns, and configure Platform API Key authentication. This version appends another row for each identical delivery. The spreadsheet-failure test was run on the original flow; it was not repeated on the imported copy. -
Webhook to Google Sheets with duplicate protection
Delivery format: Downloadable template. Category: Data intake and duplicate protection. Difficulty: Intermediate (8 nodes, 1 decision router).
Production-tested and imported/re-tested: . This version uses Upsert Row keyed on
event_id. First delivery returned200 {"status":"inserted"}; a sequential repeat returned200 {"status":"duplicate"}and updated the same row without inserting a second row. The last write wins.Download the duplicate-protection workflow (ZIP) · Related tutorial: setup, recorded tests and limits
Select your Google Account, replace the Spreadsheet ID placeholder, configure webhook authentication, and follow the tutorial’s worksheet setup with
event_id,name,email,requestheaders. Send a textevent_idof 1–100 characters and reuse it for retries of the same event. Matching is case-sensitive. Protection lasts while the keyed row exists in that worksheet; deleting or changing it can allow another insert. Simultaneous duplicate deliveries can both insert. -
Capture website leads into Google Sheets
Delivery format: Downloadable template. Uses the linked underlying validated workflow, with no separate lead-capture export. Category: Lead capture. Difficulty: Intermediate (underlying validated graph: 7 nodes, 1 decision router).
Built on the recipe production-tested on . Send
name,emailandrequestfrom your website’s trusted sender to the validated workflow. This use case reuses the recipe’s evidence; the recorded tests used synthetic HTTP requests. They do not establish a test of your website form or a customer deployment.Lead-capture use case and setup · Download the underlying validated workflow (ZIP) · Related tutorial: webhook to Google Sheets
Keep the Platform API Key in a trusted sender, outside public browser code. Test your site’s submission path with synthetic data before using real leads. The use-case guide also links the version tested on 9 October 2026 for sequential retries.
Before you use a download
Both downloads are sanitised and were imported into clean flows for re-testing. Configure your own Google connection, spreadsheet and webhook authentication, then check the HTTP response and sheet rows with synthetic inputs.
Spreadsheet errors remain a limitation: a Google Sheets failure stops the flow and returns the raw platform error, which can include the Google API URL and Spreadsheet ID. Version 1.9.2 has no in-flow error branch for this failure. Do not display the raw response verbatim to website visitors.
These are no-model workflows. Plans: Go from USD8/month billed yearly (USD10 monthly), five plans up to Pro 500. Every plan is listed on the pricing page.
Explore AI Flowi Workflow · Pricing · Google Sheets integration
More production-tested templates (9 October 2026)
Each template below was built and run on AI Flowi Workflow 1.9.2 with synthetic data. Each page lists every test case, the observed result and its limits.
- Validate webhook input and return 200 or 422
Delivery format: Tested recipe. Manual setup; no importable workflow file. Category: Input validation. Difficulty: Beginner (5 nodes, 1 decision router).
Production-tested : 28 of 28 test cases passed. Related tutorial: webhook validation and routing.
- Clean and normalise lead data before writing to Google Sheets
Delivery format: Tested recipe. Manual setup; configuration JSON is available on the linked page, with no importable workflow file. Category: Lead data cleaning. Difficulty: Intermediate (7 nodes, 1 decision router).
Production-tested : 32 of 32 test cases passed. Related tutorial: webhook to Google Sheets.
- Look up a row in Google Sheets by email
Delivery format: Tested recipe. Manual setup; a setup JSON download button is available on the linked page, with no importable workflow file. Category: Spreadsheet lookup. Difficulty: Intermediate (8 nodes, 1 decision router).
Production-tested : 30 of 30 test cases passed. Related tutorial: webhook and Google Sheets setup.
- Update a row’s status in Google Sheets
Delivery format: Tested recipe. Manual setup; no importable workflow file. Category: Spreadsheet updates. Difficulty: Intermediate (13 nodes, 2 decision routers).
Production-tested : 34 of 34 test cases passed. Related tutorial: webhook and Google Sheets setup.
- Route webhook requests by type into Google Sheets tabs
Delivery format: Tested recipe. Manual setup; no importable workflow file. Category: Request routing. Difficulty: Intermediate (12 nodes, 2 decision routers).
Production-tested : 34 of 34 test cases passed. Related tutorial: webhook validation and Google Sheets setup.
- Use a Google Sheet as a read-only JSON API
Delivery format: Tested recipe. Manual setup; no importable workflow file. Category: Spreadsheet read API. Difficulty: Beginner (5 nodes, no decision router).
Production-tested : 25 of 26 test cases passed; T20 failed the no-leak check because a raw platform error exposed a private spreadsheet identifier. Related tutorial: webhook and Google Sheets setup.
- Write a scheduled status row to Google Sheets
Delivery format: Tested recipe. Manual setup; no importable workflow file. Category: Scheduling. Difficulty: Beginner (3 nodes, no decision router).
Production-tested : 15 of 15 test cases passed across a companion harness, a manual graph run and one real one-minute firing. Daily wall-clock timing was not tested. Related tutorial: Google Sheets setup background.
- Create a Google Doc from a form submission
Delivery format: Tested recipe. Manual setup; no importable workflow file. Category: Document creation. Difficulty: Intermediate (9 nodes, 1 decision router).
Production-tested using AI Flowi Workflow 1.9.2: 41 of 42 cases matched exactly; the recipe passed 42/42 with the documented Windows CR+LF to LF conversion in
unicode-literal. Tab, emoji, braces, HTML-like and formula-like text stayed literal. Repeat delivery creates a second document (no deduplication). Related tutorial: webhook validation and Google connection setup. - Save a webhook submission as a JSON file in Google Drive
Delivery format: Tested recipe. Recreate manually from the documented settings; no import file is supplied. Category: File storage. Difficulty: Intermediate; nine nodes with one decision router.
Tested with AI Flowi Workflow 1.9.2: 47 of 48 cases matched exactly; 48/48 is supported with documented NFD-to-NFC name normalisation. Email and request values stayed exact, including Windows CR+LF; the name’s emoji was retained. Requires sequential requests, shared local worker storage and Drive authorisation. Repeat submissions create additional files without deduplication. Webhook validation and Google connection tutorial.
- Create a Google Slides presentation from a form submission
Delivery format: Tested recipe. Build manually from the page’s configuration and port mappings; no workflow download is supplied. Category: Presentation creation. Difficulty: Intermediate (14 nodes, 1 decision router).
All 49/49 production cases passed on with synthetic test requests in Ai Flowi’s own workspace. The presentation retains Google’s default first slide plus one added slide with the request text. Stored-text checks allow line-ending normalization; visual slide layout was not tested. Repeated delivery creates a distinct presentation, with no deduplication. The success acknowledgement contains a literal redacted ID rather than a deck link. Related tutorial: authenticated webhooks and Google connections.
Sources: Webhook to Google Sheets tutorial and production tests, 8 and 9 October 2026; lead-capture use case.