Quick overview This workflow takes a video idea sent via Telegram, uses OpenAI to generate a Seedance 2.0-ready prompt plus platform-specific captions, creates the video through AtlasCloud’s Seedance API, then publishes it to TikTok, Instagram, and YouTube using Blotato and confirms back in Telegram. How it works Receives a video idea as a Telegram message. Uses OpenAI (via an agent) to generate a structured JSON payload containing a Seedance 2.0 text-to-video prompt plus TikTok and Instagram captions and a YouTube title and description. Submits the prompt to AtlasCloud’s Seedance 2.0 video generation API and requests a 5-second video. Polls AtlasCloud every 30 seconds until the video generation status returns completed/succeeded. Extracts the final video URL and pairs it with the generated captions and YouTube metadata. Publishes the video to TikTok, Instagram, and YouTube via Blotato, then sends a Telegram confirmation message. Setup Create a Telegram bot and add Telegram credentials, then ensure the trigger and confirmation nodes use the correct bot and chat settings.
Tags
OpenAI Chat Model
Structured Output Parser
TelegramRelated workflows
See all AI Automation→
CWReport workflow errors to Asana tasks with Google Chat and Grok 4.5 analysis
Quick overview When a monitored workflow fails, this reads its Description field to find the owning client and assignee, looks them up in Asana, analyses the error with Grok 4.5, and creates an assigned task with a severity-based due date. Repeat failures comment on the existing task. How it works Any workflow that names this one as its error workflow triggers it on failure. There is no production trigger by design. The error payload only carries a workflow ID, so an HTTP Request calls the n8n API to read that workflow's own Description field, which holds a small JSON object naming the client and the assignee. Asana projects and users are fetched live and matched by name, so no GID is ever hardcoded. A failed match raises a warning that travels downstream instead of failing silently. Asana is searched for an open task covering the same workflow and node. If one exists, a comment carrying the new execution ID is added rather than a duplicate task. For a new error, Grok 4.5 via OpenRouter returns a root cause, a solution, concrete steps, a severity, and a category, held to a fixed shape by a structured output parser. Severity sets the due date: Critical today, High tomorrow, Medium i
Draft personalized cold emails from Google Sheets using Gemini and HubSpot
Quick overview This workflow batch-processes leads from Google Sheets, researches each person and company using Tavily plus Google Gemini, drafts a personalized cold email, then creates/updates the contact in HubSpot with a research note and a saved email draft before marking the lead as Done in the sheet. How it works Runs manually and sets a batch size that controls how many leads to process per run. Reads leads from Google Sheets, skips rows already marked as Done, and normalizes the selected batch into clean lead fields. Processes the batch one lead at a time and uses Tavily search (last 60 days) with Google Gemini to extract the most recent public activity, pain points, and a personalization hook. Cleans and parses the research JSON so it can be reused reliably downstream. Uses Google Gemini to draft a 90–120 word cold outreach email (subject and body) that incorporates the research and offers a free “Automated LinkedIn Post Creator” n8n workflow. Creates or reuses the HubSpot contact, logs a HubSpot note with the research and drafted email, and saves the email as a HubSpot engagement in DRAFT status. Updates the matching row in Google Sheets (by Email) to set Status to “Done
AI: Summarize podcast episode and enhance using Wikipedia
The workflow automates the process of creating a summarized and enriched podcast digest, which is then sent via email. Note that to use this template, you need to be on n8n version 1.19.4 or later.