Workflow Templates

Community Node Disclaimer: This workflow uses KlickTipp community nodes. How It Works Automate transactional emails from KlickTipp via SMTP This workflow receives contact data from a KlickTipp Outbound rule, generates a personalized HTML email, and sends it via any SMTP-compatible service (e.g., Gmail SMTP, Outlook, SendGrid, your own mail server). Key fields (e.g., first name, company, website, phone, or other custom fields) can be dynamically mapped into the body. After sending, the workflow saves the email’s HTML content and writes back an Email delivery status (“Sent” or “Failed”) to the contact in KlickTipp for clear visibility. Key Features KlickTipp Outbound Trigger Starts when a KlickTipp Outbound rule calls the webhook (e.g., after a tag is applied). Accepts payload with recipient email and optional custom fields (first name, company, website, phone, etc.). Easy to adapt for confirmations, updates, welcomes, and announcements. HTML Email Composer Builds a clean, brandable HTML template with safe fallbacks. Supports per-contact personalization via mapped fields. SMTP Delivery Sends emails using the n8n Send Email node (SMTP). Works with Gmail, Outlook, or any SMTP-compatible service. Supports From/Reply-To, Subject, HTML body, CC/BCC, and attachments. Delivery Status Write-Back On success: updates a KlickTipp custom field (e.g., Email delivery status = Sent). On error: updates the same field to Failed (error details available in execution logs). Setup Instructions Install and Configure Nodes Add/enable KlickTipp community nodes and authenticate with valid API credentials. Configure an SMTP credential in n8n: Host (e.g., smtp.gmail.com) Port (465 or 587) Authentication (username, password, or app password) SSL/TLS settings as required by your provider Select this credential in the Send Email node. Paste/import your HTML into the Generate HTML template node. Activate the workflow. Workflow Logic Trigger from KlickTipp: Outbound sends contact data to the workflow. Generate HTML: Build personalized HTML (and optional plain-text). Send via SMTP: Deliver the message with the Send Email node. On Success: Update KlickTipp contact → Email delivery status: Sent. On Error: Update KlickTipp contact → Email delivery status: Failed (see logs for details). Benefits Immediate, personalized communication** without manual steps. Consistent branding** with reusable HTML templates. Clear observability** by writing back delivery status to KlickTipp. Flexible & extensible** for many message types beyond payments. Testing and Deployment Tag a test contact in KlickTipp to trigger the Outbound rule. Verify the email arrives with correct personalization. Confirm the Email delivery status field updates to Sent (or Failed for negative tests). Review execution logs and adjust field mappings if necessary. Notes Customization:** Swap templates, add CC/BCC, attachments, or a plain-text part for deliverability. SMTP Provider Settings:** Refer to your email provider’s SMTP configuration (e.g., Gmail, Outlook, or custom server).

YouTube Caption Extractor (Your Channel Only) Extracts clean transcripts from YOUR CHANNEL YouTube video captions using YouTube Data API v3. ⚠️ API Limitation: Only works with videos from YOUR OWN CHANNEL. Cannot access external/public videos. 🎯 Use Cases AI summarization & sentiment analysis Keyword extraction from your content Content generation from your videos Batch transcript processing 🔄 How It Works (6 Steps) 📥 Input: Receives videoId + preferredLanguage 🔍 API: Lists captions from your channel 🆔 Selector: Picks preferred language (fallback to first) 📥 Download: Gets VTT subtitle file 🧹 Cleaning: Removes timestamps, [Music], duplicates ✅ Output: Clean transcript + metadata 🚀 How to Use Trigger with JSON payload: {"youtubeVideoId": "YOUR_VIDEO_ID", "preferredLanguage": "es"} Video ID must belong to your authenticated YouTube channel** Works as sub-workflow (Execute Workflow Trigger) or replace with Webhook/Form trigger Handles videos with no captions gracefully with structured error response Output ready for downstream AI processing or storage ⚠️ Setup Required: Change YouTube credentials* in *"List Captions"* and *"Download VTT"** nodes Video ID from your authenticated channel Sub-workflow or Webhook trigger Graceful no-captions handling 🔧 Requirements ✅ YouTube OAuth2 (youtube.captions.read scope) ✅ Update credentials in List Captions + Download VTT nodes ✅ n8n HTTP Request + Code nodes 💬 Need Help? n8n Forum Happy Automating! 🎉

