Back to Catalog

Automated Upwork job alerts with Airtable & Slack

ArturArtur
196 views
2/3/2026
Official Page

Overview

This automated workflow fetches Upwork job postings using Apify, removes duplicate job listings via Airtable, and sends new job opportunities to Slack.

Key Features:

  • Automated job retrieval from Upwork via Apify API
  • Duplicate filtering using Airtable to store only unique jobs
  • Slack notifications for new job postings
  • Runs every 30 minutes during working hours (9 AM - 5 PM)

This workflow requires an active Apify subscription to function, as it uses the Apify Upwork API to fetch job listings.

Who is This For?

This workflow is ideal for:

  • Freelancers looking to track Upwork jobs in real time
  • Recruiters automating job collection for analytics
  • Developers who want to integrate Upwork job data into their applications

What Problem Does This Solve?

Manually checking Upwork for jobs is time-consuming and inefficient. This workflow:

  • Automates job discovery based on your keywords
  • Filters out duplicate listings, ensuring only new jobs are stored
  • Notifies you on Slack when new jobs appear

How the Workflow Works

1. Schedule Trigger (Every 20 Minutes)

  • Triggers the workflow at 20-minute intervals
  • Ensures job searches are only executed during working hours (9 AM - 5 PM)

2. Query Upwork for Jobs

  • Uses Apify API to scrape Upwork job posts for specific keywords (e.g., "n8n", "Python")

3. Find Existing Jobs in Airtable

  • Searches Airtable to check if a job (based on title and link) already exists

4. Filter Out Duplicate Jobs

  • The Merge Node compares Upwork jobs with Airtable data
  • The IF Node filters out jobs that are already stored in the database

5. Save Only New Jobs in Airtable

  • The Insert Node adds only new job listings to the Airtable collection

6. Send a Slack Notification

  • If a new job is found, a Slack message is sent with job details

Setup Guide

