Send Google Forms responses to Slack with Make and Google Sheets

Define the output and acceptance sample

The target is one message per new response, containing an intake ID, category and brief summary. Prepare a normal response, one with an optional field empty and a replay case. Keep detailed personal content in the access-controlled source rather than copying it to a broad channel. Decide what an operator needs to identify the request and what can remain behind the sheet’s permissions.

Prepare the linked response sheet

Link the practice form to a response spreadsheet and submit once so the actual response columns exist. Add management columns such as request_id, notified_at and slack_message_id without replacing the form-generated columns. For an initial trial, assign TEST-001 manually. In production, choose a stable intake identifier; a row number alone is not stable if people later sort or move records.

Choose the new-row trigger and starting point

Add Google Sheets > Watch New Rows, select the linked response sheet and configure its header row. Keep the first limit at one and choose a starting point restricted to the practice response. The module reference warns about blank rows interrupting subsequent processing. Avoid using an operational response table as a scratchpad with separator rows, and recheck the trigger after structural edits.

Map a message that helps the recipient act

Connect Slack’s message action to a fixed practice destination. A useful message might say “New enquiry TEST-001 / Category: information request / Summary: pricing question.” Map the values from the source, including an explicit fallback for an absent optional summary. A recipient should know what to open and who owns the next action without interpreting a raw payload.

Save delivery evidence after the message succeeds

After the Slack action, update the source row with the delivery time and returned message identifier. Map the current row carefully and preserve unrelated columns. This evidence helps distinguish a missing notification from a failed bookkeeping update. A new-row trigger is not a repair queue: a later recovery process needs to inspect unfinished IDs rather than assume the trigger will discover them again.

Test all three outputs

Run one controlled response and compare the response sheet, real Slack post and delivery state. Add a second response and repeat. Check the workspace’s integration permission if authorization fails, and inspect both source values and mapping if a field is blank. The acceptance record should identify the tested request IDs and expected destinations; this article itself does not claim those tests were run in your account.

Common question: should Make append the response too?

If Google Forms already saves into the linked sheet, Make should not append the same response there again. That can duplicate the row or create a loop if the added row is watched too. Copying into a separate operations ledger is a different job: preserve the relationship between its reference and the original response.

After renaming a form question, recheck the mapping with a practice response. The form owner and workflow owner need to share that change. A form accepting a submission does not establish that its downstream message still contains the correct category and summary. Treat the field contract as part of routine maintenance.

Choose timing and review the consumed work

Choose the schedule from the acceptable notification delay, then inspect the acquisition, message and update activity in execution history. Include any extra lookups in the budget. If posting succeeded but the state update failed, replaying everything may post again. Use the saved message identifier and incomplete execution details to choose a recovery point before enabling unattended operation.

• Get started with Make: registration to a first spreadsheet notification
• How to estimate Make credits: polling, rows and retries
• Prevent duplicate writes in Make with stable keys and recovery states
• Handle Make errors: execution history, incomplete runs and safe retries