How it works This workflow helps you stay on top of your inbox without constant interruptions. Every afternoon, it automatically: Fetches all emails received in your inbox throughout the current day. Intelligently summarizes the key content of these emails using AI, providing a concise overview. Compiles these summaries into a single, organized digest. Sends you a single email containing the aggregated summary of your day's correspondence. Efficiently review your daily communications and focus on what truly matters, all in one convenient digest! Set up steps Setting up this workflow is straightforward and typically takes around 10-15 minutes. You'll need to: Authenticate your preferred email service (e.g., Gmail). Obtain API keys for your preferred AI service (e.g., OpenAI, Google AI). Specify the email address where you want to receive the digest. All detailed setup instructions and specific configuration guidance are provided within the workflow itself using sticky notes.

Automated Research Paper Analysis Pipeline This workflow automatically analyzes research papers by: Parsing PDF documents into clean Markdown format Extracting key information using AI analysis Generating concise summaries and insights Storing results in a database for future reference Perfect for researchers, students, and academics who need to quickly understand the key points of multiple research papers. How it works: Trigger: Manual trigger or webhook with PDF URL PDF Vector: Parses the PDF document with LLM enhancement OpenAI: Analyzes the parsed content to extract key findings, methodology, and conclusions Database: Stores the analysis results Output: Returns structured analysis data Setup: Configure PDF Vector credentials Set up OpenAI API key Connect your preferred database (PostgreSQL, MySQL, etc.)

Stripe → Pipedrive (Automatic Person + Deal Creation) Prerequisites / Requirements n8n instance (cloud or self-hosted) with HTTPS reachable webhook endpoint Stripe account and secret API key Pipedrive account with API access and custom fields defined Users should create custom fields in Pipedrive and copy their field IDs (e.g. amount, payment method, status, Stripe Event ID) How it works (Step-by-Step) Stripe Webhook: n8n triggers on payment events from Stripe via an HTTP POST. Edit / Set node: Extracts eventId, eventType, and payload. HTTP Request: Confirms Stripe event via Stripe API (adds security). Search Person: Looks up Pipedrive contact by email from the Stripe payload. IF: Checks whether the person exists. If exists → skip to deal creation. If node - Check if Event id is not the same If same - Skip the deal creation If different - Create a deal linked to that person with the payment amount If not → create new Person. Create Person: Adds new Pipedrive contact, populates custom fields (amount, payment method, status, source). Create Deal: Creates a deal linked to that person with the payment amount. Description **This workflow connects Stripe to Pipedrive. Whenever a new payment (or checkout success) occurs in Stripe, this automation will: Fetch the full Stripe event data Find or create a customer (“Person”) in Pipedrive Create a “Deal” record corresponding to that payment Log custom fields like amount, source, payment method, status It’s ideal for SaaS Subscription businesses Agencies, or Teams who want payments mirrored inside their CRM without manual work. Modification Notes / Extensions You can extend this workflow by: Adding Slack or Gmail notifications after deal creation. Logging every event in Google Sheets or Notion for audit. Enriching the customer using OpenAI / CRM data. Handling refunds, subscription cancellations, etc.

This workflow fetches NASA’s Astronomical Picture of the Day (APOD), prepares a caption combining the title and explanation, publishes the image to Instagram and sends you a Telegram notification with the result. It runs on a schedule so you can share inspiring space images without manual effort. Who is it for? Designed for science communicators, educators, astronomy fans and social media managers who want to share the APOD each day without searching for content. It’s also helpful for anyone looking to automate daily posts while receiving clear success or failure notifications. How it works A Schedule Trigger fires every day at 18:00 (adjustable) to start the workflow. The Get APOD HTTP request node calls https://api.nasa.gov/planetary/apod using your NASA API key and retrieves the image URL, title and explanation. The Prepare Caption node builds a caption by concatenating the title and explanation, and extracts the image URL. Prepare IG Post node sends a POST request to https://graph.facebook.com/v23.0/{YOUR_APP_ID}/media with the image URL and caption to create a media container on Instagram. A Wait node pauses the workflow while Instagram processes the media. The Get Status for Publish request checks the status of the media; the If node proceeds only when the status_code equals FINISHED. When ready, the Publish Post node calls to https://graph.facebook.com/v23.0/{YOUR_APP_ID}/media_publish endpoint with the creation_id to publish the photo on Instagram. On success, a Telegram node sends a message such as “PUBLISH STATUS: FINISHED” to your chat; on failure, another Telegram node notifies you that the upload failed and the workflow stops with an error. Setup steps ++Node Get APOD:++ Configure Query Auth with your own Nasa credential. ++Node: Prepare IG Post:++ Create a Facebook app and generate an access token with instagram_basic and pages_manage_posts permissions; Configure the url with you ID from you Meta Graph {YOUR_APP_ID}. Configure Facebook Graph API Credential Type with your token, you can generate in your API Graph Explorer ++Node Get Status For Publish:++ Configure your Facebook Graph API token like before. ++Node Publish Post:++ Configure your Facebook Graph API token like before and configure the url with you ID from you Meta Graph {YOUR_APP_ID}. ++Node Send Finish Message:++ Configure your token from Telegram API and your Telegram Chat ID {YOUR_CHAT_ID}. ++Node Send Fail Message:++ Configure your token from Telegram API and your Telegram Chat ID {YOUR_CHAT_ID}. Test the workflow to ensure the image posts correctly and that the Telegram notifications reflect the status. Requirements · NASA APOD API key from api.nasa.gov. · Instagram account linked to a Facebook page and a valid Facebook Graph API token with the appropriate permissions. · Telegram bot token and chat ID. How to customise it You can change the posting time or frequency, edit the caption template to include hashtags or links, or send success/failure notifications via email or Slack instead of Telegram. You might also save the images to cloud storage or cross‑post to other platforms, and adjust the error handling logic based on your needs.

