FormGuard
First proof: save one response cap, deadline, or choice quota on a test form, then confirm the form closes or shows the expected message.
Use this page when you are ready to install a FormSuite add-on from Google Workspace Marketplace but want a low-risk first test. The goal is simple: open the right add-on, configure one tiny workflow, confirm the result, then decide whether to scale it.
Each add-on below has a public Marketplace install path. Pick the workflow that matches your current file, then run the smallest test listed before relying on real submissions, rows, emails, or documents.
First proof: save one response cap, deadline, or choice quota on a test form, then confirm the form closes or shows the expected message.
First proof: send one test owner alert or respondent confirmation, then confirm the message arrives with the right subject, recipient, and template fields.
First proof: submit one test form response and confirm the new response row receives the formulas, formats, and helper columns from the model row.
First proof: send one test email to yourself from a sample row, then confirm merge tags, recipient column, and row-level status before any batch send.
First proof: generate one sample Doc or PDF from a test row, then check template fields, output folder, filename, and formatting.
First proof: link one Google Forms choice question to one selected Sheets column, run preflight, update now, and confirm two sample choices appear.
Ask for setup help only after one small test is unclear. Request a Marketplace review only after the add-on completed a meaningful first result.
Include the add-on name, the type of file, the test you tried, and the exact step that blocked the first run. Do not include private responses, customer data, passwords, or sensitive records.
A useful review says what the add-on helped you do, what file type you used, and whether the first-run check passed. Keep it short and specific.
When sharing this page in public communities, answer the user's immediate problem first. Use one link, disclose that you maintain FormSuite when recommending it, and prefer this checklist when the user has not chosen a product yet.
For Google Forms add-ons, I would test one small workflow first: one cap, one confirmation email, or one dynamic-choice mapping. Disclosure: I maintain FormSuite; this checklist shows the install and first-run path.
For Sheets add-ons, start with one row before any batch. Test formula copy-down, one email, or one generated document, then scale only after the first result looks right.
If the first test worked, a short Marketplace review helps other users evaluate the add-on faster. Mention the workflow and result rather than broad praise.