Workflow Templates

Sync Dartagnan Email Templates to Braze Why Use This Workflow Email marketing demands consistency across platforms. This workflow automatically synchronizes your email templates from Dartagnan to Braze, eliminating manual transfers and ensuring brand consistency. Perfect for marketing teams who need to maintain a unified email experience while leveraging the strengths of both platforms. Business Benefits Save Time**: Eliminate hours of manual template copying and formatting between platforms Maintain Consistency**: Ensure your email templates look identical across Dartagnan and Braze Reduce Errors**: Automated synchronization prevents human error in template transfers Streamline Workflows**: Create once in Dartagnan, use everywhere through Braze's distribution power Preserve Image Assets**: Keep images hosted on Dartagnan while properly formatting them for Braze How It Works This workflow performs a bi-directional sync between your Dartagnan email templates and Braze platform. It intelligently handles: Template Updates: Automatically updates existing templates in Braze when modified in Dartagnan New Template Creation: Creates new templates in Braze when added to Dartagnan Image URL Transformation: Properly embeds and formats image URLs to meet Braze requirements while keeping assets on Dartagnan infrastructure Technical Implementation The workflow uses a scheduled trigger to check for template changes and then processes them in batches: Authentication: Securely connects to both Dartagnan and Braze APIs Template Retrieval: Fetches current templates from Dartagnan Comparison Logic: Determines which templates need updating or creation in Braze Content Transformation: Processes HTML content and image URLs to ensure compatibility API Integration: Pushes changes to Braze through their Content Blocks API Customization Options This workflow can be customized to meet your specific needs: Sync Frequency**: Adjust the schedule to run hourly, daily, or on any custom schedule Template Filtering**: Add conditions to sync only specific templates based on tags or categories Error Handling**: Configure notification emails when synchronization issues occur Logging**: Enable detailed logs for troubleshooting and auditing Setup Requirements Setting up this workflow takes approximately 20-30 minutes and requires: Dartagnan Requirements API Client ID API Client Secret Template access permissions Braze Requirements Braze Instance URL API Key with content block permissions Appropriate rate limits configured Common Use Cases Email Campaign Coordination**: Maintain consistent templates across platforms for multi-channel campaigns Agency Work**: Design in Dartagnan, deploy through client's Braze instance Rebranding Projects**: Update templates once and propagate changes automatically International Marketing**: Maintain language variants across platforms with automatic synchronization Get Started Once installed, configure your API credentials, set your desired synchronization schedule, and let the workflow handle the rest. The initial sync will create all your templates in Braze, with subsequent runs only updating what's changed.

Startup Funding Research Automation with Claude, Perplexity AI, and Airtable How it works This intelligent workflow automatically discovers and analyzes recently funded startups by: Monitoring multiple news sources (TechCrunch and VentureBeat) for funding announcements Using AI to extract key funding details (company name, amount raised, investors) Conducting automated deep research on each company through perplexity deep research or jina deep search. Organizing all findings into a structured Airtable database for easy access and analysis Set up steps (10-15 minutes) Connect your news feed sources (TechCrunch and VentureBeat). Could be extended. These were easy to scrape and this data can be expensive. Set up your AI service credentials (Claude and Perplexity or jina which has generous free tier) Connect your Airtable account and create a base with appropriate fields (can be imported from my base) or see structure below. Airtable Base Structure Funding Round Base | Field Name | Data Type | Description | |------------|-----------|-------------| | website_url | String | URL of the company website | | company_name | String | Name of the company | | funding_round | String | The funding stage or round (e.g., Series A, Seed, etc.) | | funding_amount | Number | The amount of funding received | | lead_investor | String | The primary investor leading the funding round | | market | String | The market or industry sector the company operates in | | participating_investors | String | List of other investors participating in the funding round | | press_release_url | String | URL to the press release about the funding | | evaluation | Number | The company's valuation | Structure Company Deep Research Base | Field Name | Data Type | Description | |------------|-----------|-------------| | website_url | String | URL of the company website | | company_name | String | Name of the company | | funding_round | String | The funding stage or round (e.g., Series A, Seed, etc.) | | funding_amount | Number | The amount of funding received | | currency | String | Currency of the funding amount | | announcement_date | String | Date when the funding was announced | | lead_investor | String | The primary investor leading the funding round | | participating_investors | String | List of other investors participating in the funding round | | industry | String | The industry sectors the company operates in | | company_description | String | Description of the company's business | | hq_location | String | Company headquarters location | | founding_year | Number | Year the company was founded | | founder_names | String | Names of the company founders | | ceo_name | String | Name of the company CEO | | employee_count | Number | Number of employees at the company | | total_funding | Number | Total funding amount received to date | | total_funding_currency | String | Currency of total funding | | funding_purpose | String | Purpose or use of the funding | | business_model | String | Company's business model | | valuation | Object | Company valuation information | | previous_rounds | Object | Information about previous funding rounds | | source_urls | String | Source URLs for the funding information | | original_report | String | Original report text about the funding | | market | String | The market the company operates in | | press_release_url | String | URL to the press release about the funding | | evaluation | Number | The company's valuation | Notes I found that by using perplexity via open router, we lose access to the sources, as they are not stored in the same location as the report itself so I opted to use perplexity API via HTTP node. For using perplexity and or jina you have to configure header auth as described in Header Auth - n8n Docs What you can learn How to scrape data using sitemaps How to extract strucutred data from unstructured text How to execute parts of the workflow as subworkflow How to use deep research in a practical scenario How to define more complex JSON schemas

