by PDF Vector
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.)
by Paul Roussel
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
by Marker.io
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
by Marker.io
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
by Panth1823
Daily n8n Workflow Backup Automatically backs up all workflows to Google Drive daily. How it works Triggers daily at 11 PM (or manually on demand) Creates a timestamped backup folder in Google Drive Fetches all workflows from your n8n instance Converts each workflow to a JSON file Uploads files to the backup folder Automatically deletes old backup folders to save storage Setup steps Ensure your n8n instance has API access enabled Connect your Google Drive account (OAuth2) Create a Google Drive folder for backups and copy its Folder ID Important: Open the 'Cleanup Old Backups' node and paste that Folder ID into the code
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,