Daily SharePoint changes digest in Slack

Build an agent workflow that posts a daily "what changed in SharePoint" digest into Slack every weekday morning so important documents do not sit unread.

Trigger: cron, every weekday (Monday through Friday) at 8:00 AM in the user's configured time zone.

Configuration the user provides at setup time: (1) one or more SharePoint document libraries or folders to watch, identified by site and library or drive plus optional folder path, (2) the target Slack channel to post the digest to, (3) the time zone for the 8am schedule, and (4) optional skip rules (folder names, file name patterns, or document types to ignore).

Each run, the agent should:

1. For every configured library or folder, use Microsoft SharePoint's Search Drive Items operation (or List Folder Children when the user pinned a specific folder) to find files that were created or last modified in the previous 24 hours. Resolve site, drive, and folder addressing through the standard Microsoft Graph site and drive item paths. Page through results until all matching items are collected.

2. Filter the candidate list before downloading. Skip: items larger than the simple-download limit (250 MB), system-generated files, obvious template files, hidden files, and anything matching a user-configured skip rule. Treat a same-day create-then-modify as a single "new" item, not two events.

3. For each surviving item, call SharePoint's Download File Content operation to fetch the file body, then write a two-to-three sentence summary covering: what the document is, why it likely matters to the team, and who created or last modified it. Use the file's name, folder path, and last-modified-by metadata to enrich the summary. For non-text formats (PDFs, Office docs), summarize from the extracted text. If a file cannot be parsed, fall back to a short metadata-only line so it is not silently dropped.

4. Group the summaries by folder or document type. Suggested buckets: Contracts, SOWs, Policies, Meeting decks, and an "Other" catch-all. If the user's folders make a different grouping more natural (e.g. by library), prefer that. Within each group, sort newest first.

5. Build a single Slack digest message using Slack mrkdwn. Header line should say "SharePoint changes for <date>" and include the total count. Each item should render as a bullet with a clickable link to the file's SharePoint webUrl (use the file name as the link text), followed by the two-to-three sentence summary and a small "updated by <person>" tag. Keep the post compact enough to fit in one Slack message; if it would exceed Slack's message size, post the overflow as threaded replies under the main message.

6. Post the digest to the configured Slack channel using Slack Bot's Send a Message operation. Use the slackbot integration (not the user OAuth slack integration) so the digest is attributed to the bot and keeps working regardless of which person originally set it up.

7. If no files changed in the last 24 hours, post a single short line like "No SharePoint changes in the last 24 hours" rather than skipping the run silently, so the team knows the workflow ran.

Edge cases to handle gracefully: SharePoint throttling (respect Retry-After), pagination across large libraries, files the connected account cannot read (skip with a logged note, do not fail the whole run), and Slack rate limits on chat.postMessage.

This is an agent workflow because per-file summarization, noise filtering, and grouping are reasoning steps, not deterministic transforms.