This workflow template, "n8n Error Report to LINE," is designed to streamline error handling by sending real-time notifications to your LINE account whenever an error occurs in any of your n8n workflows. By integrating with the LINE Messaging API , this template ensures you stay informed about workflow failures, allowing you to take immediate action and minimize downtime. Whether you're a developer managing multiple workflows or a business owner relying on automation, this template provides a simple yet powerful way to monitor and resolve errors efficiently. Who Is This Template For? Developers: Who manage complex n8n workflows and need real-time error notifications. DevOps Teams: Looking to enhance monitoring and incident response for automated systems. Business Owners: Who rely on n8n workflows for critical operations and want to ensure reliability. Automation Enthusiasts: Seeking tools to simplify error tracking and improve workflow performance. What Problem Does This Workflow Solve? When automating processes with n8n, errors can occur due to various reasons such as misconfigurations, API changes, or unexpected inputs. Without proper error handling, these issues may go unnoticed, leading to delays or disruptions. This workflow solves that problem by: 1) Automatically detecting errors in your n8n workflows. 2) Sending instant notifications to your LINE account with details about the failed workflow, including its name and execution URL. Allowing you to quickly identify and resolve issues, ensuring smooth operation of your automated systems. What This Workflow Does 1) Error Trigger: The workflow is triggered automatically whenever an error occurs in any n8n workflow configured to use this error-handling flow. 2) Send Notification via LINE: Using the LINE Push API , the workflow sends a message to your LINE account with key details about the error, such as the workflow name and execution URL. You can also customize the notification message to include additional information or format it to suit your preferences. Setup Guide Pre-Requisites Access to the LINE Developers Console with a registered bot and access to the Push API. https://developers.line.biz/console/ [API Reference]( https://developers.line.biz/en/reference/messaging-api/#send-narrowcast-message) Basic knowledge of n8n workflows and JSON formatting. An active n8n instance where you can configure error workflows. Step-by-Step Setup Configure the Error Trigger: Set this workflow as the default error workflow in your n8n instance. https://docs.n8n.io/flow-logic/error-handling/ Set Up LINE Push API: Replace <UID HERE> in the HTTP Request node with your LINE user ID to ensure notifications are sent to the correct account.

