Skip to content
FlowHubFluxonLab
HTTP Request
MongoDBfree

Automated Upwork Job Alerts with MongoDB & Slack

by Arturadapted from n8n official workflow galleryUpdated Aug 2026
RequiresHTTP RequestHTTP RequestMongoDBMongoDBSlack
Share Post Share
SeAssign parametersAssign paramete…HRQuery For Upwork Job PostsQuery For Upwor…ScSchedule TriggerIfIf Working HoursFind Existing EntriesFind Existing E…MeOutput New EntriesOutput New Entr…Add New Entries To MongoDBAdd New Entries…Send message in #generalSend message in…12345678
1/5
STEPS · 8
Runs on a schedule

Overview This automated workflow fetches Upwork job postings using Apify, removes duplicate job listings via MongoDB, and sends new job opportunities to Slack. Key Features: Automated job retrieval** from Upwork via Apify API Duplicate filtering** using MongoDB to store only unique jobs Slack notifications** for new job postings Runs every 20 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.

Tags

n8nreference-onlymongo-dbslack
Connects
WHTTP RequestmongodbMongoDBSlack
CategoryMongoDB
Triggermanual
Complexitymedium
Nodes8
AddedFeb 1, 2025

Related workflows

See all MongoDB
Wmongodbuproc
free

Scrape and store data from multiple website pages

This workflow allows extracting data from multiple pages website. The workflow: 1) Starts in a country list at https://www.theswiftcodes.com/browse-by-country/. 2) Loads every country page (https://www.theswiftcodes.com/albania/) 3) Paginates every page in the country page. 4) Extracts data from the country page. 5) Saves data to MongoDB. 6) Paginates through all pages in all countries. It uses getWorkflowStaticData('global') method to recover the next page (saved from the previous page), and it goes ahead with all the pages. There is a first section where the countries list is recovered and extracted. Later, I try to read if a local cache page is available and I recover the cached page from the disk. Finally, I save data to MongoDB, and we paginate all the pages in the country and for all the countries. I have applied a cache system to save a visited page to n8n local disk. If I relaunch workflow, we check if a cache file exists to discard non-required requests to the webpage. If the data present in the website changes, you can apply a Cron node to check the website once per week. Finally, before inserting data in MongoDB, the best way to avoid duplicates is to check that swift_co

by Miquel Colomer
mongodb
free

Insert a document in MongoDB

Companion workflow for MongoDB node docs

by amudhan