Good fit
Simple approve/reject decisions
Leave requests, access requests, event applications, resource requests, and internal operational approvals.
Approval email guide
Approve or reject Google Forms responses by email
FormFlow sends a reviewer email for a Google Forms submission, lets the reviewer approve or reject, and records the decision status in the linked Google Sheet.
Quick answer
To approve or reject Google Forms responses by email, collect the request in Google Forms, connect the linked response sheet, add approvers in FormFlow, run Preflight, and confirm one reviewer decision updates the sheet.
When email approval is the right shape
Email approval is useful when reviewers already live in their inbox and the workflow needs a simple decision, not a full workflow dashboard. The Google Form collects the request, the email gives the reviewer context, and the linked response Sheet becomes the audit record.
Weak fit
Complex routed approvals
Procurement, expense systems, legal review, ticket queues, compliance workflows, or anything needing a full dashboard and SLA rules.
Email decision path
1
Submission arrives
A respondent submits the Google Form and the response lands in the linked Google Sheet.
2
Reviewer gets an email
FormFlow sends the approval request to the configured reviewer email address.
3
Reviewer decides
The reviewer opens the decision link and chooses approve or reject.
4
Status is recorded
The linked response sheet shows the decision status so operators can track the request.
Email and decision screenshots
Before adding real approvers
- Use one internal approver account first.
- Submit one internal test response with obvious request details.
- Check that the reviewer email includes enough context to decide.
- Click approve or reject from the reviewer account.
- Verify the linked Sheet status changed.
- Only then add additional approvers or route a live form.
What the approval email needs to include
Name, email, team, or other identifier so the reviewer knows who submitted the form.
The amount, date, access request, event choice, document, or reason that makes the decision possible.
A clear approve or reject path for the intended reviewer account.
A linked response Sheet status so operators can see Pending, Approved, or Rejected after the email action.
Common issues
Email did not arrive
Check the approver address, spam folder, Workspace mail restrictions, and whether Preflight showed any send-mail warning.
Wrong Sheet updated
Re-select the linked response spreadsheet in FormFlow. Duplicated test files can make this easy to miss.
Reviewer cannot decide
Ask the reviewer to use the intended Google account and send the decision-link error screenshot to support.
Need multi-step approval
Start with one reviewer first. Add more levels after the simple path is proven end to end.
Email approval troubleshooting
| Problem | Check first | Evidence for support |
|---|---|---|
| Email did not arrive | Approver address, spam folder, Workspace mail restrictions, and Preflight result. | Preflight text plus inbox/spam search result. |
| Email has wrong context | Whether the Google Form collects enough fields for the reviewer to decide. | Example test submission and email screenshot. |
| Decision link fails | Reviewer is signed into the intended Google account. | Decision page screenshot and reviewer account context. |
| Sheet status does not change | The selected response Sheet belongs to the tested form. | Linked Sheet name, decision result, and status column screenshot. |
How to design the first email test
Use a test request that is obvious to the reviewer: a fake requester, a clear item, and a decision that does not require policy judgment. The goal is not to approve a real business case. The goal is to prove email delivery, decision link behavior, and Sheet status write-back in one controlled run.
Requester: Test User. Request: Access to Demo Folder. Reason: First-run approval test. Reviewer: one internal account you can check.
A real purchase, confidential HR request, or multi-person decision before you know whether the approval email and Sheet status work.
What FormFlow is not
FormFlow is a focused Google Forms approval add-on. It is not a procurement platform, expense system, CRM, ticketing system, compliance system, or legal workflow suite. Keep the first workflow small and easy to audit.
FAQ
Can reviewers approve directly from email?
FormFlow sends a reviewer email with a decision path. Test with one internal reviewer first to confirm the link and account context work.
Where is the final decision stored?
The final approval status should be written to the linked Google Sheets response file so the operator has a visible record.
What if the email is blocked?
Check Preflight, the reviewer address, spam folder, and Workspace mail restrictions before adding more approvers.
Can this run a multi-department approval system?
Start with one small approval workflow first. If you need procurement, ticketing, SLA, or compliance features, use a broader workflow platform.
Next steps
- Approval workflow guideBuild the whole request-to-review path.
- First-run checklistProve Preflight, email delivery, decision link, and Sheet status.
- Track status in SheetsCheck that the linked response Sheet updates after Approve or Reject.
- Review after successUse this only after Preflight, reviewer email, decision link, and linked Sheet status all work.