Hackathon participant badge generator with QR code, PDF & email delivery
Title
Hackathon Participant Badge Generator with QR Code & Email Delivery
Description
A fast, reliable, and fully automated workflow that generates professional participant badges for hackathons, tech events, and workshops — complete with unique Badge ID, QR verification, PDF output, and email delivery.
This workflow takes any simple registration input and transforms it into a verified, branded participant badge in under 10 seconds.
What this workflow does
-
Accepts event registrations via a POST Webhook (name, email, event, team, role).
-
Performs input validation and disposable/fake email detection using VerifiEmail.
-
Creates a unique Badge ID (e.g.,
HACK-2025-1763560499-AB3XYF). -
Generates a public verification URL and QR code for check-in.
-
Builds a high-resolution badge (1056×816px) with event branding, logo, gradient background, and QR code.
-
Converts the HTML badge design into a print-ready PDF using PDFMunk (htmlcsstopdf).
-
Sends a beautiful HTML email via Gmail that includes:
- Inline badge preview (visible immediately)
- Attached PDF badge
- Verification URL + Badge ID
-
Logs all badge metadata to Google Sheets for audit and check-in tracking.
-
Returns a clean JSON success response to the caller.
Use Cases
Ideal for:
- Hackathons & tech conferences
- Engineering fests & competitions
- Workshops, meetups, bootcamps
- Any event requiring verified digital badges with QR check-in
Key Features
- Real-time email verification blocks fake/disposable registrations.
- QR code check-in powered by a reliable public QR API.
- Fully customizable badge design — swap logos, colors, fonts easily.
- Inline email preview means participants see their badge instantly.
- Complete event log stored in Google Sheets with timestamps, PDF links, and verification URLs.
- Extendable (add Slack alerts, Drive uploads, role-based templates, etc.)
Setup Instructions (5 Minutes)
-
Add your credentials:
- VerifiEmail
- PDFMunk (HTML → PDF)
- Gmail
- Google Sheets
-
Update your:
- Logo URL
- Verification domain
-
Activate the workflow and start sending POST requests to the Webhook.
-
Badges will be generated and emailed automatically — no manual work needed.
Why this workflow is special
It’s built for speed, reliability, visual quality, and zero manual overhead. Participants receive a sleek, branded badge instantly, organizers get automated logs, and your event gets a professional identity.
Perfect for teams who want enterprise-grade badge automation without writing a single line of code.
Tags
hackathon, badge, qr-code, pdf, email, gmail, automation, participant, event, check-in, google-sheets
Hackathon Participant Badge Generator with QR Code, PDF & Email Delivery
This n8n workflow automates the process of generating personalized hackathon participant badges with QR codes, creating them as PDFs, and delivering them via email. It's designed to streamline event registration and participant management by automating the creation and distribution of essential event credentials.
What it does
This workflow simplifies the badge generation and delivery process through the following steps:
- Receives Participant Data: It starts by listening for incoming participant data via a webhook. This data is expected to contain details such as the participant's name, email, and potentially other information required for the badge.
- Processes Data for Badge Generation: A
Functionnode is used to process the incoming data. This likely involves formatting the data, generating a unique QR code URL (or data), and preparing it for the badge creation service. - Generates Badges (External Service): An
HTTP Requestnode sends the processed participant data to an external service (e.g., a badge generation API like Bannerbear, PDFMonkey, or a custom service). This service is responsible for creating the actual PDF badge, embedding the QR code, and laying out the participant's information. - Retrieves Badge PDF: The
HTTP Requestnode then receives the generated badge, likely as a PDF file or a URL to the PDF. - Checks for Badge Generation Success: An
Ifnode evaluates the response from the badge generation service to determine if the badge was successfully created. - Sends Email with Badge:
- On Success: If the badge generation was successful, a
Gmailnode sends an email to the participant. This email includes the generated PDF badge as an attachment. - On Failure: If the badge generation failed, the workflow might send an internal notification (not explicitly shown in the JSON but a common practice) or respond to the webhook with an error.
- On Success: If the badge generation was successful, a
- Responds to Webhook: Finally, a
Respond to Webhooknode sends a response back to the system that triggered the workflow, indicating the success or failure of the badge generation and delivery process.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Webhook Trigger: An external system or application configured to send participant data to the n8n webhook URL.
- Google Sheets (Optional): While not directly connected in the provided JSON, the presence of the Google Sheets node suggests it might be used for inputting participant data or logging results in a more complete workflow.
- External Badge Generation Service: An API endpoint for a service capable of generating PDF documents with dynamic data and QR codes (e.g., Bannerbear, PDFMonkey, DocRaptor, or a custom API). You will need an API key or authentication details for this service.
- Gmail Account: A configured Gmail credential in n8n to send emails.
- Basic JavaScript Knowledge: For customizing the
Functionnode to fit your specific data processing and QR code generation logic.
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Webhook:
- Activate the
Webhooknode and copy its test or production URL. - Configure your external system to send participant data (e.g.,
name,email,uniqueId) to this URL. The data should be in a JSON format that theFunctionnode can process.
- Activate the
- Configure Function Node:
- Edit the
Functionnode (ID 14) to transform the incoming webhook data into the format expected by your badge generation service. This is also where you would typically generate the QR code data (e.g., a URL pointing to participant details).
- Edit the
- Configure HTTP Request Node:
- Update the
HTTP Requestnode (ID 19) with the URL of your badge generation API. - Configure the HTTP method (e.g., POST) and the request body to send the data prepared by the
Functionnode. - Add any necessary authentication headers (e.g., API Key).
- Ensure it's configured to expect a PDF file or a URL to a PDF in response.
- Update the
- Configure If Node:
- Review the
Ifnode (ID 20) conditions to accurately check for the success of the badge generation API call. This might involve checking HTTP status codes or specific fields in the API response.
- Review the
- Configure Gmail Node:
- Select your Gmail credential.
- Set the recipient email address using an expression like
={{$json.email}}to dynamically send to the participant. - Compose the email subject and body.
- Attach the generated PDF badge. You'll need to reference the output of the
HTTP Requestnode that contains the PDF data or URL.
- Activate Workflow: Once all nodes are configured, activate the workflow.
This workflow provides a robust foundation for automating hackathon badge generation and delivery, ensuring participants receive their credentials efficiently.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte