Back to Catalog

Generate PDF invoices with CustomJS API

CustomJSCustomJS
7567 views
2/3/2026
Official Page

workflow.png

n8n Workflow: Invoice PDF Generator

This n8n workflow captures invoice data and generates a PDF invoice, ready to be sent or saved. It uses a webhook to trigger the process, preprocesses the invoice data, and converts it to a PDF using HTML and custom styling.

@custom-js/n8n-nodes-pdf-toolkit

Features:

  • Webhook Trigger: Receives incoming data, including invoice details.
  • Preprocessing: Transforms the invoice data into HTML format.
  • HTML to PDF Conversion: Converts the preprocessed HTML into a styled PDF document.
  • Response: Sends the generated PDF back to the webhook response.

Notice

Community nodes can only be installed on self-hosted instances of n8n.

Requirements

  • Self-hosted n8n instance
  • A CustomJS API key for website screenshots.
  • Invoice data for PDF generation

Workflow Steps:

  1. Webhook Trigger:

    • Accepts incoming data (e.g., invoice number, recipient details, itemized list).
    • This data is passed to the next node for processing.
  2. Set Data Node:

    • Configures initial values for the invoice, including the recipient, sender, invoice number, and the items on the invoice.
    • The invoice details include information like description, unit price, and quantity.
  3. Preprocess Node:

    • Processes the raw data to format it correctly for HTML. This includes splitting addresses and converting the items into an HTML table format.
  4. HTML to PDF Conversion:

    • Converts the generated HTML into a PDF document. The HTML includes a header, a detailed invoice table, and a footer with contact information.
  5. Respond to Webhook:

    • Returns the generated PDF as a response to the initial webhook request.

Setup Guide:

1. Configure CustomJS API

  • Sign up at CustomJS.
  • Retrieve your API key from the profile page. 1.png
  • Add your API key as n8n credentials. 2.png

2. Design Workflow

  1. Create a Webhook:

    • Set up a webhook to trigger the workflow when invoice data is received.
  2. Prepare Data:

    • Ensure the incoming request contains fields like "Invoice No", "Bill To", "From", and "Details" (list of items with price and quantity).
  3. Customize the HTML:

    • The HTML template for the invoice includes custom styling to give the invoice a professional look.
  4. Convert to PDF:

    • The HTML to PDF node is configured with the data generated from the preprocessing step to convert the invoice HTML to a PDF format.

Example Invoice Data:

{
  "Invoice No": "1",
  "Bill To": "John Doe\n1234 Elm St, Apt 567\nCity, Country, 12345",
  "From": "ABC Corporation\n789 Business Ave\nCity, Country, 67890",
  "Details": [
    {
      "description": "Web Hosting",
      "price": 150,
      "qty": 2
    },
    {
      "description": "Domain",
      "price": 15,
      "qty": 5
    }
  ],
  "Email": "support@mycompany.com"
}

Result PDF File

3.png

Generate PDF Invoices with Custom JavaScript API

This n8n workflow demonstrates how to set up a basic API endpoint that can be extended to generate dynamic content, such as PDF invoices, using custom JavaScript logic. It provides a foundational structure for receiving data via a webhook, processing it with custom code, and sending a response.

What it does

This workflow simplifies the process of creating an API endpoint with custom logic:

  1. Listens for incoming requests: An HTTP Webhook node acts as the entry point, waiting for external systems to send data.
  2. Processes data with custom JavaScript: The Code node allows you to write arbitrary JavaScript to manipulate the incoming data, perform calculations, or interact with other services (which you would add).
  3. Sets output fields: The Edit Fields (Set) node is used to define and structure the data that will be sent back in the response.
  4. Responds to the webhook: The Respond to Webhook node sends a custom response back to the system that initiated the webhook call.

Prerequisites/Requirements

  • An n8n instance (self-hosted or cloud).
  • Basic understanding of JavaScript for customizing the "Code" node.

Setup/Usage

  1. Import the workflow:
    • Save the provided JSON content as a .json file.
    • In your n8n instance, click "Workflows" in the left sidebar.
    • Click "New" and then "Import from JSON".
    • Select the saved .json file.
  2. Activate the Webhook:
    • Click on the "Webhook" node.
    • Copy the "Webhook URL" provided. This is the endpoint you will call.
  3. Customize the Code Node:
    • Click on the "Code" node.
    • Modify the JavaScript code within the node to implement your desired logic. For example, you could add code to:
      • Parse incoming invoice data.
      • Generate dynamic HTML for a PDF.
      • Call an external PDF generation API (e.g., using an HTTP Request node, which you would add).
      • Perform data validation or transformation.
  4. Configure the Edit Fields Node:
    • Click on the "Edit Fields" node.
    • Adjust the fields and their values to format the data you want to return in the webhook response.
  5. Test the workflow:
    • Once the workflow is active, send an HTTP POST request to the Webhook URL you copied in step 2. You can use tools like Postman, Insomnia, curl, or any application capable of making HTTP requests.
    • Observe the execution in n8n to ensure it runs as expected.
    • The response from the webhook will contain the data defined in the "Edit Fields" node.

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.

Ranjan DailataBy Ranjan Dailata
161

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

Daniel NkenchoBy Daniel Nkencho
601

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

Wessel BulteBy Wessel Bulte
247