Agency Intake to Google Sheets: A Review Workflow
Use a response spreadsheet as the source for a review queue. Each submission supplies the client’s brief; your team adds ownership, open questions and next actions in a separate review tab. The integration moves responses, but it does not qualify a lead, assign a reviewer or approve a scope.
What the native connection does
Save the form, open its Integrations tab and authorize Google Sheets. Zunoform creates a new spreadsheet named after the form, containing a tab named Responses. Use Open spreadsheet on the connected card to reach that destination. The current setup does not offer an existing-spreadsheet picker or a custom field-mapping screen.
Google Sheets is available on Zunoform Free. A Google account and any applicable Google service limits still apply. Enabling delivery affects new completed responses; it does not backfill earlier responses or send a partially completed questionnaire.
Prepare the intake and receiving sheet
Finish the question structure
Choose the project questionnaire and review its required fields and branches. Use distinct question labels before collecting production responses, because labels become column headings.
Save and authorize
Save the form so it has an ID, then use the Google Sheets card in Integrations. Complete authorization, open the automatically created spreadsheet and confirm that the integration is enabled.
Run a controlled submission
Publish a test copy or use an appropriate test form with fictional details. A template preview does not save a response or deliver a row. Compare the saved response with the destination row before sharing the production form.
Create a separate Review tab
Use Response ID to associate each review record with its source submission. Keep reviewer, status and next action outside the integration-managed Responses tab. Creating this tab and its review process is a manual setup task.
Map the brief into review decisions
Scroll sideways to read all three columns.
| Source answer | Review record | What a reviewer decides |
|---|---|---|
| Your name and organization; project contact email | Client reference and contact route | Who should receive a targeted clarification. |
| Audience and desired outcome | Primary objective | Whether the requested deliverables support that outcome. |
| Pages or features in scope | Scope questions | Which requests fit the agreed work and which require discussion. |
| Content owner and target date | Dependencies | Whether source material will be ready for the proposed schedule. |
| Response ID | Source response reference | Which submission the review concerns, including repeat submissions. |
Illustrative review example
An agency receives a brief asking for six pages before an event, but the client has approved copy for only two. The response row is the input record. In Review, the coordinator records “Needs content decision,” names the client’s content owner and asks whether a smaller first release is acceptable. No automatic readiness status is inferred from the client pressing Submit.
A later submission is a new record, even if the email address is unchanged. Link the new Response ID and record whether it replaces the earlier brief. Preserve the earlier review context so another team member can understand why scope or dates changed.
Handle schema changes and delivery problems
The worker writes Timestamp, Response ID, question columns, Location and User Agent. Multi-part fields can produce several columns. When headings differ, the worker rewrites the header row; it does not migrate older rows into a new schema. Freeze labels and order for a collecting form, or plan a new version with a separate review of historical data.
Keep formulas and internal status columns off Responses. If a row is missing, first confirm that the response was saved, then inspect the enabled connection and destination. Transient provider failures can retry; missing configuration can be skipped. Check for the Response ID before manually recovering a row, because an uncertain delivery followed by a retry can produce a duplicate.
Acceptance check
- The receiving spreadsheet is the one linked on this form’s integration card.
- A known sample response has matching labels and values.
- Both branches produce an understandable row.
- The team has a separate Review record linked by Response ID.
- Missing rows and repeated submissions have an assigned reviewer.
Start with the matching form
Questions people ask
Can I choose an existing spreadsheet?
The current native setup creates a new spreadsheet automatically. The guide’s Review tab is added to that destination manually; it is not a picker or mapping feature in Zunoform.
Can I add reviewer columns to Responses?
Use a separate tab. Responses is managed by the integration, and header updates or form changes can interfere with custom columns and historical interpretation.
Does a successful form submission prove Sheets delivery?
No. Check the saved response and the destination independently. Integration delivery happens after submission and can fail or be delayed.
Keep reading
Better forms.
Better data.
Start with a conversation, a document or a single page. Unlimited forms and 500 responses per month on Free. No card required.