How Ai Flowi writes, tests and reviews its guides

Ai Flowi publishes these guides and is operated by AI FLOWI SDN. BHD. This editorial policy explains our team responsibilities, evidence labels, test method, sourcing and corrections.

By Ai Flowi · Published · Updated .

Who writes, reviews and publishes

  • Writing: the guide writer explains the task, required setup, steps, sources and known limitations, and separates observed results from examples.
  • Technical review: a technical reviewer checks the steps against the live product before publication. Our technical reviewer is Janice Lee, Technical Support.
  • Publishing: Ai Flowi publishes the guide with evidence labels and dates, and handles reported corrections.

What our page labels mean

Production-tested, with a date
The stated workflow and cases were run against the live product on the recorded test date. The label applies to that test scope, not every feature or configuration. For example, the webhook-to-Google-Sheets workflow was production-tested on 8 October 2026; its duplicate-protection version was production-tested on 9 October 2026.
Documented
The statement comes from a cited source. Documentation describes what is offered or specified; it does not establish that we ran it successfully.
Illustrative
The example explains a possible setup or expected output. It is not a production test result, testimonial or customer outcome.

How workflow tests are run

The recorded webhook-to-Google-Sheets tests used this method:

  1. Use a dedicated test workflow and an isolated test sheet, with synthetic data and @example.com email addresses.
  2. Send real HTTP requests to the production webhook. Exercise valid input, invalid input and missing or invalid authentication, and record the HTTP status and response.
  3. Read the sheet after each request and record the row count before and after. A response alone does not prove that a row was written.
  4. Sanitise the workflow export, import it into a clean flow, configure the test connection and sheet, and re-test the stated cases. Report which cases were repeated and which were not.

On 8 October 2026, valid authenticated input returned HTTP 200 and added a row; invalid input returned 422, and missing or invalid authentication returned 403, without adding rows. The clean-import re-test reproduced those results. The spreadsheet-failure case was tested on the original flow but was not repeated on that imported copy.

Test limits stay visible: the 9 October 2026 version prevented extra rows for sequential duplicate deliveries; simultaneous duplicates can still insert extra rows. In AI Flowi Workflow 1.9.2, a Google Sheets failure returns the raw platform error and has no in-flow error branch.

Read the recorded production results, test limitations and duplicate-protection results.

How competitor facts are sourced

Competitor facts come from official product, documentation and pricing pages. We cite the source URL and access date, and label the fact documented, not tested: documented (official source, checked <date>). Reading an official page does not establish that we tested that product.

Comparisons state the task, inputs and outputs, setup, credentials, operations, error handling, usage units and cost assumptions. Different billing units are not treated as equivalent.

This section: written by Ai Flowi; facts checked 21 October 2026.

Evidence for AI-staff feature pages

For AI-staff pages, distinguish documented product features from observed results. A feature description supports its stated local scope; it does not establish deployment, external delivery or a completed customer outcome.

By Ai Flowi

Updated 21 October 2026; facts checked 21 October 2026

Documented product features. Read the evidence policy.

Keep the source-check date separate from any test date. Label proposed setups as illustrations. The workflow test labels elsewhere in this policy apply only to their recorded configurations; they do not establish AI-staff production tests.

Add a named technical-review credit only after that reviewer has completed the page’s review, with its scope and date recorded. The existing reviewer profile is not evidence that new staff pages have been reviewed.

For statutory or financial definitions, link the official authority and record the source version where stated and the actual check date. Stronger correctness claims need relevant, confirmed review evidence. Keep private evidence out of public text.

Read the staff feature guides alongside their limits. Report a correction with the page, disputed statement and supporting evidence so its wording and date can be checked. Publisher identity is on About Ai Flowi.

Product statements

Read the AI Flowi Workflow product overview alongside the source and test scope attached to individual statements.

How prices are presented

AI Flowi Workflow has five plans, Go, Plus, Pro 100, Pro 200 and Pro 500, and every plan includes all features: Plans: Go from USD8/month billed yearly (USD10 monthly), five plans up to Pro 500. Every plan is listed on the pricing page. Each node run uses 1 Flowi Token. Plans: Go from USD8/month billed yearly (USD10 monthly), five plans up to Pro 500. Every plan is listed on the pricing page. Third-party API and model usage is not included. See pricing.

Corrections and publication limits

Report an error to contact@aiflowi.com or use our contact page. Include the guide URL, the disputed step or statement and supporting evidence so it can be checked. Changed guides show an updated date.

We never publish invented testimonials or ratings, or customer results without permission.