Public holiday lookup with Nager.Date API via webhook
This n8n template empowers you to instantly fetch a list of public holidays for any given year and country using the Nager.Date API. This is incredibly useful for scheduling, planning, or integrating holiday data into various business and personal automation workflows.
๐ง How it works
- Receive Holiday Request Webhook: This node acts as the entry point, listening for incoming POST requests. It expects a JSON body containing the year (e.g., 2025) and countryCode (e.g., US for United States, PH for Philippines, DE for Germany) for which you want to retrieve public holidays.
- Get Public Holidays: This node makes an HTTP GET request to the Nager.Date API (date.nager.at). It dynamically uses the year and countryCode from your webhook request to query the API. The API responds with a JSON array, where each object represents a public holiday with details like its date, name, and type.
- Respond with Holiday Data: This node sends the full list of public holidays received from Nager.Date back to the service that initiated the webhook.
๐ค Who is it for?
This workflow is ideal for:
- Businesses with International Operations: Automatically check holidays for different country branches to adjust production schedules, customer service hours, or delivery estimates.
- HR & Payroll Departments: Accurately calculate workdays, plan leave schedules, or process payroll taking public holidays into account.
- Event Planners: Avoid scheduling events on public holidays, which could impact attendance or venue availability.
- Travel Agencies: Inform clients about holidays in their destination country that might affect local business hours or attractions.
- Content & Social Media Schedulers: Plan content around national holidays to maximize engagement or avoid insensitive postings.
- Personal Productivity & Travel Planning: Integrate holiday data into your calendar or task management tools to plan trips or personal time off more effectively.
- Developers: Easily integrate a reliable source of public holiday data into custom applications, dashboards, or internal tools without managing complex datasets.
๐ Data Structure
When you trigger the webhook, send a POST request with a JSON body structured as follows:
{
"year": 2025,
"countryCode": "PH" // Example: "US", "DE", "GB", etc.
}
You can find a comprehensive list of supported country codes on the Nager.Date API documentation: https://www.nager.at/Country
The workflow will return a JSON array, where each element is a holiday object, like this example for a single holiday:
[
{
"date": "2025-01-01",
"localName": "New Year's Day",
"name": "New Year's Day",
"countryCode": "PH",
"fixed": true,
"global": true,
"counties": null,
"launchYear": null,
"types": [
"Public"
]
}
// ... more holiday objects
]
โ๏ธ Setup Instructions
- Import Workflow: In your n8n editor, click "Import from JSON" and paste the provided workflow JSON.
- Configure Webhook Path:
- Double-click the Receive Holiday Request Webhook node.
- In the 'Path' field, set a unique and descriptive path (e.g., /public-holidays).
- Activate Workflow: Save and activate the workflow.
๐ Tips
This workflow is a foundation for many powerful automations:
- Conditional Branching for Specific Holidays: Add an IF node after "Get Public Holidays" to check for a specific holiday (e.g., "Christmas Day"). You can then trigger different actions (e.g., send a reminder, adjust a schedule) only for that particular holiday.
- Filtering and Aggregating Data:
- Use a Filter node to only keep holidays of a certain type (e.g., "Public").
- Use a Code or Function node to count the number of public holidays, or extract just the names and dates into a simpler list.
- Storing Holiday Data:
- Google Sheets/Airtable: Automatically append new holidays to a spreadsheet for easy reference or further analysis.
- Database: Store holiday data in a database (like PostgreSQL or MySQL) to build a custom holiday calendar application.
- Scheduling and Reminders:
- Connect this workflow to a Cron or Schedule node to run periodically (e.g., once a year at the start of the year).
- Use the retrieved holiday dates to set up reminders in your calendar (Google Calendar node) or send notifications (Slack, Email, SMS) a few days before an upcoming holiday.
- Integrate with Business Logic:
- Employee Leave Management: Cross-reference employee leave requests with public holidays to ensure accuracy.
- Automated Messages: Schedule automated "Happy Holiday" messages to customers or employees.
- E-commerce Shipping: Adjust estimated shipping times based on upcoming non-working days.
- API Key (Not needed for Nager.Date free tier): The Nager.Date API used here does not require an API key for basic public holiday lookups, which makes this template very easy to use out-of-the-box.
Public Holiday Lookup with Nager.Date API via Webhook
This n8n workflow provides a simple API endpoint to query public holidays for a given country and year using the Nager.Date API. It's designed to be triggered by an external system via a webhook, making it easy to integrate holiday information into other applications or services.
What it does
- Listens for incoming requests: The workflow starts by exposing a webhook URL that waits for incoming HTTP POST requests.
- Makes an API call to Nager.Date: Upon receiving a request, it constructs a URL for the Nager.Date API (e.g.,
https://date.nager.at/api/v3/PublicHolidays/{year}/{countryCode}) using theyearandcountryCodeparameters provided in the incoming webhook data. It then makes an HTTP GET request to this API. - Responds to the webhook: Finally, it takes the data received from the Nager.Date API and sends it back as the response to the original webhook call.
Prerequisites/Requirements
- An active n8n instance.
- No external API keys are required for the Nager.Date API as it's publicly accessible.
Setup/Usage
-
Import the workflow:
- Save the provided JSON to a file (e.g.,
public-holiday-lookup.json). - In your n8n instance, go to "Workflows" and click "New".
- Click the three dots in the top right corner and select "Import from JSON".
- Upload the
public-holiday-lookup.jsonfile.
- Save the provided JSON to a file (e.g.,
-
Activate the workflow:
- Once imported, ensure the workflow is active by toggling the "Active" switch in the top right corner.
-
Get the Webhook URL:
- Click on the "Webhook" node (the first node in the workflow).
- Copy the "Webhook URL" displayed in the node's settings. This is the endpoint you will call.
-
Trigger the workflow:
- Send an HTTP POST request to the copied Webhook URL.
- The request body should be a JSON object containing
year(integer) andcountryCode(string, e.g., "US", "GB", "DE") properties.
Example cURL request:
curl -X POST -H "Content-Type: application/json" \ -d '{"year": 2024, "countryCode": "US"}' \ YOUR_N8N_WEBHOOK_URLReplace
YOUR_N8N_WEBHOOK_URLwith the actual URL you copied from the Webhook node.
The workflow will respond with a JSON array of public holidays for the specified year and country.
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 invoice processing with OCR, GPT-4 & Salesforce opportunity creation
PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive โ Download PDF โ OCR text โ AI normalize to JSON โ Upsert Buyer (Account) โ Create Opportunity โ Map Products โ Create OLI via Composite API โ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content โ the parsed JSON (ensure itโs an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id โ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total โ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger โ Download File From Google Download File From Google โ Extract from File โ Update File to One Drive Extract from File โ Message a model Message a model โ Create or update an account Create or update an account โ Create an opportunity Create an opportunity โ Build SOQL Build SOQL โ Query PricebookEntries Query PricebookEntries โ Code in JavaScript Code in JavaScript โ Create Opportunity Line Items --- Quick setup checklist ๐ Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. ๐ IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) ๐ง AI Prompt: Use the strict system prompt; jsonOutput = true. ๐งพ Field mappings: Buyer tax id/name โ Account upsert fields Invoice code/date/amount โ Opportunity fields Product name must equal your Product2.ProductCode in SF. โ Test: Drop a sample PDF โ verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep โReturn only a JSON arrayโ as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields donโt support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your orgโs domain or use the Salesforce nodeโs Bulk Upsert for simplicity.