Setting up n8n workflow Overview The Docker Immich WHMCS module uses a specially designed workflow for n8n to automate deployment processes. The workflow provides an API interface for the module, receives specific commands, and connects via SSH to a server with Docker installed to perform predefined actions. Prerequisites You must have your own n8n server. Alternatively, you can use the official n8n cloud installations available at: n8n Official Site Installation Steps Install the Required Workflow on n8n You have two options: Option 1: Use the Latest Version from the n8n Marketplace The latest workflow templates for our modules are available on the official n8n marketplace. Visit our profile to access all available templates: PUQcloud on n8n Option 2: Manual Installation Each module version comes with a workflow template file. You need to manually import this template into your n8n server. n8n Workflow API Backend Setup for WHMCS/WISECP Configure API Webhook and SSH Access Create a Basic Auth Credential for the Webhook API Block in n8n. Create an SSH Credential for accessing a server with Docker installed. Modify Template Parameters In the Parameters block of the template, update the following settings: server_domain – Must match the domain of the WHMCS/WISECP Docker server. clients_dir – Directory where user data related to Docker and disks will be stored. mount_dir – Default mount point for the container disk (recommended not to change). Do not modify the following technical parameters: screen_left screen_right Deploy-docker-compose In the Deploy-docker-compose element, you have the ability to modify the Docker Compose configuration, which will be generated in the following scenarios: When the service is created When the service is unlocked When the service is updated nginx In the nginx element, you can modify the configuration parameters of the web interface proxy server. The main section allows you to add custom parameters to the server block in the proxy server configuration file. The main\_location section contains settings that will be added to the location / block of the proxy server configuration. Here, you can define custom headers and other parameters specific to the root location. Bash Scripts Management of Docker containers and all related procedures on the server is carried out by executing Bash scripts generated in n8n. These scripts return either a JSON response or a string. All scripts are located in elements directly connected to the SSH element. You have full control over any script and can modify or execute it as needed.

🎥 Analyze YouTube Video for Summaries, Transcripts & Content + Google Gemini Who is this for? This workflow is ideal for content creators, video marketers, and research professionals who need to extract actionable insights, detailed transcripts, or metadata from YouTube videos efficiently. It is particularly useful for those leveraging AI tools to analyze video content and optimize audience engagement. What problem does this workflow solve? / Use case Analyzing video content manually can be time-consuming and prone to errors. This workflow automates the process by extracting key metadata, generating summaries, and providing structured transcripts tailored to specific use cases. It helps users save time and ensures accurate data extraction for content optimization. What this workflow does Extracts audience-specific metadata (e.g., video type, tone, key topics, engagement drivers). Generates customized outputs based on six prompt types: Default: Actionable insights and strategies. Transcribe: Verbatim transcription. Timestamps: Timestamped dialogue. Summary: Concise bullet-point summary. Scene: Visual descriptions of settings and techniques. Clips: High-engagement video segments with timestamps. Saves extracted data as a text file in Google Drive. Sends analyzed outputs via Gmail or provides them in a completion form. Setup Configure API keys: Add your Google API key as an environment variable. Input requirements: Provide the YouTube video ID (e.g., wBuULAoJxok). Select a prompt type from the dropdown menu. Connect credentials: Set up Google Drive and Gmail integrations in n8n. How to customize this workflow to your needs Modify the metadata prompt to extract additional fields relevant to your use case. Adjust the output format for summaries or transcripts based on your preferences (e.g., structured bullets or plain text). Add nodes to integrate with other platforms like Slack or Notion for further collaboration. Example Usage Input: YouTube video ID (wBuULAoJxok) and prompt type (summary). Output: A concise summary highlighting actionable insights, tools, and resources mentioned in the video.

🎨 AI Graphic Design Team - Generate and Review AI Images with Ideogram and OpenAI Description Who is this for? This workflow is perfect for graphic designers, creative agencies, marketing teams, or freelancers who regularly use AI-generated images in their projects. It's specifically beneficial for teams that want to automate the generation, review, and management of AI-created graphics efficiently. What problem does this workflow solve? Design teams often face time-consuming manual reviews and inconsistent quality checks for AI-generated images. This workflow addresses these challenges by automating image generation and introducing a systematic, AI-driven vetting process. This ensures only high-quality, relevant images reach your team's assets, saving valuable time and enhancing workflow efficiency. What this workflow does AI Image Generation:** Integrates Ideogram via HTTP Request to automatically create AI-generated images based on creative briefs. Automated Image Review:** Uses OpenAI to automatically evaluate and approve images, ensuring they meet your predefined quality standards. Efficient Asset Management:** Automatically creates structured Google Drive folders and compiles key metadata (including creation dates, prompts, and image links) into a CSV file and Google Sheet. Immediate Email Notifications:** Delivers a setup confirmation and provides easy access to Google Drive folders and assets via automated email notifications. Final Approved Images:** Outputs vetted, ready-to-use images for your creative projects, removing the burden of manual reviews. Setup Initial Email Configuration Update your email details in both the "Setup Gmail" node and the "Gmail" notification node. Run the initial setup workflow to automatically create the Google Drive folders "Graphic_Design_Team" and "Image_Generations," and upload your CSV file (n8n-Graphic_Design_Team.csv). Review Email & Set Up Google Sheets Check your inbox for an automated email containing folder IDs and direct links. Create and set up a Google Sheet by importing the provided CSV data from your email. Update Workflow Nodes Select your newly created Google Sheet in both Google Sheets nodes. Update your Creative Brief node with the Google Drive folder IDs provided in the email. Run Workflow for AI Image Generation & Review Execute the workflow. Your generated images will be automatically vetted, organized, and ready for creative use. How to Customize This Workflow Tailor Image Generation Prompts:** Adjust prompts and settings in the Ideogram HTTP Request node to better fit your project's creative requirements. Set Quality Standards:** Modify the criteria used by the OpenAI node to reflect your specific standards and preferences for image approval. Customize Asset Organization:** Adapt Google Drive folder structures, CSV headers, or Google Sheets integrations to match your team's organizational preferences. Dependencies & Requirements Nodes Used:** HTTP Request (Ideogram API integration) OpenAI (Image review and quality assessment) Gmail (Automated notifications) Google Drive (File and asset management) Google Sheets (Metadata organization) Credentials:** Ensure Gmail, Google Drive, Google Sheets, and OpenAI credentials are properly configured in your n8n account. No custom or community nodes are needed. Final Outcome Upon completion, your workflow efficiently provides vetted, high-quality AI-generated images, organized in Google Drive and accessible via easy-to-use metadata in Google Sheets, drastically reducing manual intervention and accelerating your creative processes.

