Create & validate digital certificates with PDF Generator API and Gmail
Automated Certificate Creation & Verification (PDF Template-based)
π Overview
This n8n workflow provides a complete end-to-end system for creating, distributing, and verifying digital certificates, using PDF Generator API templates instead of raw HTML.
It is designed as a production-ready MVP, fully functional and tested, that can be imported and adapted with minimal configuration.
The workflow exposes public endpoints to:
- generate personalized certificates as PDFs
- assign unique Certification IDs
- email certificates automatically
- verify certificate authenticity via API
π― Typical use cases
This workflow is ideal for:
- training providers and academies
- online courses and bootcamps
- internal company certifications
- workshops and events
- proof-of-completion documents
Any scenario where certificates must be generated automatically and verified reliably.
βοΈ What this workflow does
1οΈβ£ Certificate creation (Webhook)
Endpoint
POST /certifications2
When triggered, the workflow:
- Receives candidate data (name, surname, course, email)
- Generates a unique Certification ID
- Ensures the ID does not already exist
- Stores certificate data in an n8n Data Table
- Generates a PDF using a PDF Generator API template
- Sends the certificate via email as a PDF attachment
2οΈβ£ PDF generation (Template-based)
Instead of HTML, the workflow sends a JSON payload to a predefined PDF template.
Example payload:
{
"Candidate": "John Doe",
"CourseName": "Advanced n8n Automation",
"DueDate": "2025-01-10",
"ID": "LQ4Z5H8R2A1F"
}
The PDF layout (fonts, colors, logos, formatting) is fully managed via the PDF Generator API Template UI, keeping the workflow clean and maintainable.
3οΈβ£ Email delivery
- Uses Gmail OAuth2
- Sends a customizable email
- Attaches the generated certificate PDF automatically
4οΈβ£ Certificate verification
Endpoint
GET /certificationscheck?id=CERTIFICATION-ID
This endpoint:
- checks if the Certification ID exists
- returns validation status and candidate info
Example response (valid):
{
"ok": true,
"name": "John",
"surname": "Doe"
}
This enables public, API-based certificate verification.
π Requirements
Before importing the workflow, you need:
-
n8n instance (cloud or self-hosted)
-
n8n Data Table with the following fields:
Name(string)Surname(string)CertificationID(string)
-
PDF Generator API account
-
Gmail OAuth2 credentials
-
Ability to expose webhook endpoints publicly
π Setup guide
Step 1 β Import the workflow
- Open n8n
- Go to Workflows β Import
- Paste the provided workflow JSON
Step 2 β Configure the Data Table
Create (or reuse) an n8n Data Table with these fields:
| Field | Type | | --------------- | ------ | | Name | string | | Surname | string | | CertificationID | string |
Update the following nodes to reference your Data Table:
Insert_CertificationFind_Certification_By_IDFind_Certification_By_ID1
Step 3 β Configure PDF Generator API
-
Create a PDF template in PDF Generator API
-
Add placeholders such as:
{Candidate}{CourseName}{DueDate}{ID}
-
In n8n, set credentials on the Generate a PDF document node
β οΈ Placeholder names must exactly match the JSON keys used in the workflow.
Step 4 β Configure email credentials
- Open the Email Certificate node
- Set Gmail OAuth2 credentials
- Customize subject and message body if needed
Step 5 β Activate the workflow
-
Click Activate
-
Your endpoints are now live:
/certifications2/certificationscheck
π§ͺ Status & notes
-
This workflow is an MVP, but already production-ready
-
Designed to be:
- modular
- reusable
- easy to extend
-
Recommended version for new implementations
-
HTML-based version is kept only for reference/backward compatibility
π‘ Customization ideas
You can easily extend this workflow by:
- adding QR codes to certificates
- storing additional metadata
- integrating with LMS platforms
- adding a public verification webpage
- switching email provider
n8n Workflow: Digital Certificate Validation and Email Notification
This n8n workflow provides a robust framework for creating and validating digital certificates. While the provided JSON is a skeleton, it outlines a common pattern for handling incoming data, applying conditional logic, and sending notifications. This workflow is designed to be highly customizable for various certificate generation and validation scenarios, potentially integrating with a PDF generator API and Gmail for distribution and alerts.
What it does
This workflow establishes a foundation for automating a digital certificate process. Based on the current JSON, here's a breakdown of its core components:
- Receives External Data: It starts with a
Webhooknode, indicating that the workflow is triggered by an external HTTP request. This webhook would typically receive data related to certificate requests, such as recipient details, certificate type, or validation parameters. - Conditional Logic: An
Ifnode is present, which is crucial for implementing decision-making within the workflow. This node would be configured to evaluate conditions based on the incoming webhook data. For example, it could check if a certificate request is valid, if all necessary data is provided, or if a specific validation status is met. - Data Transformation/Processing: A
Codenode is included, allowing for custom JavaScript logic. This is where complex data manipulation, formatting, or integration with external APIs (like a PDF generator for certificate creation or a validation service) would occur. - Email Notification: A
Gmailnode is part of the flow, suggesting that email notifications are a key component. This could be used to send generated certificates, notify administrators of validation results, or alert users about certificate status. - Respond to Trigger: A
Respond to Webhooknode is used to send a response back to the system that initiated the webhook call, indicating the success or failure of the workflow execution. - Data Table for Configuration/Lookup: A
Data tablenode is included, which can serve as a local data store within the workflow. This could be used to store configuration parameters, lookup tables for certificate templates, or track certificate IDs. - Documentation/Notes: A
Sticky Notenode is present, serving as a place for comments or explanations within the workflow, which is helpful for documentation and understanding.
Prerequisites/Requirements
To fully implement and utilize this workflow, you will need:
- n8n Instance: A running instance of n8n.
- Webhook Source: An external system capable of sending HTTP requests to trigger the workflow.
- Gmail Account: Configured as a credential in n8n for sending emails.
- PDF Generator API (Optional, but likely): If the goal is to create digital certificates, integration with a PDF generation service (e.g., PDF Generator API, DocRaptor, etc.) will be necessary.
- Certificate Validation Service (Optional): Depending on the validation requirements, an external service or custom code to verify certificate authenticity or data integrity might be needed.
- Custom Logic: Familiarity with JavaScript for customizing the
Codenode.
Setup/Usage
- Import the Workflow: Download the provided JSON and import it into your n8n instance.
- Configure Webhook:
- Activate the
Webhooknode. - Copy the generated webhook URL. This URL will be used by your external system to trigger the workflow.
- Activate the
- Set up Gmail Credentials:
- Create or select an existing Gmail credential in n8n.
- Ensure it has the necessary permissions to send emails.
- Customize
IfNode:- Define the conditions in the
Ifnode based on your validation rules. For example,{{ $json.isValid === true }}. - Connect the
TrueandFalseoutputs to subsequent nodes for different processing paths.
- Define the conditions in the
- Develop
CodeNode Logic:- Edit the
Codenode to implement your specific business logic. This might include:- Calling a PDF generator API with data from the webhook to create a certificate.
- Performing data transformations or calculations.
- Interacting with a database or other services.
- Edit the
- Configure
GmailNode:- Specify the recipient email addresses (e.g., from the webhook data, or a fixed address).
- Compose the email subject and body.
- Attach the generated PDF certificate (if applicable, from the
Codenode output).
- Configure
Data Table(Optional):- Populate the
Data tablewith any static data or configuration needed for your workflow.
- Populate the
- Activate the Workflow: Once configured, activate the workflow to make it live.
- Trigger the Workflow: Send an HTTP POST request to the
WebhookURL with the necessary data to initiate the certificate generation/validation process.
Related Templates
AI multi-agent executive team for entrepreneurs with Gemini, Perplexity and WhatsApp
This workflow is an AI-powered multi-agent system built for startup founders and small business owners who want to automate decision-making, accountability, research, and communication, all through WhatsApp. The βvirtual executive team,β is designed to help small teams to work smarter. This workflow sends you market analysis, market and sales tips, It can also monitor what your competitors are doing using perplexity (Research agent) and help you stay a head, or make better decisions. And when you feeling stuck with your start-up accountability director is creative enough to break the barrier π― Core Features π§βπΌ 1. President (Super Agent) Acts as the main controller that coordinates all sub-agents. Routes messages, assigns tasks, and ensures workflow synchronization between the AI Directors. π 2. Sales & Marketing Director Uses SerpAPI to search for market opportunities, leads, and trends. Suggests marketing campaigns, keywords, or outreach ideas. Can analyze current engagement metrics to adjust content strategy. π΅οΈββοΈ 3. Business Research Director Powered by Perplexity AI for competitive and market analysis. Monitors competitor moves, social media engagement, and product changes. Provides concise insights to help the founder adapt and stay ahead. β° 4. Accountability Director Keeps the founder and executive team on track. Sends motivational nudges, task reminders, and progress reports. Promotes consistency and discipline β key traits for early-stage success. ποΈ 5. Executive Secretary Handles scheduling, email drafting, and reminders. Connects with Google Calendar, Gmail, and Sheets through OAuth. Automates follow-ups, meeting summaries, and notifications directly via WhatsApp. π¬ WhatsApp as the Main Interface Interact naturally with your AI team through WhatsApp Business API. All responses, updates, and summaries are delivered to your chat. Ideal for founders who want to manage operations on the go. βοΈ How It Works Trigger: The workflow starts from a WhatsApp Trigger node (via Meta Developer Account). Routing: The President agent analyzes the incoming message and determines which Director should handle it. Processing: Marketing or sales queries go to the Sales & Marketing Director. Research questions are handled by the Business Research Director. Accountability tasks are assigned to the Accountability Director. Scheduling or communication requests are managed by the Secretary. Collaboration: Each sub-agent returns results to the President, who summarizes and sends the reply back via WhatsApp. Memory: Context is maintained between sessions, ensuring personalized and coherent communication. π§© Integrations Required Gemini API β for general intelligence and task reasoning Supabase- for RAG and postgres persistent memory Perplexity API β for business and competitor analysis SerpAPI β for market research and opportunity scouting Google OAuth β to connect Sheets, Calendar, and Gmail WhatsApp Business API β for message triggers and responses π Benefits Acts like a team of tireless employees available 24/7. Saves time by automating research, reminders, and communication. Enhances accountability and strategy consistency for founders. Keeps operations centralized in a simple WhatsApp interface. π§° Setup Steps Create API credentials for: WhatsApp (via Meta Developer Account) Gemini, Perplexity, and SerpAPI Google OAuth (Sheets, Calendar, Gmail) Create a supabase account at supabase Add the credentials in the corresponding n8n nodes. Customize the system prompts for each Director based on your startupβs needs. Activate and start interacting with your virtual executive team on WhatsApp. Use Case You are a small organisation or start-up that can not afford hiring; marketing department, research department and secretar office, then this workflow is for you π‘ Need Customization? Want to tailor it for your startup or integrate with CRM tools like Notion or HubSpot? You can easily extend the workflow or contact the creator for personalized support. Consider adjusting the system prompt to suite your business
π How to transform unstructured email data into structured format with AI agent
This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From β senderβs email address To β recipientβs email address Subject β email subject line Summary β short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits β Full Automation: Eliminates manual reading and data entry from incoming emails. β Multi-Source Integration: Handles data from different email providers seamlessly. β AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. β Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. β Time Efficiency: Processes emails in real time, improving productivity and response speed. *β Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.
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