Generate professional email signatures in HTML & PDF with Gmail delivery
Dynamic Email Signature Creator (PDF + HTML)
Create gorgeous, branded, professional email signatures automatically — from a simple POST request. This workflow turns user details into a premium HTML signature, converts it into PDF, and delivers it instantly via Gmail, along with a clean JSON response.
✨ What This Template Does
This workflow automatically:
- Receives user details (name, role, email, phone, links) via Webhook
- Extracts & validates inputs
- Generates a modern, premium HTML signature with icons + layout
- Converts HTML → high-quality PDF using HTMLCSS → PDF service
- Emails both the HTML signature preview + PDF attachment to the user
- Returns a clean JSON success response with the
pdf_url - Works 100% automated — no manual designing needed
Perfect for:
- HR onboarding
- Corporate identity management
- Personal branding
- Team signature standardization
- Automated client signature setup
🔥 Features
- Beautiful modern design
- Clean branding layout with icons (LinkedIn, Instagram, Website)
- Professional color palette + typography
- Auto-generated PDF (print-ready)
- Mobile-friendly & email-safe HTML
- Supports any social links
- Extremely easy to integrate with forms, portals, CRMs
- Fast: Signature generated in < 3 seconds
🧩 How It Works
- Webhook receives user information
- Input extractor formats the fields
- HTML template dynamically inserts user values
- HTML → PDF generator creates high-resolution output
- Email node sends signature + PDF
- Workflow responds with JSON (
pdf_url,status, etc.)
⚙️ Setup Needed
Connect these credentials in n8n:
- HTML → PDF (PDFMunk account)
- Gmail (for sending the final signature email)
Update inside the HTML template:
- Brand colors
- Logo URL (optional)
- Social icon colors / links (optional)
That’s it — your automated signature generator is live.
🏷️ Tags
email-signature, branding, pdf-generator, html-template, gmail, automation, onboarding, corporate
Generate Professional Email Signatures in HTML & PDF with Gmail Delivery
This n8n workflow automates the creation of professional email signatures in both HTML and PDF formats, then delivers them via Gmail. It's designed to streamline the process of generating consistent and branded signatures for individuals or teams.
What it does
This workflow performs the following key steps:
- Receives Input: It starts by listening for incoming data via a Webhook. This data is expected to contain the necessary information for generating an email signature.
- Prepares Data: An "Edit Fields (Set)" node processes the incoming data, likely structuring or transforming it for subsequent use in the signature generation.
- Generates Signature (HTML/PDF): An "HTTP Request" node is used to interact with an external service or API to generate the email signature. Based on the directory name, this step likely involves generating both HTML and PDF versions of the signature.
- Processes Output: A "Code" node executes custom JavaScript, which could be used to further process the generated signature data, extract specific parts, or prepare it for email delivery.
- Delivers via Gmail: The "Gmail" node sends an email containing the generated signature(s) to the designated recipient(s).
- Responds to Webhook: Finally, the "Respond to Webhook" node sends a response back to the original caller of the webhook, indicating the successful completion of the workflow.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running instance of n8n.
- Webhook Trigger: An external system or application configured to send data to the n8n webhook URL.
- External Signature Generation Service/API: An API endpoint that can generate email signatures (HTML and/or PDF) based on provided data. The "HTTP Request" node will need to be configured with the URL and authentication for this service.
- Gmail Account: A configured Gmail credential within n8n to send emails.
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Webhook:
- Activate the "Webhook" node.
- Copy the test or production webhook URL. This is the endpoint your external system will send data to.
- Configure "Edit Fields (Set)": Review and adjust the fields being set or transformed based on your input data structure.
- Configure "HTTP Request":
- Set the
URLto your external signature generation service. - Configure the
Method(e.g., POST) andBodyto send the necessary signature data (e.g., name, title, company, contact info) to the service. - Add any required
Headersfor authentication (e.g., API keys).
- Set the
- Configure "Code": If the external service returns data that needs further manipulation before sending via Gmail, update the JavaScript in the "Code" node accordingly.
- Configure "Gmail":
- Select or create a new Gmail OAuth2 credential.
- Set the
Toemail address (e.g., from the webhook input). - Configure the
SubjectandBodyof the email. You will likely attach the generated HTML and/or PDF signature here. - Ensure the
Operationis set to "Send an Email".
- Configure "Respond to Webhook": Customize the response body if needed.
- Activate the Workflow: Once all nodes are configured, activate the workflow.
Now, whenever data is sent to the webhook, the workflow will trigger, generate the signature, and send it via Gmail.
Related Templates
Send WooCommerce discount coupons to customers via WhatsApp using Rapiwa API
Who is this for? This workflow is ideal for WooCommerce store owners who want to automatically send promotional WhatsApp messages to their customers when new coupons are created. It’s designed for marketers and eCommerce managers looking to boost engagement, streamline coupon sharing, and track campaign performance effortlessly through Google Sheets. Overview This workflow listens for WooCommerce coupon creation events (coupon.created) and uses customer billing data to send promotional WhatsApp messages via the Rapiwa API. The flow formats the coupon data, cleans phone numbers, verifies WhatsApp registration with Rapiwa, sends the promotional message when verified, and logs each attempt to Google Sheets (separate sheets for verified/sent and unverified/not sent). What this Workflow Does Listens for new coupon creation events in WooCommerce via the WooCommerce Trigger node Retrieves all customer data from the WooCommerce store Processes customers in batches to control throughput Cleans and formats customer phone numbers for WhatsApp Verifies if phone numbers are valid WhatsApp accounts using Rapiwa API Sends personalized WhatsApp messages with coupon details to verified numbers Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Automated coupon distribution: Triggers when new coupons are created in WooCommerce Customer data retrieval: Fetches all customer information from WooCommerce Phone number validation: Verifies WhatsApp numbers before sending messages Personalized messaging: Includes customer name and coupon details in messages Dual logging system: Tracks both successful and failed message attempts Rate limiting: Uses batching and wait nodes to prevent API overload Data formatting: Structures coupon information for consistent messaging Google Sheet Column Structure A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: | name | number | email | address1 | couponCode | couponTitle | couponType | couponAmount | createDate | expireDate | validity | status | | ----------- | ------------- | --------------------------------------------------- | --------- | ---------- | -------------- | ---------- | ------------ | ------------------- | ------------------- | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | verified | sent | Requirements n8n instance with the following nodes: WooCommerce Trigger, Code, SplitInBatches, HTTP Request, IF, Google Sheets, Wait WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Message Content: The current message template references the first coupon only (coupons[0]). Adjust if you need to handle multiple coupons. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen
Generate Weather-Based Date Itineraries with Google Places, OpenRouter AI, and Slack
🧩 What this template does This workflow builds a 120-minute local date course around your starting point by querying Google Places for nearby spots, selecting the top candidates, fetching real-time weather data, letting an AI generate a matching emoji, and drafting a friendly itinerary summary with an LLM in both English and Japanese. It then posts the full bilingual plan with a walking route link and weather emoji to Slack. 👥 Who it’s for Makers and teams who want a plug-and-play bilingual local itinerary generator with weather awareness — no custom code required. ⚙️ How it works Trigger – Manual (or schedule/webhook). Discovery – Google Places nearby search within a configurable radius. Selection – Rank by rating and pick the top 3. Weather – Fetch current weather (via OpenWeatherMap). Emoji – Use an AI model to match the weather with an emoji 🌤️. Planning – An LLM writes the itinerary in Markdown (JP + EN). Route – Compose a Google Maps walking route URL. Share – Post the bilingual itinerary, route link, and weather emoji to Slack. 🧰 Requirements n8n (Cloud or self-hosted) Google Maps Platform (Places API) OpenWeatherMap API key Slack Bot (chat:write) LLM provider (e.g., OpenRouter or DeepL for translation) 🚀 Setup (quick) Open Set → Fields: Config and fill in coords/radius/time limit. Connect Credentials for Google, OpenWeatherMap, Slack, and your LLM. Test the workflow and confirm the bilingual plan + weather emoji appear in Slack. 🛠 Customize Adjust ranking filters (type, min rating). Modify translation settings (target language or tone). Change output layout (side-by-side vs separated). Tune emoji logic or travel mode. Add error handling, retries, or logging for production use.
Monitor stock market with AI: news analysis & multi-channel alerts via Slack & Telegram
AI Customer Support Triage with Gmail, OpenAI, Airtable & Slack How it Works This workflow monitors your Gmail support inbox every minute, automatically sending each unread email to OpenAI for intelligent analysis. The AI evaluates sentiment (Positive/Neutral/Negative/Critical), urgency level (Low/Medium/High/Critical), categorizes requests (Technical/Billing/Feature Request/Bug Report/General), extracts key issues, and generates professional response templates. The system calculates a priority score (0-110) by combining urgency and sentiment weights, then routes tickets accordingly. Critical issues trigger immediate Slack alerts with full context and 30-minute SLA reminders, while routine tickets post to standard monitoring channels. Every ticket logs to Airtable with complete analysis and thread tracking, then updates a Google Sheets dashboard for real-time analytics. A secondary AI pass generates strategic insights (trend identification, risk assessment, actionable recommendations) and stores them back in Airtable. The entire process takes seconds from email arrival to team notification, eliminating manual triage and ensuring critical issues get immediate attention. --- Who is this for? Customer support teams needing automated prioritization for high email volumes SaaS companies tracking support metrics and response times Startups with lean teams requiring intelligent ticket routing E-commerce businesses managing technical, billing, and return inquiries Support managers needing data-driven insights into customer pain points --- Setup Steps Setup time: 20-30 minutes Requirements: Gmail, OpenAI API key, Airtable account, Google Sheets, Slack workspace Monitor Support Emails: Connect Gmail via OAuth2, configure INBOX monitoring for unread emails AI Analysis Engine: Add OpenAI API key, system prompt pre-configured for support analysis Parse & Enrich Data: JavaScript code automatically calculates priority scores (no changes needed) Route by Urgency: Configure routing rules for critical vs routine tickets Slack Alerts: Create Slack app, get bot token and channel IDs, replace placeholders in nodes Airtable Database: Create base with "tblSupportTickets" table, add API key and Base ID (replace appXXXXXXXXXXXXXX) Google Sheets Dashboard: Create spreadsheet, enable Sheets API, add OAuth2 credentials, replace Sheet ID (1XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX) Generate Insights: Second OpenAI call analyzes patterns, stores insights in Airtable Test: Send test email, verify Slack alerts, check Airtable/Sheets data logging --- Customization Guidance Priority Scoring: Adjust urgency weight (25) and sentiment weight (10) in Code node to match your SLA requirements Categories: Modify AI system prompt to add industry-specific categories (e.g., healthcare: appointments, prescriptions) Routing Rules: Add paths for High urgency, VIP customers, or specific categories Auto-Responses: Insert Gmail send node after routine tickets for automatic acknowledgment emails Multi-Language: Add Google Translate node for non-English support VIP Detection: Query CRM APIs or match email domains to flag enterprise customers Team Assignment: Route different categories to dedicated Slack channels by department Cost Optimization: Use GPT-3.5 (~$0.001/email) instead of GPT-4, self-host n8n for unlimited executions --- Once configured, this workflow operates as your intelligent support triage layer—analyzing every email instantly, routing urgent issues to the right team, maintaining comprehensive analytics, and generating strategic insights to improve support operations. --- Built by Daniel Shashko Connect on LinkedIn