✨ Overview This workflow allows candidates to schedule interviews through a conversational AI assistant. It integrates with your Google Calendar to check for existing events and generates a list of available 30-minute weekday slots between 9 AM and 5 PM Eastern Time. Once the candidate selects a suitable time and provides their contact information, the AI bot automatically books the meeting on your calendar and confirms the appointment. ⚡ Prerequisites To use this workflow, you need an OpenAI account with access to the GPT-4o model, a Google account with a calendar that can be accessed through the Google Calendar API, and an active instance of n8n—either self-hosted or via n8n cloud. Within n8n, you must have two credential configurations ready: one for Google Calendar using OAuth2 authentication, and another for your OpenAI API key. 🔐 API Credentials Setup For Google Calendar, go to the Google Cloud Console and create a new project. Enable the Google Calendar API, then create OAuth2 credentials by selecting “Web Application” as the application type. Add http://localhost:5678/rest/oauth2-credential/callback as the redirect URI if using local n8n. After that, go to n8n, navigate to the Credentials section, and create a new Google Calendar OAuth2 credential using your account. For OpenAI, visit platform.openai.com to retrieve your API key. Then go to the n8n Credentials page, create a new credential for OpenAI, paste your key, and name it for reference. 🔧 How to Make This Workflow Yours To customize the workflow for your use, start by replacing all instances of the calendar email rbreen.ynteractive@gmail.com with your own Google Calendar email. This email is referenced in multiple places, including Google Calendar nodes and the ToolWorkflow JSON for the node named "Run Get Availability." Also update any instances where the Google Calendar credential is labeled as Google Calendar account to match your own credential name within n8n. Do the same for the OpenAI credential label, replacing OpenAi account with the name of your own credential. Next, go to the node labeled Candidate Chat and copy the webhook URL. This is the public chat interface where candidates will engage with the bot—share this URL with them through email, your website, or anywhere you want to allow access. Optionally, you can also tweak the system message in the Interview Scheduler node to modify the tone, language, or logic used during conversations. If you want to add branding, update the title, subtitle, and inputPlaceholder in the Candidate Chat node, and consider modifying the final confirmation message in Final Response to User to reflect your brand voice. You can also update the business rules such as time zone, working hours, or default duration by editing the logic in the Generate 30 Minute Timeslots code node. 🧩 Workflow Explanation This workflow begins with the Candidate Chat node, which triggers when a user visits the public chat URL. The Interview Scheduler node acts as an AI agent, guiding the user through providing their email, phone number, and preferred interview time. It checks availability using the Run Get Availability tool, which in turn reads your calendar and compares it with generated free time slots from the Generate 30 Minute Timeslots node. The check day names tool helps the AI interpret natural language date expressions like “next Tuesday.” The schedule is only populated with 30-minute weekday slots from 9 AM to 5 PM Eastern Time, and no events are scheduled if they overlap with existing ones. When a suitable time is confirmed, the AI formats the result into structured JSON, creates an event on your Google Calendar, and sends a confirmation back to the user with all relevant meeting details. 🚀 Deployment Steps To deploy the interview scheduler, import the provided workflow JSON into your n8n instance. Update the Google Calendar email, OpenAI and Google credential labels, system prompts, and branding as needed. Test the connections to ensure the API credentials are working correctly. Once everything is configured, copy and share the public chat URL from the Candidate Chat node. When candidates engage with the chat, the workflow will walk them through the interview booking process, check your availability, and finalize the booking automatically. 💡 Additional Tips By default, the workflow avoids scheduling interviews on weekends and outside of 9–5 EST. Each interview lasts exactly 30 minutes, and overlapping with existing events is prevented. The assistant does not reveal details about other meetings. You can customize every part of this workflow to fit your use case, including subworkflows like Get Availability and check day names, or even white-label it for client use. This workflow is ready to become your AI-powered interview scheduling assistant. 🤝 Connect with Me Description I’m Robert Breen, founder of Ynteractive — a consulting firm that helps businesses automate operations using n8n, AI agents, and custom workflows. I’ve helped clients build everything from intelligent chatbots to complex sales automations, and I’m always excited to collaborate or support new projects. If you found this workflow helpful or want to talk through an idea, I’d love to hear from you. Links 🌐 Website: https://www.ynteractive.com 📺 YouTube: @ynteractivetraining 💼 LinkedIn: https://www.linkedin.com/in/robert-breen 📬 Email: rbreen@ynteractive.com

