Do not make the first live submission your first approval test. Use a copied or disposable Google Form, select the linked response spreadsheet, add one known approver, save the workflow, run Preflight, and send one internal test submission before real reviewers depend on it.
A safe Google Forms approval workflow test uses one form, one linked response sheet, one approval level, one approver you control, and one sample submission. The test is successful only when Preflight passes and the response sheet can show the workflow status.
FormFlow should show the linked response spreadsheet and response tab before the workflow is enabled.
Start with one reviewer email that you can inspect quickly, then add more levels later.
Run Preflight after saving so missing sheets, empty approvers, or quota issues are caught before launch.
Confirm the linked response sheet is the operational record for approval status and follow-up.
Use a known inbox for the first test so approval messages and any delivery problems are visible.
Approvers should see enough form answers to make a decision without guessing.
Check that the response sheet can support the way your team will monitor approval state.
Tell reviewers what Approved, Rejected, comment, and reminder behavior should mean in your process.
Most launch blockers are setup issues, not product mysteries. Fix them before sending live traffic through the form.
Create or reconnect the Google Sheets response destination, then select it from FormFlow with Picker.
Add at least one valid reviewer email to the first approval level.
Complete the Google authorization path for the account that owns or edits the form.
Reduce the test scope and keep launch volume inside Google account limits.
If the copied form passed Preflight and one internal submission produced the expected approval path, move to a small live rollout. Ask for setup help only if a specific step blocks you, and leave a Marketplace review only after the first real workflow succeeds.