Generate AI avatar videos with GPT-5 & publish to social media platforms
This workflow contains community nodes that are only compatible with the self-hosted version of n8n. Automate Social Media with HeyGen and GPT-5: Publish Videos to TikTok, YouTube & Instagram --- π₯ Who is this for? This workflow is designed for: Content creators who want to scale their short-form video production Marketing teams seeking consistent and automated publishing pipelines Agencies managing multiple social accounts for clients Entrepreneurs looking to save time by automating repetitive content tasks --- π‘ What problem is this workflow solving? Publishing on multiple platforms like YouTube Shorts, TikTok, and Instagram is often: Time-consuming (manual editing, caption writing, uploads) Inconsistent (different requirements for each platform) Prone to delays (switching between tools) This workflow solves these issues by creating a fully automated video pipeline powered by GPT-5, HeyGen, and Blotato. --- βοΈ What this workflow does Capture voice idea via Telegram Transcribe voice to text using OpenAI Whisper Generate a catchy title and caption with GPT-5 Create an AI avatar video with HeyGen Save and organize assets in Google Drive and Google Sheets Upload final video to Blotato Auto-publish to: YouTube Shorts TikTok Instagram (Optional: Facebook, X/Twitter, LinkedIn, Pinterest, Threads, Bluesky) Update logs in Google Sheets Send a Telegram confirmation once published --- π§° Setup Before using this workflow, ensure you have: A Telegram Bot connected to n8n for voice input An OpenAI API key for transcription (Whisper) and GPT-5 processing A HeyGen account & API key for avatar video generation A Google Drive & Google Sheets integration for storing assets and logs A Blotato account (Pro plan) with API access enabled Verified Community Nodes enabled in n8n Admin Panel Blotato node installed and credentials configured --- π οΈ How to customize this workflow Prompts β Adjust GPT-5 prompts to match your brand voice and niche Avatars β Use custom avatars or voices via HeyGen configuration Platforms β Activate only the social nodes you need (e.g., focus on TikTok & YouTube Shorts) Approval steps β Add Telegram or Slack confirmation before publishing Analytics β Extend the workflow to track engagement data in Google Sheets, Airtable, or Notion --- This workflow turns a simple spoken idea into a viral-ready video β automatically generated, styled, and posted across your most important platforms. --- π Documentation: Notion Guide --- Need help customizing? Contact me for consulting and support : Linkedin / Youtube
Automated replies to X threads with Airtop browser automation
Use Case Automatically responding to X (formerly Twitter) posts can help you engage with potential customers at scale, saving time while maintaining a personal touch. What This Automation Does This automation replies to specified X posts using the following input parameters: airtop_profile: The name of your Airtop Profile connected to X. thread_url: The URL of the X post to reply to. Example reply_text: The message you want to post as a reply. How It Works Creates a browser session using Airtop. Navigates to the specified X post. Types and submits the reply text. Setup Requirements Airtop API Key β free to generate. An Airtop Profile connected to X (requires one-time login). Next Steps Combine with X Monitoring: Use this with the X monitoring automation to create a fully automated engagement pipeline. Extend to Other Platforms: Adapt the automation for use on LinkedIn, Reddit, or any web community. Read more about this Airtop Automation.
Auto-resolve Jira tickets with GitHub Copilot using Port Context
Auto-resolve Jira tickets with coding agents Coding agents can significantly speed up development, but crucial engineering context often gets lost in the process. This guide demonstrates how to use Port as a context lake in n8n workflows to automatically generate GitHub issues from Jira tickets with rich organizational context, ensuring that important information is preserved when assigning them to GitHub Copilot and linking pull requests back to Jira. This setup helps establish a seamless ticket-to-PR workflow, bridging the gap between Jira and GitHub while leveraging Port's comprehensive software catalog as a source of truth. How it works The n8n workflow orchestrates the following steps: Jira trigger β The workflow listens for Jira issue updates via webhook. Condition check β Verifies that the issue status is "In Progress" and has the required label (e.g., "productapproved") without the "copilotassigned" label. Port context extraction β Uses Port's n8n node to query your software catalog for relevant context about services, repositories, teams, dependencies, and documentation related to the Jira issue. Parse response β Retrieves the AI-generated GitHub issue title and body from Port. Create GitHub issue β Creates a new GitHub issue with the enriched context from Port. Assign to Copilot β Adds a comment to the GitHub issue instructing Copilot to take ownership. Add issue link to Jira ticket β Adds a comment to the Jira ticket with the GitHub issue URL, providing clear traceability. Mark ticket as assigned β Updates the Jira ticket to add the "copilot_assigned" label, preventing duplicate processing. Setup [ ] Connect your Jira Cloud account and enable issue_updated events [ ] Register for free on Port.io [ ] Connect your Port.io account and add the API key [ ] Connect your GitHub account and select the target repository [ ] Ensure a Copilot bot or @copilot user has access to the repository [ ] Confirm the workflow webhook or Jira trigger URL is active [ ] Test by moving a product_approved ticket to In Progress. [ ] You should be good to go! Prerequisites You have a Port account and have completed the onboarding process. Port's GitHub app is installed in your account. Port's Jira integration is installed in your account. You have a working n8n instance (Cloud or self-hosted) with Port's n8n custom node installed. Your GitHub organization has GitHub Copilot enabled, so Copilot can be automatically assigned to any issues created through this guide. β οΈ This template is intended for Self-Hosted instances only.