⚠️ DISCLAIMER: This workflow uses the HDW LinkedIn community node, which is only available on self-hosted n8n instances. It will not work on n8n.cloud. Overview This workflow automates the entire LinkedIn lead generation process from finding prospects that match your Ideal Customer Profile (ICP) to sending personalized messages. It uses AI to analyze lead data, score potential clients, and prioritize your outreach efforts. Key Features AI-Driven Lead Generation**: Convert ICP descriptions into LinkedIn search parameters Comprehensive Data Enrichment**: Analyze company websites, LinkedIn posts, and news Intelligent Lead Scoring**: Prioritize leads based on AI analysis of intent signals Automated Outreach**: Connect with prospects and send personalized messages Requirements Self-hosted n8n instance with the HDW LinkedIn community node installed OpenAI API access (for GPT-4o) Google Sheets access HDW API key (available at app.horizondatawave.ai) LinkedIn account Setup Instructions 1. Install Required Nodes Ensure the HDW LinkedIn community node is installed on your n8n instance Command: npm install n8n-nodes-hdw (or use this instruction) 2. Configure Credentials OpenAI**: Add your OpenAI API key Google Sheets**: Set up Google account access HDW LinkedIn**: Configure your API key from horizondatawave.ai 3. Set Up Google Sheet Create a new Google Sheet with the following columns (or copy template): Name, URN, URL, Headline, Location, Current company, Industry, etc. The workflow will populate these columns automatically 4. Customize Your ICP Use chat to provide the AI Agent with your Ideal Customer Profile Example: "Target marketing directors at SaaS companies with 50-200 employees" 5. Adjust Scoring Criteria Modify the lead scoring prompt in the "Company Score Analysis" node to match your specific product/service Tune the evaluation criteria based on your unique business needs 6. Configure Message Templates Update the HDW LinkedIn Send Message node with your custom message How It Works ICP Translation: AI converts your ICP description into LinkedIn search parameters Lead Discovery: Workflow searches LinkedIn using these parameters Data Collection: Results are saved to Google Sheets Enrichment: System collects additional data about each lead: Company website analysis Lead's LinkedIn posts Company's LinkedIn posts Recent company news Intent Analysis: AI analyzes all data to identify buying signals Lead Scoring: Leads are scored on a 1-10 scale based on likelihood of interest Connection Requests: Top-scoring leads receive connection requests Follow-Up: When connections are accepted, automated messages are sent Customization Search Parameters**: Adjust the AI Agent prompt to refine your target audience Scoring Criteria**: Modify scoring prompts to highlight indicators relevant to your product Message Content**: Update message templates for personalized outreach Schedule**: Configure when connection requests and messages are sent Rate Limits & Best Practices LinkedIn has connection request limits (approximately 100-200 per week) The workflow includes safeguards to avoid exceeding these limits Consider spacing your outreach for better response rates Note: Always use automation tools responsibly and in accordance with LinkedIn's terms of service.

