Slack logo
Microsoft OneDrive logo

Workflow template

Save tagged Slack messages as OneDrive text files

Save selected Slack messages as text files in Microsoft OneDrive. Add [OneDrive] to a new human message in a chosen channel; the workflow captures its text and source metadata.

How it works

From a tagged Slack message to a OneDrive text file

1 Trigger · 1 Action
Slack1 · Trigger

New Keyword Mention

Receive new human messages containing [OneDrive] in the selected channels. Matching is case-insensitive and bot messages are ignored.

Microsoft OneDrive2 · Action

Save the selected Slack message

Write a UTF-8 text file containing the captured message, author and channel IDs, timestamp and source channel URL. The filename uses the workspace, channel and message timestamp.

The result

A readable copy of the selected message

Example OneDrive text file

[OneDrive] FICTIONAL Köln handoff — Grüße. The review checklist is ready. Author ID: UEXAMPLE21 Channel ID: CEXAMPLE21 Message timestamp: 1794787200.000021 Source channel: https://app.slack.com/client/TEXAMPLE21/CEXAMPLE21

Fictional Slack data. Message text and the included metadata become visible to readers of the OneDrive destination. Opening the original Slack channel still requires Slack access.

Before activation

Set up your workflow

  1. Choose Slack channels

    Connect Slack, add FastHook to the source channel and select the channels to monitor. Keep [OneDrive], Ignore bot messages and case-insensitive matching. Empty Channels means all accessible channels.

  2. Choose the OneDrive destination

    Connect OneDrive. Optionally add a Parent folder mapping and choose a folder you control; without one, files are saved in the OneDrive root.

  3. Send a fictional tagged message

    Activate, wait for the Slack trigger to be ready, then post a fictional message containing [OneDrive]. Open its generated file in OneDrive and compare the text and source metadata.

Details and limitations
  • Message text is copied. The file contains the complete captured message text plus author ID, channel ID, timestamp and source channel URL. Attached files, thread history, profile names and email addresses are not separately fetched; the message text itself may contain private information.

  • An explicit marker chooses messages. [OneDrive] is matched anywhere without case sensitivity. Matching human thread replies are included, while bot messages are ignored. Select source channels to limit the scope.

  • A capture, not synchronization. Older messages, edits and deletions are not synchronized. Slack formatting and mentions remain source text. The source URL opens the channel rather than guaranteeing a direct link to that message.

  • Reruns can replace the same file. The filename uses the workspace, channel and message timestamp. Different messages have different names; reprocessing the same message writes the same path and can replace edited file contents. Files inherit destination access, without a public sharing action.

Questions about this template

Which Slack messages are saved?

New human messages containing [OneDrive] in the selected channels. The marker is matched anywhere without case sensitivity, and matching human thread replies are included. Empty Channels means all accessible channels.

Are attachments and thread history archived too?

No. The workflow captures the selected message text and source metadata. It does not download attached files or fetch thread history and user profiles.

Where does OneDrive save the file?

In the folder selected through a Parent folder mapping, or in the OneDrive root when no parent is supplied. File access follows the destination’s existing permissions.

What happens if I rerun the same message?

The same workspace, channel and timestamp produce the same filename. The upload can replace that file’s contents. Separate messages have different names; later Slack edits and deletions are not automatically synchronized.