by iamvaar
Workflow explaination: https://youtu.be/ecafBTFPuvE?si=7csA1yNsaUxUG72F This workflow is designed to automatically handle new freelance project requests from a JotForm, analyze the requirements using AI, create a custom proposal, log the details in a Google Sheet, and send a personalized response to the client. 1. JotForm Trigger Purpose**: This node is the entry point of the entire automation. It waits for a new freelance project submission from your specified JotForm. Action: When a potential client fills out and submits the form, this node **instantly triggers the workflow, passing all submitted data (name, email, project requirements, and budget) to the next node. Key Detail**: Uses a webhook for real-time activation, ensuring immediate processing of every new project request. 2. AI Agent Purpose**: The central brain of your freelance workflow. 🧠 It takes the project submission and turns it into a structured, customized proposal. Action**: The agent follows a prompt sequence to perform these tasks: Calls the My Freelance Document Tool: Fetches your Google Doc containing details about your services, pricing, and project templates — your “source of truth.” Analyzes the Project Request: Reads the client’s requirements and goals from the form. Generates a Custom Proposal: Based on scope, budget, and relevance to your offerings, it prepares a short, tailored proposal or quote that fits the project. Creates a Personalized Email: Builds an HTML email with the proposal embedded, including next steps or a scheduling link for further discussion. Outputs Structured Data: Packages everything (project summary, proposal text, email subject, and body) into a clean JSON object for downstream use. 3. Append or Update Row in Sheet (Google Sheets) Purpose**: Serves as your lightweight CRM for all project inquiries. Action**: Logs data from the AI Agent (proposal details, client info, and project summary) into a Google Sheet. Key Detail: Configured to **Append or Update—if an email already exists, it updates that row instead of duplicating. Keeps your client records clean and organized. 4. If Purpose**: Acts as a control node to decide whether a proposal email should be sent. Action**: Checks the output from the AI Agent to ensure the proposal text is valid (not empty). Key Detail**: If the proposal generation fails or returns “NAN,” the workflow stops here to avoid sending incomplete responses. 5. Send a Message (Gmail) Purpose**: Sends the final personalized proposal email to the client. Action: Pulls the recipient’s email from the sheet and sends the **AI-generated subject and HTML proposal email automatically. Key Detail**: The email is customized per project, giving the client an instant, professional response with no manual effort.
by Sheragim
This workflow automates the creation of a draft article for a blog Use Cases Rapidly generate blog content from simple prompts. Ensure content consistency and speed up time-to-publish. Automatically source and attach relevant featured images. Save your digital marketing team significant time. (Personalized touch based on your experience) Prerequisites/Requirements An OpenAI API Key (for GPT-4O). A Pixabay API Key (for image sourcing). A WordPress site URL and API credentials (username/password or application password). Customization Options Adjust the AI prompt in the AI Content Generation node to change the content tone and style. Modify the search query in the Pixabay Query HTTP node to influence the featured image selection. Change the reviewer email address in the final Send Review Notification node.
by Paul Abraham
This n8n template creates an intelligent AI-powered travel agent that can assist with travel planning and send email confirmations. The agent can extract user requests, plan travel itineraries by fetching real-time data on flights, accommodations, and activities, and then communicate this information by sending a customized email. Use Cases Quickly plan a trip by providing your destination and dates. Get real-time flight and accommodation details for a planned vacation. Receive a summary of your travel plans directly in your inbox. A personal travel planner available on-the-go. Good to Know This template uses Google Gemini for AI reasoning. The Planner Agent can break down complex travel requests and make multiple API calls to gather all the necessary information. The Email Agent crafts a professional and personalized email to send to the user. How it Works Incoming Message Trigger: The workflow begins when a new message is received from a user. Extract User Request: The user's message is sent to a Gemini Chat Model which identifies the user's intent and extracts key details like destination, dates, and interests. Planner Agent: The extracted information is passed to the Planner Agent. This agent, powered by Gemini, determines what information is needed and then calls a series of sub-agents to gather: Activities: Fetches information about local attractions and things to do. Flight Booking: Retrieves flight details and pricing. Accommodation Details: Looks for hotels, rentals, and other lodging options. Accommodations: Gathers general information about accommodations. Email Agent: Once the Planner Agent has collected all the necessary information, it’s handed over to the Email Agent. This agent uses a second Gemini Chat Model to format a clear and professional email containing the full travel itinerary. Send Message: The final email is sent to the user, providing a comprehensive travel plan. How to Use Clone this workflow into your n8n instance. Connect your accounts as required. You will need credentials for your email service and any APIs you want to use for fetching travel data (e.g., flight booking, accommodation, and activities). Modify the nodes with your specific credentials and API endpoints. Run the workflow and start receiving automated travel plans. Requirements Google Gemini account for AI reasoning. Email integration (e.g., Gmail, Outlook). Serp API keys for travel-related services (optional, depending on your setup). Customizing This Workflow Add more integrations (e.g., a hotel booking service like Booking.com, a restaurant reservation system) for extended functionality. Modify the AI prompts in the agent nodes to fine-tune the personality or focus of the travel agent. Connect the final output to a different messaging service like Telegram or Slack instead of email.
by Aryan Shinde
AI-Powered Gmail Auto-Labeler Automatically organize your Gmail inbox with seamless, dynamic AI classification! This workflow leverages Google Gemini’s latest model to continually sort new emails into your own custom Gmail labels—no manual intervention or tedious setup required. 🚀 What This Workflow Does Watches for Unread Emails:** Continuously polls your Gmail inbox for new unread emails (polling interval can be changed as needed). Fetches All Available Labels:** Dynamically syncs every custom & system label from your Gmail account—no hardcoded lists. AI-Based Classification:** Each new email’s subject and snippet/body are sent to the Gemini 2.5 Pro AI, which analyzes content and recommends the best matching label(s) from your own label list (not made up!). Accurate Label Application:** The workflow maps Gemini’s label name suggestions to the correct label IDs in Gmail and auto-applies one or more labels directly to each email. Self-Updating / No Maintenance:** If you add/change Gmail labels, the workflow always uses the current label list. You don’t need to update any configuration or nodes (completely dynamic). Supports Multiple Simultaneous Labels:** Gemini can assign several labels at once—perfect for nuanced sorting (ex: “Receipts”, “Work”, "Travel"). 🔧 How to Set Up Connect Credentials: Google Gmail account (OAuth2) Gemini API key (for Google Gemini) (Optional) Adjust Gmail Labels: Add, rename, or customize labels in Gmail to suit your sorting preferences. You can continue to modify these at any time! Activate the Workflow: Turn on the workflow. It starts processing new emails immediately. No need to edit code or update nodes when labels change. (Optional) Customize Filtering or Post-Processing: The default trigger checks for unread messages, but you can adjust this (e.g., all messages, specific senders, etc.). Add extra workflow steps as desired for downstream automation. 📝 Key Features & Best Practices Dynamic Label Handling:** Workflow always references your live Gmail label list—ensuring AI only selects valid, current labels. Never Misses a Label:** Gemini never invents new labels; only suggests exact matches from your actual account. Highly Customizable:** Enhance/chain further automations—trigger from read emails, exclude newsletters, forward labeled messages, etc. No Manual Updates:** Completely plug-and-play. Adding/changing labels in Gmail immediately reflects in workflow. Includes In-Workflow Notes:** Clear sticky notes and documentation embedded for reference and troubleshooting. 🕰 Example Use Cases Automated Inbox Zero – Instantly sort incoming emails into actionable folders. Smart Multi-Labeling – Financial emails get “Receipts”, “Accounting” and “Work”, all at once. Personal & Work Split – Classify emails into "Personal", "Clients", "Leads", etc. Travel, Projects, Subscriptions – Transform your Gmail into a fully organized hub. This workflow is perfect for anyone who wants Gmail organization powered by leading-edge AI, with absolutely minimal maintenance. Just connect accounts and activate — let Gemini do the sorting!
by Roshan Ramani
Smart Lead Qualification for JotForm Contact Forms Automatically classify and manage contact form submissions using AI-powered lead scoring. This workflow analyzes JotForm submissions in real-time, categorizes them as hot leads, cold leads, or spam, and takes intelligent actions—sending Telegram notifications for hot leads, ignoring irrelevant inquiries, and automatically deleting spam. Who's It For This template is perfect for: Businesses receiving high volumes of contact form submissions** who need to prioritize responses Marketing and sales teams** wanting to focus on qualified leads immediately Agencies and consultants** offering AI/automation services who want to filter out noise Anyone struggling with spam** or low-quality form submissions What It Does The workflow uses Google Gemini AI to intelligently classify each JotForm submission into three categories: Hot Lead (1)**: Genuine inquiries about your services, collaboration requests, or project proposals → Sends Telegram notification + Flags in JotForm Cold Lead (0)**: Legitimate but irrelevant inquiries (job applications, unrelated business queries) → No action taken Garbage/Spam (2)**: Test submissions, bots, gibberish, or fake data → Automatically deleted from JotForm How It Works JotForm trigger captures new contact form submissions Submission data is extracted and formatted Google Gemini AI analyzes the content and classifies the lead A switch routes the submission based on classification: Hot leads trigger Telegram notifications and get flagged Cold leads are ignored Spam submissions are automatically deleted Requirements n8n instance** (cloud or self-hosted) JotForm account** with a contact form (Get JotForm here) Google Gemini API key** (free tier available) Telegram account** for notifications How to Set Up 📋 Detailed setup instructions are included inside the workflow in sticky notes. Quick setup overview: Create your contact form in JotForm using the "Contact Form with Fancy Header and Footer" template Get your JotForm API key and form ID Obtain a Google Gemini API key from Google AI Studio Create a Telegram bot via @BotFather and get your chat ID Configure all credentials in the respective nodes Update the HTTP request nodes with your JotForm API key Test the workflow with sample submissions The workflow includes comprehensive sticky notes with step-by-step instructions, including how to get your Telegram chat ID and configure all integrations. How to Customize Adjust classification criteria**: Modify the AI Agent's system prompt to match your business type and lead qualification criteria Change notification format**: Edit the Telegram message template to include/exclude specific fields Add more actions**: Extend hot lead handling with additional nodes (e.g., add to CRM, send email, create task) Modify form fields**: Update field references if your JotForm uses different field names Multi-channel notifications**: Add Slack, Discord, or email notifications alongside Telegram Note All API keys and credentials shown in the workflow are placeholders. You'll need to replace them with your own credentials during setup.
by PollupAI
Who's it for This workflow is for Customer Success, Product, and Support teams who need to centralize and analyze unstructured customer feedback. It automates the process of identifying key themes from various communication channels, allowing you to proactively address issues, track feature requests, and understand the voice of the customer without manual effort. What it does This workflow uses a powerful chain of AI agents to process customer feedback from end to end. It begins by using a Data Agent to gather all recent customer interactions from multiple sources, including Gmail, Pipedrive, Zendesk, and Slack. Once the raw data is collected, a second AI Chain reads all the text and compresses it into concise, actionable "signals." A third AI Chain then takes these signals and intelligently clusters them into shared topics, assigning each a human-readable label like "Billing," "Performance," or "Feature Request." Finally, a fourth AI Agent acts as a dispatcher. It analyzes the clustered topics and follows a set of routing rules defined in its prompt to take the appropriate action. It uses its tools to automatically create a Zendesk ticket for product feedback, send a Slack message for billing issues, create a Notion page for training opportunities, or send a direct email alert for high-risk accounts. How to set up To get this workflow running, you will need to configure the credentials and parameters for the following nodes: Configure Credentials: Add your credentials for the Config: Set LLM for Agents node and all of the Tool nodes (Gmail, Pipedrive, Zendesk, Slack, and Notion). Set Initial Parameters: In the Set: Initial Parameters node, update the placeholder email address and the Slack channel name for billing alerts. Update Slack Search Channel: In the Tool: Search Slack Messages node, set the channel you want the agent to search for feedback in. Activate Workflow: Once configured, you can run the workflow manually to start the analysis. Requirements An account with an LLM provider, such as OpenAI. Accounts for the services you wish to connect (Gmail, Pipedrive, Zendesk, Slack, Notion). This workflow requires n8n's Langchain community nodes to be installed on your instance. How to customize the workflow This workflow's logic is primarily driven by AI prompts, making it highly customizable: AI Prompts:** Adjust the prompts in any of the AI Agent or AI Chain nodes to change the data gathering, analysis, clustering, or routing rules to fit your business needs. Data Sources:** Add, remove, or swap out the "Tool" nodes in the AI Agent: Gather Customer Feedback section to connect to different data sources like Intercom, Salesforce, or a database. Triggers:** Replace the Manual Trigger with a Schedule Trigger to run the analysis automatically on a daily or weekly basis.
by CustomJS
> ⚠️ Notice: > Community nodes like @custom-js/n8n-nodes-pdf-toolkit can only be installed on self-hosted instances of n8n. This n8n workflow demonstrates how to collect form submissions from a landing page, fill a PDF form automatically, and send it via email. It uses the PDF Form Fill node from customjs.space to populate PDF fields with the submitted data. What this workflow does Serves a landing page with a user-friendly form. Receives form submissions via a Webhook. Uses the HTTP Request node to fetch a PDF template. Fills the PDF form fields with the submitted data using the PDF Form Fill node. Optionally reads PDF form field names using Get PDF Form Fields. Sends the completed PDF as an email attachment. Requirements Self-hosted n8n instance. CustomJS API key for the PDF Toolkit nodes. SMTP account for sending emails. Optional: Access to the PDF template online. Workflow Steps Landingpage Endpoint (Webhook) Serves the landing page HTML to visitors. Set Form Endpoint Dynamically injects the endpoint URL into the HTML form. HTML for Landingpage Provides the form where users enter personal information (name, address, city, country, etc.). Respond to Webhook Returns the landing page HTML to the visitor. FormData Endpoint (Webhook) Receives the submitted form data as JSON. HTTP Request – Get PDF Template Fetches the PDF form template from a URL. PDF Form Fill (Fill PDF Fields) Populates the PDF with the submitted form data. Get PDF Form Fields (Optional) Reads and lists the names of the form fields in the PDF. Send Email Sends the completed PDF as an attachment to a configured recipient. Sticky Notes Provide documentation within the workflow for easier understanding and maintenance. Usage Get API key from CustomJS Sign up on the CustomJS platform. Navigate to your profile page and copy your API key. Set Credentials for CustomJS API in n8n Create a new credential in n8n with your API key. Prepare SMTP Credentials Add your SMTP server credentials to n8n for sending emails. Run or schedule the workflow The workflow will serve the landing page, fill the PDF form with submissions, and send it via email. Customization Tips Modify the landing page form** in the HTML node to add or remove fields. Change PDF template URL** in the HTTP Request node. Add more recipients** or dynamic email addresses in the Send Email node. Track submitted form data** in Google Sheets or a database for long-term storage. Extend workflow logic** with validation or notifications using additional nodes.
by WeWeb
This template gives you a complete, automated system for monitoring Reddit and extracting growth insights. It tracks discussions across target subreddits, surfaces what users love, dislike, want changed, and highlights how they compare you to competitors. Paired with the free WeWeb UI template, it prioritizes engagement and organizes everything into a clean, easy-to-use dashboard. So every team gets the insights they need: Leadership** gains clarity on industry trends and emerging shifts Product** can adjust roadmaps and prioritize features or integrations Marketing** gets content angles, competitive messaging, and SEO topics Sales** receives objection insights straight from real conversations Support** spots early patterns in user challenges 🙌 Who this is for Perfect for product teams, founders, and growth marketers who want to build and scale Reddit as a channel without spending hours manually scanning threads. 💫 What Makes This Different Eliminates manual scanning:** Automatically pull product and competitor mentions using F5Bot for free, without the high cost of traditional monitoring tools. Captures full conversations:** Track not just posts, but the entire comment chain where real insights, objections, and frustrations actually surface. AI-powered prioritization:** Every mention is classified by sentiment and topic so you know what to prioritize and why. Cross-team intelligence:** Highlights product insights, competitor signals, sales objections, user frustrations, and industry trends, helping product, marketing, sales, support, and leadership make more customer-centric decisions. ⚙️ How the Workflow Works A cron job runs every hour and scans your Gmail inbox for new F5Bot alert emails. When an alert is found, the workflow extracts all mention data from the email. An AI node processes each mention to: categorize it by topic tag sentiment All data is stored in Supabase. The data is displayed in a WeWeb dashboard where users can browse mentions. If a user wants deeper context, they click “AI Summary.” This triggers a webhook in n8n, which pulls the main Reddit post and its entire comment chain. The AI node summarizes the full thread and highlights: the core discussion competitor comparisons what users like or dislike industry-level signals The workflow returns a clean, actionable summary back to the WeWeb UI. 🧪 Requirements You don’t need any heavy infrastructure. To get started, you’ll need: F5Bot account (free)** - to track Reddit mentions by keywords and trigger email alerts Gmail integration** - so the workflow can parse emails from F5Bot OpenAI API key** - for AI-powered categorization and summarization Supabase project (free)** - to store all mention data WeWeb account (free)** - connects your n8n workflow to a clean, user-friendly dashboard for viewing insights Here's a detailed setup guide. 🔧 Want to Go Further? This setup is beginner-friendly, but you can extend it with: Blog topic generation Full blog post generation Social media posts Competitor benchmarking reports Weekly or monthly email digests Slack alerts for high-signal mentions
by Oneclick AI Squad
Description Automates monitoring of error logs and notifies developers of critical errors. Sends Slack alerts for critical and non-critical errors, with auto-creation of Jira tickets for critical issues. Essential Information Triggers manually or on a scheduled basis (e.g., every 5 minutes). Reads and parses server logs to detect errors. Alerts developers via Slack and creates Jira tickets for critical errors. System Architecture Error Detection Pipeline**: Manual Trigger: Initiates the workflow manually. Schedule Every 5min: Schedules automatic runs every 5 minutes. Set Config: Configures basic parameters for log reading. Read Error Logs: Executes SSH command to fetch server logs. Wait For All Logs: Ensures all logs are read. Error Processing Flow**: Parse Logs: Parses logs and categorizes critical vs. non-critical errors. IF Critical Error: Filters for critical errors. Alert and Ticket Creation**: Send Slack Alert: Sends detailed alerts for critical errors via Slack. Create Jira Ticket: Creates a Jira ticket for critical errors. Send Non-Critical Alert: Sends simple alerts for non-critical errors via Slack. Implementation Guide Import the workflow JSON into n8n. Configure SSH credentials for log access. Set up Slack and Jira integrations with appropriate credentials. Test with a manual trigger and sample log data. Adjust the schedule (e.g., every 5min) and error parsing rules as needed. Monitor alert accuracy and ticket creation. Technical Dependencies SSH access for reading server logs. Slack API for team notifications. Jira API for bug ticket creation. n8n for workflow automation and scheduling. Customization Possibilities Adjust the Cron schedule for different intervals (e.g., every 10min). Modify Parse Logs node to refine error categorization rules. Customize Slack alert messages in Send Slack Alert and Send Non-Critical Alert nodes. Enhance Jira ticket details in Create Jira Ticket node (e.g., add priority). Add email notifications for additional alert channels.
by Davide
This workflow automates the process of sending personalized lead-nurturing emails and tracking when each recipient opens the message through a custom tracking pixel. It integrates Google Sheets, Gmail, OpenAI, and webhooks to generate, deliver, and monitor engagement with your email sequence. It sends personalized emails containing a unique, invisible tracking pixel and then monitors who opens the email by detecting when the pixel is loaded, logging the activity back to a Google Sheets CRM. Key Features ✅ 1. Fully Automated Lead Nurturing Once leads are added to the Google Sheet, the workflow handles everything: Generating email content Creating tracking pixels Sending emails Updating CRM fields No manual actions required. ✅ 2. Real-Time Email Open Tracking Thanks to the pixel + webhook integration: You instantly know when a lead opens an email Data is written back to the CRM automatically No external email marketing platforms are needed ✅ 3. Infinite Scalability with Zero Extra Cost You can send emails and track performance using: n8n (self-hosted or cloud) Gmail Google Sheets AI-generated content This replicates features of expensive tools like HubSpot or Mailchimp—without their limits or pricing tiers. ✅ 4. Clean and Organized CRM Updates The system keeps your CRM spreadsheet structured by automatically updating: Send dates Pixel IDs Open status This ensures you always have accurate, up-to-date engagement data. ✅ 5. Easy to Customize and Expand You can easily add: Multi-step email sequences Click tracking Lead scoring Zapier/Make integrations CRM synchronization The workflow is modular, so each step can be modified or extended. How it Works Load Lead Data from Google Sheets The workflow reads your CRM-like Google Sheet containing lead information (name, email, and status fields such as EMAIL 1 SEND, PIXEL EMAIL 1, etc.). This allows the system to fetch only the leads that haven’t received Email 1 yet. Generate a Unique Tracking Pixel For each lead, the workflow creates a unique identifier (“pixel ID”). This ID is later appended to a small invisible 1×1 image—your tracking pixel. Example pixel structure used in emails: When the email client loads this image, n8n detects the open event via the webhook. Use AI to Generate a Personalized HTML Email An OpenAI node creates the email body in HTML, inserting the tracking pixel directly inside the content. This ensures the email is personalized, consistent, and automatically includes the tracking mechanism. Send the Email via Gmail The Gmail node sends the generated HTML email to the lead. After sending, the workflow updates the Google Sheet to log: Email sent flag Pixel ID generated Sending date Detect Email Opens with Webhook + Pixel Image When the recipient opens the email, their client loads the hidden pixel. That triggers your webhook, which: Extracts the pixel ID and email address from the query parameters Matches it with the lead in Google Sheets Update CRM When Email Is Opened The workflow updates the CRM by marking OPEN EMAIL 1 as “yes” for the corresponding pixel ID. This transforms your sheet into a live tracking dashboard of lead engagement. Set up Steps To configure this workflow, follow these steps: Prepare the CRM: Make a copy of the provided Google Sheet template. In your copy, fill in the "DATE," "FIRST NAME," "LAST NAME," and "EMAIL" columns with your lead data. Configure the Workflow: In the "Get CRM," "Update CRM," and "Update Open email 1" nodes, update the documentId field to point to your new Google Sheet copy. In the "Generate Pixel" node, locate the webhook_url assignment. Replace the placeholder text https://YOUR_N8N_WEBHOOK_URL with the actual, production webhook URL generated by the "Webhook" node in your n8n environment. Important: After setting this, you must activate the workflow for the webhook to be live and able to receive requests. Configure Credentials: Ensure the following credentials are correctly set up in your n8n instance: Google Sheets OAuth2 API: For reading from and updating the CRM sheet. Gmail OAuth2: For sending emails. OpenAI API: For generating the email content. Test and Activate: Execute the workflow once manually to send test emails. Check the Google Sheet to confirm that the "EMAIL 1 SEND," "PIXEL EMAIL 1," and "EMAIL 1 DATE" columns are populated. Open one of the sent test emails to trigger the tracking pixel. Verify in the Google Sheet that the corresponding lead's "OPEN EMAIL 1" field is updated to "yes." Once testing is successful, activate the workflow. Summary This workflow provides a powerful, low-cost automation system that: Sends personalized AI-generated emails Tracks email opens via a unique pixel Logs all actions into Google Sheets Automatically updates lead engagement data Need help customizing? Contact me for consulting and support or add me on Linkedin.
by Rahul Joshi
📘 Description This automation streamlines developer billing and compliance tracking by integrating Jira, Gmail, and n8n into a single intelligent workflow. It fetches all project issues from Jira, calculates logged hours per team member, identifies missing time entries, and automatically generates professional invoice summaries — complete with text attachments — which are then emailed to each developer. The system ensures no time logs are missed, billing remains accurate, and finance teams receive transparent, auditable records — all without manual follow-ups. ⚙️ What This Workflow Does (Step-by-Step) 🟢 When Clicking ‘Execute Workflow’ Starts the entire billing and compliance cycle manually or on schedule. 📋 Fetch All Project Issues with Time Data Retrieves all Jira issues across projects, including: Time spent (seconds → hours) Assignee, project, sprint, and status info Priority and issue summaries This serves as the foundation for billing calculations and compliance checks. 📊 Aggregate Hours by Team Member Groups issues by assignee and calculates total hours logged per person. Outputs per-user data with: Name & email Total logged hours Full issue breakdown (status, sprint, priority) Forms the core dataset for both invoice creation and reminder logic. ⚠️ Identify Issues with Missing Time Logs Scans aggregated data to find issues where time = 0 hours. Generates HTML reminders with: Table of unlogged issues (key, summary, sprint, status) Personalized note urging time entry completion Only sends reminders to users who actually missed logs. Prevents manual follow-up and ensures billing accuracy. 💰 Generate Invoice Summary with Text Attachment Creates text-based invoice documents for each user with logged hours. Includes: Itemized issue breakdowns Hourly rate (default: $50/hr) Total hours & billing amount Auto-generated timestamp Exports invoices as text attachments (Invoice_{Assignee}.txt) in base64. 🔗 Combine Reminder & Invoice Data Streams Merges invoice data and reminder data into one unified stream, ensuring: All users (with or without logged hours) are processed Emails contain correct context and attachments Enables complete communication coverage in a single workflow. 🔧 Reconcile JSON & Binary Attachments Smartly merges JSON email metadata and binary invoice files post-merge. Handles complex data cases (missing binary or JSON) using fallback logic. Guarantees each email has a valid recipient and invoice attachment. 📧 Send Invoices & Reminders to Team Sends personalized emails to each developer with: Subject: project name Body: hours summary & reminder message Attachment: invoice text file (if available) Emails are automatically delivered via Gmail with audit trails. 🧩 Prerequisites Jira Software Cloud API credentials Gmail OAuth2 connection Configured hourly billing rate (default: $50/hr) Active n8n instance (self-hosted or cloud) 💡 Key Benefits ✅ Eliminates manual invoice generation ✅ Ensures accurate time tracking & compliance ✅ Sends automated reminders for missing hours ✅ Provides transparent, auditable billing communication ✅ Saves finance & project teams hours of manual effort 👥 Perfect For Tech & IT service companies billing by developer hours Project managers tracking time compliance Finance teams ensuring timely invoicing Agencies managing multiple sprint-based projects
by Hattie Elbahri
What this does This automation automatically sends an email with a random Bible verse to a specified recipient every morning, as well as some reflections on the meaning of that verse. Start your day off grounded and faithful. Requirements n8n Gmail account with OAuth2 credentials enabled Google Gemini(PaLM) API credentials enabled How this works Runs every morning at 7:00a. Reads the config value send_to_email Calls bible.api for a random verse Uses Gemini to analyze the random verse and create the body text for the email Sends an Email to the recipient specified by send_to_email Subject reads "Daily Bible Verse: Inspiration for Today (book #:#)" How to set up In the "Config - recipient" node, in the send_to_email field, replace "example@example.com" with the desired recipient email Add your Google Gemini(PaLM) API credentials Add your Gmail OAuth2 credentials (optional) In the "Schedule trigger" node, keep the default schedule at 7:00a or change the hour as desired Test the flow by running it to verify the subject and body content. How to customize the workflow Change the send time in the Schedule Trigger node Change the Bible translation, or specify Old vs. New Testament in the Bible API node Adjust the prompt in the Gemini node to change the email content Modify the subject line in the Gmail node