How it works • Upload foreground video (AI actors, product demos, webcam footage) • Provide custom background video URL • API removes video background with videobgremover.com • Composites foreground onto background • Downloads and uploads to Google Drive • Returns shareable link Set up steps • Get API key at https://videobgremover.com/n8n (2 min) • Import workflow (1 min) • Add API key to n8n variables as VIDEOBGREMOVER_KEY (1 min) • Connect Google Drive (2 min) • Test with manual trigger (1 min) • Total: 7 minutes What you'll need • VideoBGRemover API key ($0.50-$2.00 per minute) • Google Drive account • Publicly accessible video URLs • n8n instance Perfect for • AI UGC ad creators using HeyGen, Synthesia, Arcads • Marketing agencies creating ad variations • E-commerce product demos on custom backgrounds • Social media content with branded scenes • Video editors removing backgrounds at scale Key features • Video composition with custom templates • Audio mixing with adjustable volumes • 20-second polling for status • Google Drive integration • Webhook automation support • 3-5 minute processing time per minutes of input video

🚀 Try It Out! YouTube Transcript API Extractor (Any Public Video) Extracts a clean transcript from a videoId using youtube-transcript.io. 🎯 Use Cases AI summaries, sentiment analysis, keyword extraction Internal indexing/SEO Content pipelines (blog/newsletter) Batch transcript processing 🔄 How It Works (5 Steps) 📥 Input: youtubeVideoId, apiToken 🌐 API: POST to youtube-transcript.io 🧩 Parse: Normalizes the response format 🧹 Clean: Normalizes text and whitespace ✅ Output: Transcript + metrics (wordCount/charCount) 🚀 How to Use Payload: {"youtubeVideoId":"xObjAdhDxBE", "apiToken": "xxxxxxxxxx"} ⚙️ Setup: This sub-workflow is intended to be called from another workflow (Execute Workflow Trigger)

Automatically create Intercom conversations with full technical context when your team receive new Marker.io issues 🎯 What this template does This workflow creates a seamless bridge between Marker.io and Intercom, your customer support platform. Every issue submitted through Marker.io's widget automatically becomes a trackable conversation in Intercom, complete with technical details and visual context. Centralizing customers issues in Intercom helps your support agents continue the conversation right where they work every day. When a bug is reported, the workflow: Creates or updates the reporter as an Intercom contact Opens a new conversation with the reporter and the all issue details Adds a comprehensive internal note with technical metadata Preserves all screenshots, browser info, and custom data ✨ Benefits Zero manual entry** - All bug details transfer automatically Instant visibility** - Support agents sees issues immediately Rich context** - Technical details preserved for developers Better collaboration** - Single source of truth for bugs Faster resolution** - No time wasted gathering information 💡 Use Cases Product Teams**: Streamline bug triage without switching tools Support Teams**: Get technical context for customer-reported issues Development Teams**: Access browser info, console logs and network logs directly from the support tickets 🔧 How it works n8n Webhook receives Marker.io bug report data Format and extract relevant information from the payload Create/update contact in Intercom with reporter details Start conversation with the Title and Bug description Add internal note with full technical context and Marker.io links for the support agent The result is a perfectly organized support ticket that your team can act on immediately, with all the context they need to reproduce and resolve the issue. 📋 Prerequisites Marker.io account** with webhook capabilities Intercom account** with API access Intercom Access Token** with appropriate permissions Admin ID** from your Intercom workspace 🚀 Setup Instructions Import this workflow into your n8n instance Configure the Webhook: Copy the test/production webhook URL after saving Add to Marker.io: Workspace Settings → Webhooks → Create webhook Select "Issue Created" as the trigger event Set up Intercom credentials: Create an Intercom app or use existing API credentials from the Intercom Develper Hub Add credentials to both HTTP Request nodes Update the admin_id in the "Add Internal Note" node with the id of one of your intercom admin Test the integration: Create a test issue in Marker.io Verify the conversation appears in Intercom Check that all data transfers correctly 📊 Data Captured Customer-facing message includes: Issue title Description Internal note includes: 🆔 Marker ID 📊 Priority level and issue type 📅 Due date (if set) 🖥️ Browser and OS details 🤓 Develper Console & Network logs 🌐 Website URL where issue occurred 🔗 Direct link to Marker.io issue 📷 Screenshot of the issue 📦 Any custom data fields → Read more about our webhook events