This n8n template builds a simple automation to ensure no JIRA issues go unassigned for more than a week to prevent them falling through the cracks. It uses AI to perform searching tasks against a Supabase Vector Store. This can be one way to help reduce the amount of manual work in managing the issue backlog for busy teams with little effort. How it works This template contains 2 separate flows which run continuously via schedule triggers. The first populates our Supabase vector store with resolved issues within the last day. This helps keep our vector store up-to-date and relevant for the purpose of finding similar issues. It does this by pulling the latest resolved issues from JIRA and populating the Supabase vectorstore with carefully chosen metadata. This will come in handy later. The second flow watches for stale, unassigned issues for the purpose of aut-assigning to a relevant team member. It does this by comparing the stale issue against our vector store of resolved issues with the goal of identifying which team member would have best context regarding the issue. In a busy team, this may net a few team members as possible candidates to assign. Therefore, we can introduce additional logic to count each team member's assigned, in-progress issues. This is intended to not overload our busiest members. The team member with the least assigned issues is pressumed to have the most capacity and therefore is assigned. A comennt is left in the issue to notify the team member that they've been auto-assigned due to age of issue. How to use Modify the project and interval parameters to match those of your use-case and team members. Add additional criteria before assigning to a team member eg. department, as required. Requirements OpenAI for LLM JIRA for Issue Management Supabase for Vector Store Customising this workflow Not using JIRA or Supabase? The beauty of these AI templates are these components are entirely interchangeable with competing services. Try Linear and Qdrant instead! Auto-assigning logic is simplified in this template. Expand criteria as required for your team and organisation. eg. Might be a good idea to pull in annual leave information from HR system to prevent assigning to someone who is on currently on holiday!

N8n recently introduced folders and it has been a big improvement on workflow management on top of the tags. This means the current workflows need to be moved manually to the folders. The simplest idea to try is to convert the current tags into folders and move all the current workflows within the respective tags into the folders This assumes the tag name will be used as the folder name. To Note For workflows that use more than 1 tag, the workflow will be assigned the last tag that runs as the folder. How does it work I took the liberty of simplifying the setup of this workflow that will be needed on your part and also be beginner-friendly Copy and paste this workflow into your n8n canvas. You must have existing workflows and tags before you can run this Set your n8n login details on the node set Credentials with the n8n URL, username, and password. Setup your n8n API credentials on the n8n node get workflows Run the workflow. This opens up a form where you can select the number of tags to move and click on submit The workflow responds with the successful number of workflows that were imported Read more about the template Built by Zacharia Kimotho - Imperol

This n8n template builds a newsletter ("daily digest") delivery service which pulls and summarises the latest n8n.io template in select categories defined by subscribers. It's scheduled to run once a day and sends the newsletter directly to subscriber via a nicely formatted email. If you've had trouble keeping up with the latest and greatest templates beign published daily, this workflow can save you a lot of time! How it works A scheduled trigger pulls a list of subscribers (email and category preferences) from an Excel workbook. We work out unique categories amongst all subscribers and only fetch the latest n8n website templates from these categories to save on resources and optimise the number of API calls we make. The fetched templates are summarised via AI to produce a short description which is more suitable for our email format. For each subscriber, we filter and collect only the templates relevant to their category preferences (as defined in the Excel) and ensure that duplicate templates or those which have been "seen before" are omitted. A HTML node is then used to generate the email newsletter. HTML emails are the perfect format since we can add links back to the template. Finally, we use the Outlook node to send the email digest to the subscriber. How to use Populate your Excel sheet with 3 columns: name, email and categories. Categories is a comma-delimited list of categories which match the n8n template website. The available categories are AI, SecOps, Sales, IT Ops, Marketing, Engineering, DevOps, Building Blocks, Design, Finance, HR, Other, Product and Support. To subscribe a new user, simply add their email to the Excel sheet with at least one category. To unsubscribe a user, remove them from the sheet. If you're not interested in paid templates, you may want to filter them out after fetching. Requirements Microsoft Excel for subscriber list Microsoft Outlook for delivering emails OpenAI for AI-generated descriptions Customising the workflow Use AI to summarise the week's trend of templates types and use-cases This template can be the basis for other similar newsletters - just pull in a list of things from anywhere!

