Get started with Make: registration to a first spreadsheet notification

Prepare the accounts and destinations

Prepare a Google sheet you can edit and a Slack workspace where the integration is permitted. Use the headers request_id, category and summary, with one fictional row such as TEST-001. Choose a practice channel. Resolve workspace approval before troubleshooting the scenario itself; a user being able to post manually does not establish permission for an integration.

Register and create a scenario

Create your account using the Make registration link and complete the checks shown during signup. Open Create scenario and give the workflow a name that identifies the practice task. Start with the smallest available setup appropriate to the selected modules. Do not purchase an annual subscription solely to follow a basic example before confirming what the account already supports.

Add the spreadsheet trigger

Add Google Sheets > Watch New Rows and authorize the account with access to the practice sheet. Select the spreadsheet, worksheet and header setting, and keep the first result limit to one. Choose a starting point that includes only the intended practice data. Selecting all historical rows on a populated business sheet can create a burst of real downstream actions.

Map a short, useful Slack message

Add Slack’s message-creation action and select the connection and practice channel. Start with request ID, category and a short summary. Map those values from the spreadsheet output instead of typing the sample values as constants. The result should let someone identify the request without distributing the entire submission to everyone who can read the channel.

Test the result, not only the success indicator

Save the scenario and use Run once. Compare the source row, module output and actual Slack post: TEST-001 should appear once with matching values. An empty field calls for checking the source and mapping in that order. Repeating a test can send another real message, so keep the destination isolated and do not interpret a green run alone as proof of correct delivery.

A practical first-run troubleshooting order

If the spreadsheet produces no output, check the worksheet, starting point, new input and result limit. If it produces output but Slack receives nothing, inspect the connection, filter, destination and permissions in sequence. If the message contains fixed sample values, revisit the mapping rather than changing the trigger.

Change one cause at a time. Use a new practice request ID after a correction and save the expected and actual result. This is more informative than repeatedly clicking Run once after changing several unrelated fields. It leaves a short troubleshooting history the next operator can understand.

Activate only after a second input behaves correctly

Add TEST-002 and verify that the new row produces the intended notification without replaying TEST-001. Then choose the schedule and enable it. Record the owner, how to stop the workflow and when to review credit usage. For a form-driven process, continue to the dedicated intake guide, which also covers the response sheet and notification state.

• Send Google Forms responses to Slack with Make and Google Sheets
• Make pricing: choose a free or paid plan around your workload
• How to estimate Make credits: polling, rows and retries
• Handle Make errors: execution history, incomplete runs and safe retries