Blog post workflows

From a finished webinar, produce a blog draft in Notion plus a matched set of pull-quote graphics and platform-tailored social copy.

An agent takes a published episode, transcribes it, then autonomously produces and routes the complete asset pack — show notes to Notion, blog post to the CMS.

When you publish a GitHub release, this workflow rewrites the raw release notes into three tailored versions — a long-form blog post, a short in-app announcement.

A webhook kicks off translation of a chosen post into requested locales, runs a glossary check.

Accepts a webhook with an article URL and a target language, scrapes and translates the piece into a narration script, dubs it with ElevenLabs in that locale, renders a clip.

Daily, it joins help-center search queries that returned zero results with tickets that had no KB match, drafts an article when docs can fix it.

When a Zendesk tag's ticket volume spikes above its baseline, an agent investigates the cluster, decides whether it's a known issue or a documentation gap.

When an article is flagged as decaying, an agent reads the recent tickets it failed to deflect, drafts an updated version with OpenAI.

Scans Zendesk macros against linked Confluence articles weekly and opens a deduplicated Linear issue for each macro that contradicts current docs.

When a Zendesk ticket is solved, checks whether any Confluence article could have deflected it; if not, files a Linear doc-gap task so the missing self-serve content gets written.

On a new published post (via RSS/webhook), scrape the article, draft X and Threads variants.

When a draft post is submitted in Notion, this workflow drafts a narration script and posts it to Slack for editor sign-off.

Every Friday this workflow pulls the week's published blog posts from Notion, writes a cohesive roundup script, narrates it as one episode with ElevenLabs.

Accepts a blog draft via webhook, builds a localized asset pack with images, saves everything to a Google Drive folder, and posts a review link to Slack for sign-off.

Each month, correlates the prior month's Confluence KB edits with closed Front conversations to estimate how many would now be self-served.

Every Monday, monitors a tracked list of competitors across web and their changelog pages, summarizes what changed in the last week, and posts a ranked digest to Slack.

On each low CSAT rating in Zendesk, an LLM diagnoses whether a missing or wrong help article caused the bad experience and, when it did, opens an Asana task to fix the specific…

Watches a Google Drive folder for new article drafts, generates a narration script and a preview voiceover.

An agent takes a thought-leadership theme, researches supporting evidence across the web, drafts a long-form opinion piece with citations, routes it to Slack for sign-off.

A webhook submits an article URL or text, the system drafts a narrated MP3 and hero image, then posts both to Slack for a reviewer to approve or reject before final delivery.

When a silent or rough Loom screen recording lands, generate a polished narration script, synthesize voiceover audio, and produce a matching written help article draft in Notion.

On a new published post, this pulls recent post-performance data, has OpenAI write variants biased toward the styles that performed best, posts them, and logs each variant…

When a Notion blog post is marked Ready, it is condensed into a tight script, narrated in multiple languages with ElevenLabs, paired with B-roll.

On a daily schedule, this crawls your blog's RSS feed for new posts, writes a single spoken digest with OpenAI, narrates it, and posts the audio link to Discord.

An agent-driven content desk that ingests a new episode, plans the full asset set across formats, delegates clip/blog/social production.

Submit a Loom URL via webhook and get back a polished step-by-step help article in Google Docs plus a ready-to-paste Zendesk macro answer.

On every new item in your blog's RSS feed, this drafts a community announcement plus social variants with a generated image, posts the announcement to Discord.

On a manual run, this workflow narrates a chosen blog post with ElevenLabs, generates episode cover art, writes feed metadata.

Triggered by a webhook with a blog URL, it builds a draft image carousel and posts it to Slack for approval before anything goes live on social.

When a post goes live, it writes a tight audio script, narrates it with text-to-speech, stores the file, and shares the clip plus link in your community Discord.

Send a blog URL to a webhook and this scrapes the article, breaks it into key points, generates one image per point as a carousel, writes the caption.

On a schedule it checks your blog's RSS feed, scrapes each new article, narrates it with ElevenLabs, generates a cover image.

On a new Loom recording, an agent reads the transcript, decides whether it is a public help article, an internal runbook, or a bug repro, and routes a drafted version to ReadMe.

On a weekly schedule, scrapes the latest published posts from your blog, writes a single recap script covering all of them, narrates it with ElevenLabs.

When a new article URL is submitted, it scrapes the text, narrates a short teaser with ElevenLabs, generates an audiogram cover image.

Groups recent Intercom conversations by recurring intent, and for the most common topics with no canned reply.

An agent takes a published blog post, drafts tone-matched newsletters per segment, verifies claims against the source, posts drafts to Slack for approval.

On a schedule, reads unanswered gap questions, searches Confluence for the relevant policy or help article, and drafts a ready-to-review canned reply snippet for each.

An agent reviews resolved Gmail support threads, decides which freehand answers deserve a help-center article, drafts them, and saves the docs to a Google Drive folder…

Weekly, matches recent repeat tickets against existing Notion help articles to find docs that exist but are not preventing tickets.

When an Intercom resolution bot fails to deflect a conversation and it escalates to a human, this captures the unanswered question, drafts a Notion KB article on the spot.

On each new Intercom conversation, checks whether the customer's question is covered by an existing help-center article and, if not, alerts the team and logs the uncovered…

On a weekly schedule, clusters the past week's Front conversations by topic, flags clusters that have no matching knowledge base article.

Mines tickets that received a negative satisfaction rating and had no article to point.

On each new Zendesk ticket, checks whether any help center article covers the question; if not, logs the gap to Linear and pings the docs channel in Slack so coverage grows over…

Each quarter, scores every published post for stat decay and sends a ranked Slack digest of which articles need updating, with the specific outdated numbers called out.

When a new post hits the blog RSS feed, this drafts platform-specific social posts, sends them to Slack for one-click approval.

On every inbound Intercom message, checks whether the answer bot found a confidently-relevant article; if retrieval comes back empty or low-confidence, it posts the question…

Splits a published blog post into themed newsletter installments, writes each as a row in an Airtable content calendar with a staggered send date.

On a schedule, this workflow finds newly published posts, narrates short ones automatically with ElevenLabs.

Weekly, it scans closed Zendesk tickets that never linked to a help-center article, clusters them by theme, drafts a new article for each gap.

When a Confluence help-center article is published or updated, immediately checks which Zendesk macros cite it and flags any whose canned answer now contradicts the new version.

Finds Zendesk macros that aren't linked to any help-center article, uses the LLM to match each to the most relevant Confluence doc.

Each night, compares every Zendesk macro against its linked Confluence help-center article and flags macros whose canned text now contradicts the current published doc.

Watches incoming Zendesk tickets for a sudden spike in a single topic with no existing article.

When an Intercom conversation closes, detects whether the resolved question is already covered in Confluence and, if not, drafts a new Confluence page from the agent's reply…

When an agent applies a Zendesk macro, an inline webhook check verifies the canned reply against the live help-center article and warns the agent before send if it contradicts…

When a Confluence KB article is published or updated, scans recently closed Zendesk tickets to find ones the new content would now auto-answer.

Every Friday this picks the week's top-performing blog post, writes an email-newsletter version in a friendly subscriber tone, generates a short narrated audio teaser.

When the concierge has to escalate because no help-center article covered the user's onboarding question, it logs the documentation gap and files a Linear task to write…