Slack to Google Sheets — Integration Setup Guide

Slack to Google Sheets — Integration Setup Guide

Log Slack activity into a spreadsheet automatically. No code required. Setup time: about 20 minutes. Difficulty: Beginner. Method: Slack Workflow Builder.

Overview

This guide connects Slack to Google Sheets using Slack's built-in Workflow Builder. When something happens in Slack — a teammate submits a form, posts in a channel, or reacts to a message — the workflow writes a row to your sheet.

How it flows:

Slack event: form submitted, message posted, or reaction added.

Slack Workflow Builder runs the workflow.

The Google Sheets step appends a row: Timestamp, User, Channel, Message.

Example result: a support-request log that fills itself in, with columns for Timestamp, User, Channel, Request, and Priority.

Prerequisites

Check each item before you start:

Slack paid plan (Pro, Business+, or Enterprise Grid).

Permission to create workflows — ask your workspace admin if you cannot see Create in Workflow Builder.

A Google account with permission to edit the destination sheet.

A prepared spreadsheet with a header row.

The channel(s) you want to log, and a test message ready to send.

Warning: Do not log channels that contain passwords, personal data, or client-confidential information. A spreadsheet is much easier to share by accident than a Slack channel. Decide what is safe to log before you connect anything.

Step 1 — Prepare your Google Sheet

Open Google Sheets and create a new spreadsheet. Name it something clear, for example: Slack Request Log.

In Row 1, type your column headers: Timestamp, User, Channel, Message, Link.

Freeze Row 1 so the headers stay visible: View, then Freeze, then 1 row.

Leave the sheet empty below the headers. The workflow fills it in.

Note the exact spreadsheet name — you will select it in Step 4.

Tip: Keep header names short and single-word where possible. Short headers map cleanly in the workflow editor and survive exports.

Step 2 — Open Workflow Builder

In Slack, click your workspace name in the top-left corner.

Go to Tools and settings, then Workflow Builder. (In newer Slack versions: Automate, then Workflow Builder.)

Click Create in the top-right corner.

Name the workflow, for example: Log #help-desk requests to Sheets, and click Next.

Step 3 — Choose your trigger

The trigger is the Slack event that starts the workflow. Pick the one that matches your goal:

From a shortcut: a teammate clicks a button on a message to log it.

From a channel: every message in a channel is logged.

When a reaction is added: a checkmark or eyes reaction means "log this".

From a form: structured input (request type, priority, due date).

Scheduled date and time: a recurring summary, not per-message logging.

For this guide, select From a form.

Select From a form as the trigger.

Click Add step, then Collect information in a form.

Add your form fields:

Request — long text — required.

Priority — dropdown: Low, Medium, High — required.

Channel — short text — optional.

Click Save.

Step 4 — Add the Google Sheets step

Click Add step, search for Google Sheets, and select Add a row to a spreadsheet.

If prompted, click Connect Google account and sign in with the Google account that owns the sheet. Grant access only to Google Sheets.

Under Spreadsheet, select Slack Request Log.

Under Sheet, select Sheet1 (or your tab name).

Map each column to a value:

Timestamp: Workflow run date (built-in variable).

User: User who submitted the form.

Channel: Channel where the workflow ran.

Message: Request (form field).

Link: Message link (built-in variable).

Click Save.

Warning: The Google account you connect is the account the workflow writes as. If that person's access to the sheet is removed later, the workflow stops writing rows. Use a stable shared or service account where your workspace allows it — never a personal account that might be deleted.

Step 5 — Publish the workflow

Review the workflow summary: Trigger, Form, Google Sheets step. Every step should show a green checkmark.

Click Publish in the top-right corner.

Slack confirms: Your workflow is live.

Step 6 — Test it

Open the channel where the workflow lives and run it: click the Shortcuts button and submit the form with a test request, for example: TEST — please ignore.

Open your Google Sheet. A new row should appear within a few seconds.

Check that every column landed in the right place — especially Timestamp and User.

Note: The first run can take up to 60 seconds. If the row does not appear, wait one minute and refresh the sheet before changing anything.

Step 7 — Share it with the team

In Workflow Builder, open your workflow, go to Settings, and confirm who can use it.

Post a short announcement in the channel explaining the new logging and how to use the shortcut or form.

Pin that message so new teammates find it.

Verification and testing

Run these three checks before calling the setup done. All three must pass.

Submit a test form with all fields filled. Expected result: a complete row appears in the sheet within 60 seconds. If it fails: re-open the workflow and confirm the Google Sheets step is connected to the right spreadsheet.

Submit a test with an empty optional field. Expected result: row appears with that cell blank — no error. If it fails: check that the optional field is not marked required in the form.

Check the workflow run history. In Workflow Builder, open your workflow and check Activity. Expected result: the run shows as Completed. If it fails: a Failed run lists the exact error — usually a revoked Google connection or a renamed sheet tab.

Tip: Keep your first three test rows in the sheet and label them TEST in the Message column. They prove the integration works, and you can delete them once the team starts using it for real.

Best practices

One workflow, one purpose. A workflow that logs everything becomes a junk drawer. Build separate workflows for requests, incidents, and feedback.

Freeze the header row and protect it. In Google Sheets: select Row 1, then Data, then Protect sheet, and restrict editing to yourself.

Never log secrets. Passwords, API keys, and personal data do not belong in a spreadsheet.

Name workflows like files, not like jokes. "Log #help-desk requests to Sheets" beats "Magic Logger 3000" when someone else has to fix it in six months.

Review the Activity log weekly for the first month. Failed runs are silent — nobody gets an error message in Slack.

Reconnect Google promptly after password changes. If the connected Google account changes its password or loses access, the workflow fails without warning.

Archive, don't delete, old workflows. Set unused workflows to Unpublish instead so you can read the Activity log later.

Sample documentation prepared as a portfolio piece. Workspace names, channels, and user handles are fictional. Slack interface labels may vary slightly by version; the workflow structure is the same across current Slack releases.