How this works: This workflow contains a webhook that receives updates from Reply.io when one of your connections sends you a message via either Email or LinkedIn. The workflow also includes utility nodes to create the necessary webhook subscriptions. Setup steps: Configure the body of the utility nodes to create subscriptions for the correct URL — retrieve it from the "Webhook" node in the workflow (use the production URL) Obtain your Reply.io API key. Documentation: https://apidocs.reply.io/ Create a Telegram bot Set your Reply.io API key in the HTTP nodes using Header Authentication Enter your Telegram credentials in the Telegram node Activate the workflow

How it works Start every morning on a positive note! This workflow automates delivering a curated summary of positive news directly to your mailbox. It automatically: Fetches the latest articles from a dedicated "good news" source (like Good News Network) every morning. Uses Artificial Intelligence to summarize each positive article concisely. Compiles these summaries into a clear and uplifting daily digest. Sends the daily digest to your specified email address. Say goodbye to doomscrolling and hello to your dose of daily inspiration! Set up steps Setting up this workflow is straightforward, typically taking around 10-15 minutes. You'll need to: Authenticate your preferred email service (e.g., Gmail). Obtain an API key for your chosen AI service (e.g., OpenAI). All detailed setup instructions and specific configuration guidance are provided within the workflow itself using sticky notes.

Automatically create Zendesk tickets with full technical context when your team receives new Marker.io issues 🎯 What this template does This workflow creates a seamless bridge between Marker.io and Zendesk, your customer support platform. Every issue submitted through Marker.io's widget automatically becomes a trackable ticket in Zendesk, complete with technical details and visual context. Centralizing customer issues in Zendesk helps your support agents continue the conversation right where they work every day. When an issue is reported, the workflow: Creates or updates the reporter as a Zendesk user Opens a new ticket with all issue details Adds a comprehensive internal comment with technical metadata Preserves all screenshots, browser info, and custom data Automatically tags tickets for easy filtering ✨ Benefits Zero manual entry** - All bug details transfer automatically Instant visibility** - Support agents see issues immediately Rich context** - Technical details preserved for developers Better collaboration** - Single source of truth for bugs Faster resolution** - No time wasted gathering information Smart organization** - Auto-tagging for efficient triage 💡 Use Cases Product Teams**: Streamline bug triage without switching tools Support Teams**: Get technical context for customer-reported issues Development Teams**: Access browser info, console logs, and network logs directly from support tickets 🔧 How it works n8n Webhook receives Marker.io issue data Format and extract relevant information from the payload Create/update user in Zendesk with reporter details Create ticket with the title and issue description Add internal comment with screenshot, full technical context and Marker.io links for the support agent The result is a perfectly organized support ticket that your team can act on immediately, with all the context they need to reproduce and resolve the issue. 📋 Prerequisites Marker.io account** with webhook capabilities Zendesk account** with API access Zendesk API token** with appropriate permissions 🚀 Setup Instructions Import this workflow into your n8n instance Configure the Webhook: Copy the test/production webhook URL after saving Add to Marker.io: Workspace Settings → Webhooks → Create webhook Select "Issue Created" as the trigger event Set up Zendesk credentials: Generate an API token from Zendesk Admin Center → Apps and integrations → APIs → Zendesk API Add credentials to all three HTTP Request nodes Update your subdomain in the URLs (replace [REPLACE_SUBDOMAIN] with your subdomain) Customize fields (optional): Update the custom field ID in "Create Ticket" node if you want to store Marker ID Modify tags to match your workflow Adjust priority mapping if needed Test the integration: Create a test issue in Marker.io Verify the ticket appears in Zendesk Check that all data transfers correctly 📊 Data Captured Customer-facing ticket includes: Issue title (as subject) Description (as ticket body) Internal comment includes: 🆔 Marker ID 📊 Priority level and issue type 📅 Due date (if set) 🖥️ Browser and OS details 🤓 Developer console & network logs 🌐 Website URL where issue occurred 🔗 Direct link to Marker.io issue 📦 Any custom data fields → Read more about Marker.io webhook events