Required API Keys

  • Upwork Scraper (Apify Token) – Get your token from Apify
  • Airtable Credentials
  • Slack API Token – Connect Slack to n8n and set the channel ID (default: #general)

Configuration Steps

  1. Modify search keywords in the 'Assign Parameters' node (startUrls)
  2. Adjust the Working Hours in the 'If Working Hours' node
  3. Set your Slack channel in the Slack node
  4. Ensure Airtable is connected properly - you'll need to create a table with 'title' and 'link' columns.
  5. Adjust the 'If Working Hours' node to match your timezone and hours, or remove it altogether to receive notifications and updates constantly.

How to Customize the Workflow

  • Change keywords: update the startUrls in the 'Assign Parameters' node to track different job categories
  • Change 'If Working Hours': Modify conditions in the IF Node to filter times based on your needs
  • Modify Slack Notifications: Adjust the Slack message format to include additional job details

Why Use This Workflow?

  • Automated job tracking without manual searches
  • Prevents duplicate entries in Airtable
  • Instant Slack notifications for new job opportunities
  • Customizable – adapt the workflow to different job categories

Next Steps

  1. Run the workflow and test with a small set of keywords
  2. Expand job categories for better coverage
  3. Enhance notifications by integrating Telegram, Email, or a dashboard

This workflow ensures real-time job tracking, prevents duplicates, and keeps you updated effortlessly.

Automated Upwork Job Alerts with Airtable & Slack

This n8n workflow automates the process of finding new Upwork jobs based on predefined criteria, storing them in Airtable, and sending notifications to Slack. It helps freelancers and teams stay updated on relevant job postings without manual searching.

What it does

  1. Triggers on a Schedule: The workflow runs periodically (e.g., every hour) to check for new jobs.
  2. Fetches Upwork Search Terms from Airtable: It retrieves a list of search terms (keywords) from a specified Airtable base and table.
  3. Searches Upwork for Jobs: For each search term, it performs an HTTP request to the Upwork API to find relevant jobs.
  4. Filters New Jobs: It checks if the found jobs already exist in a dedicated Airtable "Jobs" table to avoid duplicates.
  5. Adds New Jobs to Airtable: New and unique jobs are added as new records to the Airtable "Jobs" table.
  6. Formats Slack Message: It prepares a formatted message containing details of the new job.
  7. Sends Slack Notification: The formatted job alert is sent to a designated Slack channel.

Prerequisites/Requirements

  • n8n Account/Instance: To run this workflow.
  • Airtable Account:
    • An Airtable Base to store your Upwork search terms.
    • An Airtable Table within that base to store the search terms (e.g., "Search Terms"). This table should have a column for the search keywords.
    • Another Airtable Table (e.g., "Jobs") to store the discovered Upwork jobs, including fields for job title, URL, description, etc.
    • Airtable API Key.
  • Upwork API Access: You'll need to configure the HTTP Request node with the correct Upwork API endpoint and any necessary authentication (e.g., API keys, tokens).
  • Slack Account: A Slack workspace and a channel where you want to receive job alerts. You'll need a Slack Bot Token or Webhook URL.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Airtable: Set up your Airtable credentials with your API key.
    • Upwork (HTTP Request): Configure the "HTTP Request" node with your Upwork API endpoint and authentication details. You will likely need to specify headers for authorization.
    • Slack: Set up your Slack credentials (e.g., Bot Token) or configure a webhook URL for the "Slack" node.
  3. Configure Airtable Nodes:
    • Airtable (Search Terms): Update the "Airtable" node (ID: 2) to point to your Airtable Base and Table containing the Upwork search terms. Specify the column name where your keywords are stored.
    • Airtable (Jobs): Update the "Airtable" node (for adding new jobs) to point to your Airtable Base and Table where new jobs will be stored. Ensure the field mappings are correct (e.g., Job Title, Job URL, Description).
  4. Configure the "Code" Node: This node is likely used for processing the Upwork API response and extracting relevant job data. You may need to adjust the JavaScript code to match the exact structure of the Upwork API response and the fields you want to store in Airtable and send to Slack.
  5. Configure the "If" Node: This node is crucial for filtering out duplicate jobs. It compares new job IDs/URLs with existing ones in your Airtable "Jobs" table. Ensure the comparison logic is correct for your Airtable setup.
  6. Configure the "Slack" Node: Specify the Slack channel where you want the alerts to be posted. Customize the message format if desired.
  7. Activate the Workflow: Once configured, activate the workflow. It will run automatically based on the schedule defined in the "Schedule Trigger" node.

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

Wessel BulteBy Wessel Bulte
247

πŸŽ“ 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.

DavideBy Davide
1616

Tax deadline management & compliance alerts with GPT-4, Google Sheets & Slack

AI-Driven Tax Compliance & Deadline Management System Description Automate tax deadline monitoring with AI-powered insights. This workflow checks your tax calendar daily at 8 AM, uses GPT-4 to analyze upcoming deadlines across multiple jurisdictions, detects overdue and critical items, and sends intelligent alerts via email and Slack only when immediate action is required. Perfect for finance teams and accounting firms who need proactive compliance management without manual tracking. πŸ›οΈπŸ€–πŸ“Š Good to Know AI-Powered: GPT-4 provides risk assessment and strategic recommendations Multi-Jurisdiction: Handles Federal, State, and Local tax requirements automatically Smart Alerts: Only notifies executives when deadlines are overdue or critical (≀3 days) Priority Classification: Categorizes deadlines as Overdue, Critical, High, or Medium priority Dual Notifications: Critical alerts to leadership + daily summaries to team channel Complete Audit Trail: Logs all checks and deadlines to Google Sheets for compliance records How It Works Daily Trigger - Runs at 8:00 AM every morning Fetch Data - Pulls tax calendar and company configuration from Google Sheets Analyze Deadlines - Calculates days remaining, filters by jurisdiction/entity type, categorizes by priority AI Analysis - GPT-4 provides strategic insights and risk assessment on upcoming deadlines Smart Routing - Only sends alerts if overdue or critical deadlines exist Critical Alerts - HTML email to executives + Slack alert for urgent items Team Updates - Slack summary to finance channel with all upcoming deadlines Logging - Records compliance check results to Google Sheets for audit trail Requirements Google Sheets Structure Sheet 1: TaxCalendar DeadlineID | DeadlineName | DeadlineDate | Jurisdiction | Category | AssignedTo | IsActive FED-Q1 | Form 1120 Q1 | 2025-04-15 | Federal | Income | John Doe | TRUE Sheet 2: CompanyConfig (single row) Jurisdictions | EntityType | FiscalYearEnd Federal, California | Corporation | 12-31 Sheet 3: ComplianceLog (auto-populated) Date | AlertLevel | TotalUpcoming | CriticalCount | OverdueCount 2025-01-15 | HIGH | 12 | 3 | 1 Credentials Needed Google Sheets - Service Account OAuth2 OpenAI - API Key (GPT-4 access required) SMTP - Email account for sending alerts Slack - Bot Token with chat:write permission Setup Steps Import workflow JSON into n8n Add all 4 credentials Replace these placeholders: YOURTAXCALENDAR_ID - Tax calendar sheet ID YOURCONFIGID - Company config sheet ID YOURLOGID - Compliance log sheet ID C12345678 - Slack channel ID tax@company.com - Sender email cfo@company.com - Recipient email Share all sheets with Google service account email Invite Slack bot to channels Test workflow manually Activate the trigger Customizing This Workflow Change Alert Thresholds: Edit "Analyze Deadlines" node: Critical: Change <= 3 to <= 5 for 5-day warning High: Change <= 7 to <= 14 for 2-week notice Medium: Change <= 30 to <= 60 for 2-month lookout Adjust Schedule: Edit "Daily Tax Check" trigger: Change hour/minute for different run time Add multiple trigger times for tax season (8 AM, 2 PM, 6 PM) Add More Recipients: Edit "Send Email" node: To: cfo@company.com, director@company.com CC: accounting@company.com BCC: archive@company.com Customize Email Design: Edit "Format Email" node to change colors, add logo, or modify layout Add SMS Alerts: Insert Twilio node after "Is Critical" for emergency notifications Integrate Task Management: Add HTTP Request node to create tasks in Asana/Jira for critical deadlines Troubleshooting | Issue | Solution | |-------|----------| | No deadlines found | Check date format (YYYY-MM-DD) and IsActive = TRUE | | AI analysis failed | Verify OpenAI API key and account credits | | Email not sending | Test SMTP credentials and check if critical condition met | | Slack not posting | Invite bot to channel and verify channel ID format | | Permission denied | Share Google Sheets with service account email | πŸ“ž Professional Services Need help with implementation or customization? Our team offers: 🎯 Custom workflow development 🏒 Enterprise deployment support πŸŽ“ Team training sessions πŸ”§ Ongoing maintenance πŸ“Š Custom reporting & dashboards πŸ”— Additional API integrations Discover more workflows – Get in touch with us

Oneclick AI SquadBy Oneclick AI Squad
93