Archive Slack messages as Google Drive text files

Save Slack messages containing [Archive] as UTF-8 text files in Google Drive. Connect Slack and Google Drive, choose source channels and optionally browse to a destination folder. The [Archive] keyword is prefilled and matched anywhere without case sensitivity; bot messages are ignored. Each file contains the original message text, author ID, channel ID, message timestamp and a source channel URL. The filename uses the workspace, channel and message timestamp with a .txt extension. Leaving Parent folder empty saves to My Drive. Includes its own fictional English Bremen handoff example. Add FastHook to the source Slack channel before activation. Leaving Channels empty watches every channel accessible to the connection. Matching human thread replies also create files. Existing messages, edits and deletions are not synchronized; attached files and thread history are not copied. Slack formatting and mentions remain source text. This is a message capture, not a full workspace backup. Files inherit the destination folder access; no public sharing action is added. Manual reruns can create duplicate files.

Use this templateCreates a new Draft · no credentials copied

What gets copied

The working graph, not another user's secrets

FastHook recreates every Step, route, field mapping, and setting with new IDs in your workspace.

Action 1 · Google Drive

Save Slack message as a text file

Create a UTF-8 file in My Drive or a selected folder.

Before activation

Connect your accounts in the Draft

Slack

Connect your own Slack account and review the provider settings used by this Workflow.

Google Drive

Connect your own Google Drive account and review the provider settings used by this Workflow.

Create my Workflow

Questions

Template FAQ

Does the template copy someone else's credentials?

No. FastHook creates a disconnected Draft. Connect your own Slack, Google Drive accounts before activation.

Can I change the Steps and mappings?

Yes. The copied Workflow is an editable Draft. Review every Step, input, mapping, and route before you activate it.

What is copied into my workspace?

FastHook recreates the Trigger configuration, Action Steps, routes, and mappings with new IDs. Provider accounts, credentials, and secrets are never copied.

When does the Workflow start running?

Only after you connect the required accounts, finish the configuration, and explicitly activate the Draft.