AI AGENTS
Slack-dropped Loom link to Notion runbook
When someone posts a Loom link in a designated Slack channel, transcribe and rewrite it into a Notion runbook page, then reply in-thread with the new doc link.
How it runs
The automated pipeline, trigger to output.
- TriggerNew message in Slack channelSlack
- LogicFilter: message contains a Loom URL
- ActionFetch Loom transcriptLoom
- ActionRewrite transcript into runbook formatHugging Face
- ActionCreate runbook page in NotionNotion
- OutputReply in Slack thread with Notion linkSlack
What it does
Watches a Slack channel for Loom links and instantly converts each shared walkthrough into a written runbook in Notion, replying in the same thread so the doc lives next to the conversation.
When to use it
Use it when your team's default move is 'I'll just record a Loom' and drop it in Slack, but those recordings vanish into channel history. This captures the knowledge as a durable Notion page without anyone leaving Slack.
How it works
- 1A new message in the watched Slack channel triggers the flow.
- 2A logic step checks the message for a loom.com URL and exits if none is present.
- 3The agent fetches the transcript for that Loom recording.
- 4A Hugging Face model rewrites the transcript into a titled runbook with numbered steps, prerequisites, and a gotchas section.
- 5The agent creates the page in the team's Notion runbook database.
- 6The flow replies in the original Slack thread with the Notion link so context stays attached.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect LoomVideo transcripts, libraries.
- 3Connect Hugging FaceModels, datasets, spaces — the open-source hub.
- 4Connect NotionPages, databases, comments.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.