This workflow template, "Personal Assistant to Note Messages and Extract Namecard Information" is designed to streamline the processing of incoming messages on the LINE messaging platform. It integrates with powerful tools like Microsoft Teams , Microsoft To Do , OneDrive , and OpenRouter.ai to handle tasks such as saving notes, extracting namecard information, and organizing images. Whether you’re managing personal productivity or automating workflows for teams, this template offers a versatile and customizable solution. By leveraging this workflow, you can automate repetitive tasks, improve collaboration, and enhance efficiency in handling LINE messages. Who Is This Template For? This template is ideal for: Professionals: Who want to save important messages, extract data from namecards, or organize images automatically. Teams: Looking to integrate LINE messages into tools like Microsoft Teams and Microsoft To Do for better collaboration. Developers: Seeking to build intelligent workflows that process text, images, and other inputs from LINE. Business Owners: Who need to manage customer interactions, follow-ups, and task tracking efficiently. What Problem Does This Workflow Solve? Managing incoming messages on LINE can be time-consuming, especially when dealing with diverse input types like text, images, and namecards. This workflow solves that problem by: Automatically identifying and routing different message types (text, images, namecards) to appropriate actions. Extracting structured data from namecards and saving it for follow-up tasks. Uploading images to OneDrive and saving text messages to Microsoft Teams or Microsoft To Do for easy access. Sending real-time feedback to users via LINE to confirm that their messages have been processed. What This Workflow Does Receive Messages via LINE Webhook: The workflow is triggered whenever a user sends a message (text, image, or other types) to the LINE bot. Display Loading Animation: A loading animation is displayed to reassure the user that their request is being processed. Route Input Types: The workflow uses a Switch node to determine the type of input: Text Starting with "T": Adds the message as a task in Microsoft To Do. Plain Text: Saves the message in Microsoft Teams under a designated channel (e.g., "Notes"). Images: Identifies whether the image is a namecard, handwritten note, or other content, then processes accordingly. Unsupported formats trigger a polite response indicating the limitation. Process Namecards: *Images * If the image is identified as a namecard, the workflow extracts structured data (e.g., name, email, phone number) using OpenRouter.ai and saves it to Microsoft To Do for follow-up tasks. Save Images to OneDrive: Images are uploaded to OneDrive, renamed based on their unique message ID, and linked in Microsoft Teams for reference. Send Feedback via LINE: The workflow replies to the user with confirmation messages, such as "[ Task Created ]" or "[ Message Saved ]." Setup Guide Pre-Requisites Access to the LINE Developers Console to configure your webhook and bot. Accounts for Microsoft Teams , Microsoft To Do, and OneDrive with API access. An OpenRouter.ai account with credentials to access models like GPT-4o. Basic knowledge of APIs, webhooks, and JSON formatting. Step-by-Step Setup 1) Configure the LINE Webhook: Go to the LINE Developers Console and set up a webhook to receive incoming messages. Copy the Webhook URL from the Line Webhook node and paste it into the LINE Console. Remove any "test" configurations when moving to production. 2) Set Up Microsoft Integrations: Connect your Microsoft Teams, Microsoft To Do, and OneDrive accounts to the respective nodes in the workflow. 3) Set Up OpenRouter.ai: Create an account on OpenRouter.ai and obtain your API credentials. Connect your credentials to the OpenRouter nodes in the workflow. Test the Workflow: Simulate sending text, images, and namecards to the LINE bot to verify that all actions are processed correctly. How to Customize This Workflow to Your Needs Add More Actions: Extend the workflow to handle additional input types or integrate with other tools. Enhance Image Processing: Use advanced OCR tools to improve text extraction from complex images. Customize Feedback Messages: Modify the reply format to include emojis, links, or other formatting options. Expand Use Cases: Adapt the workflow for specific industries, such as sales or customer support, by tailoring the actions to relevant tasks. Why Use This Template? Versatile Automation: Handles multiple input types (text, images, namecards) with ease. Seamless Integration: Connects LINE messages to popular productivity tools like Microsoft Teams and To Do. Structured Data Extraction: Extracts and organizes data from namecards, saving time and effort. Real-Time Feedback: Keeps users informed about the status of their requests with instant notifications.