Automatic job listings extraction and publishing template
Automatically extract job listings from any website URL, format them with AI, and publish directly to WordPress. Just send a URL via Telegram, and watch as the workflow scrapes the job details, enhances the content with GPT, and creates a polished post on your site.
💡 Why Use Job Repost?
⏰ Save countless hours
Automatically extract, process, and publish job offers from any website, freeing your time from repetitive tasks.
✅ Eliminate human errors
Say goodbye to typos and missed fields — every job post is validated before going live.
📈 Boost engagement
Fresh, well-structured job listings attract more candidates, improving your site's reach and authority.
🚀 Stay ahead
Leveraging AI with GPT means your content is not just automated but polished and SEO-friendly — the digital assistant you never knew you needed.
⚡ Perfect For
- Job board managers: Want to aggregate listings from multiple sources with minimal effort
- Recruiters & HR teams: Who need to streamline job posting workflows without technical hassles
- Content creators & marketers: Looking to automate publishing while maintaining style and SEO standards
🔧 How It Works
| Step | Process | Description | |------|---------|-------------| | 📱 | Trigger | Send a job URL via Telegram bot to initiate the process | | 🔥 | Extract | Firecrawl API scrapes and extracts clean content from the provided URL | | 📎 | Process | Job data is extracted via AI, text split and cleaned, job categories and types mapped to your system | | 🤖 | Smart Logic | GPT crafts formatted job posts, intelligent validation ensures all key data is present, default values fill in the blanks if necessary | | 💌 | Output | Posts automatically published to WordPress with company logos uploaded, and success or error notifications sent via Telegram | | 🗂 | Storage | Uses Supabase vector store for managing document embeddings, ensuring quick lookup and reference compliance |
🔐 Quick Setup
- Import the provided JSON file into your n8n instances
- Add credentials:
- Firecrawl API key
- Google Drive OAuth2 (for RAG storage)
- OpenAI API
- WordPress API
- Telegram API
- Supabase
- Customize:
- Telegram bot token
- WordPress URLs
- Default images and category mappings if needed
- Update: URLs and API tokens where placeholders are used
- Test: Send a job URL to your Telegram bot to verify accurate extraction and posting
🧩 You'll Need
- ✅ Active n8n instances
- ✅ Firecrawl account with API access
- ✅ Google Drive account for RAG document storage
- ✅ OpenAI account with GPT API access
- ✅ WordPress site with autojob plugin and API enabled
- ✅ Telegram bot for URL submission and notifications
- ✅ Supabase account for vector store management
🛠️ Level Up Ideas
- 🌍 Add multi-language support to expand global reach
- 🔗 Support batch URL processing for multiple jobs at once
- 💬 Integrate Slack or email notifications for wider team alerts
- 🎯 Use more AI nodes to summarize or rate job offers for quality control
- 🔄 Schedule periodic cleanup of vector store for performance optimization
- 📊 Add analytics tracking for published jobs performance
🧠 Nodes Used
Core Components:
- Firecrawl HTTP Request (Web scraping and content extraction)
- Google Drive (RAG document storage)
- Supabase Vector Store
- OpenAI (Embeddings, GPT Extraction)
- Code Nodes for mapping categories
- Telegram Trigger & Message
- HTTP Request (for WordPress API and image uploads)
Made by: Khaisa Studio
Tags: automation recruitment job-posting wordpress AI web-scraping firecrawl
Category: Human Resources, Recruitment, Wordpress, Scrapping
Need a custom? contact me on LinkedIn or Web
n8n Workflow: Error Handling Template
This n8n workflow provides a robust error handling mechanism for your n8n instances. It's designed to be used as a sub-workflow that gets triggered whenever another workflow execution fails, allowing you to centralize and manage error notifications.
What it does
This workflow is a template for handling errors that occur in other n8n workflows. When an error workflow is configured to trigger this template, it will:
- Receive Error Details: The workflow starts by catching error events from other n8n workflows.
- Process Error Data: It then processes the incoming error data to extract relevant information.
- Conditional Notification: It checks if a specific condition (likely related to the error message or type) is met.
- Send Telegram Notification (Conditional): If the condition is met, it sends a detailed error message to a designated Telegram chat.
- Log to Google Drive (Conditional): If the condition is met, it also logs the error details to a Google Drive file.
- Wait (Conditional): Introduces a delay, possibly for rate limiting or to allow other systems to catch up before further actions.
- Process Further (Placeholder): Includes nodes for advanced AI/Langchain operations (Text Splitting, OpenAI Embeddings, Supabase Vector Store, OpenAI processing) which are currently disconnected but provide a framework for future enhancements like automated error analysis or resolution suggestions.
- Generic HTTP Request (Placeholder): Includes an HTTP Request node, which could be used to send error details to a custom logging service, an incident management system, or another API.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance where you can import and activate this workflow.
- Telegram Account: A Telegram bot token and chat ID to send notifications.
- Google Drive Account: Configured Google Drive credentials to log errors to a file.
- OpenAI API Key (Optional): If you plan to enable the AI/Langchain nodes for advanced error analysis.
- Supabase Account (Optional): If you plan to use the Supabase Vector Store for advanced AI features.
Setup/Usage
- Import the Workflow:
- Download the provided JSON file.
- In your n8n instance, go to "Workflows" and click "New".
- Click the "Import from JSON" button and paste the workflow JSON or upload the file.
- Configure Credentials:
- Locate the "Telegram" and "Google Drive" nodes.
- Click on each node and configure your respective credentials. For Telegram, you'll need a bot token and chat ID. For Google Drive, you'll need to authenticate your Google account.
- If you plan to use the AI/Langchain nodes, configure your OpenAI and Supabase credentials as well.
- Configure Error Trigger:
- The "Error Trigger" node is the starting point. This workflow is designed to be triggered by other workflows that fail.
- In any workflow you want to monitor, go to the workflow settings (the gear icon in the top right).
- Under "Error Workflow", select this workflow from the dropdown list.
- Customize Logic (Optional):
- The "If" node (ID: 20) currently has no conditions configured. You will need to define the conditions under which Telegram notifications and Google Drive logging should occur. For example, you might want to filter errors based on the error message, workflow name, or severity.
- The "Edit Fields (Set)" node (ID: 38) can be used to transform or enrich the error data before sending it to other services.
- The "Loop Over Items (Split in Batches)" node (ID: 39) is currently disconnected but could be used to process multiple error items if the error trigger outputs them in batches.
- The "Wait" node (ID: 514) is also disconnected but can be reconnected to introduce delays.
- The AI/Langchain nodes (Embeddings OpenAI, Recursive Character Text Splitter, Supabase Vector Store, OpenAI, Default Data Loader) are included as a framework for advanced error analysis but are currently disconnected. You can connect and configure them to perform tasks like summarizing error logs, suggesting solutions, or categorizing errors using AI.
- The "HTTP Request" node (ID: 19) is a placeholder for sending data to other APIs. You can configure it to integrate with your specific monitoring or incident management tools.
- Activate the Workflow:
- Once configured, activate the workflow by toggling the switch in the top right corner.
Now, whenever an n8n workflow configured to use this error workflow fails, this workflow will execute, sending notifications and logging details as per your configuration.
Related Templates
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
By Wessel BulteAI 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
By Shadrack🎓 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.
By Davide