Workflow Templates

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 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

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

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.)

Community Node Disclaimer: This workflow uses KlickTipp community nodes. How It Works Automate transactional emails from KlickTipp to Gmail This workflow receives contact data from a KlickTipp Outbound rule, generates a personalized HTML email, and sends it via Gmail. Key fields (e.g., first name, company, website, phone, or other custom fields) are 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. Gmail Delivery Sends via Gmail (OAuth) with From/Reply-To, Subject, and HTML body. Supports CC/BCC and attachments if needed. 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. Create/authorize a Gmail credential (OAuth) and select it in the Send an 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 Gmail: Deliver the message with the Gmail 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 Gmail 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.

Tagged with: , , , ,

Tagged with: , , , ,

Tagged with: , , , ,

Tagged with: Tech demo, Bitrix24, Chatbot

Tagged with: , , , ,

Tagged with: , , , ,

Tagged with: , , , ,