Save Google Forms responses to Notion with Make

Separate the response source from the working register

Treat the linked response sheet as the source and Notion as the place to assign ownership and track progress. Use TEST-N001, category “Information request” and summary “I need the setup requirements” as a fictional sample. Decide where corrections belong and which properties operators may edit in Notion before creating a synchronization rule.

Prepare typed Notion properties

Create a practice database with a title, Request ID, category, summary, received date and handling status. Use a text property for the stable identifier and a date property for time. If category is a Select, align its choices with the form. Send unknown choices or malformed dates to review rather than silently inventing values.

Authorize the intended data source

Create the Notion connection and grant access to the practice page. For a new setup, use Create a Data Source Item rather than a Legacy module. New modules use data_source_id; do not substitute database_id. If a database has multiple data sources, identify the intended one. Check sharing if it is missing instead of choosing an unrelated destination.

Read one controlled form response

Link the form to a practice spreadsheet and submit once. Configure Google Sheets > Watch New Rows for that sheet, headers, a practice starting point and limit one. Add request_id, notion_page_id and synced_at columns; manually enter TEST-N001 for this trial. Production requires a separate step that issues and durably stores each request ID before Notion creation. A row number is useful for updating the current row, but is not a stable identifier after sorting.

Map the new Notion item

Select the destination data source. A useful title is “TEST-N001 | Information request.” Map Request ID, summary and received date from the source, and set the initial status to a fixed “New.” Start with required properties and short text, then add optional properties so a type mismatch is easier to isolate.

Write the returned page ID back to the source

Follow creation with Google Sheets > Update a Row, using the row number returned by the read step. Preserve unrelated responses and record the returned Notion page ID and sync time. Before recovery, reconcile the page ID or Request ID against Notion. A successful creation followed by a failed sheet update can otherwise become a duplicate on replay.

Test boundaries as well as the normal record

Prepare an ordinary response, an empty optional summary, an unexpected category and a replay of the same request. Compare item count, property values and source bookkeeping. Record the last completed action for a deliberate practice failure. Repairing authorization alone is not a reason to replay every source record.

Document the one-way contract

This workflow appends new responses to Notion. It does not automatically reconcile later edits in either system. If updates are required, define matching by Request ID, editable properties and conflict precedence separately. Choose the polling interval and review lookups, creation and state writes before activation.

• Design stable IDs and duplicate protection
• Recover from partial failures
• Notify Slack about form responses