Stop hunting for new project posts by hand. This automation checks job listings on a schedule, keeps only the new ones, stores them, and alerts your team in Slack. It fits agencies and freelancers who want to bid fast and avoid duplicate noise.

A schedule runs every 10 minutes and only during work hours. A parameters step holds your search URLs and options. An HTTP request calls a scraper service to fetch fresh listings. Each item is checked in MongoDB by title and budget so repeats are filtered out. Only new items move forward. They are saved to your database for tracking and sent to the Slack general channel with key details like link, budget, skills, and publish time.

You will need an Apify token, a MongoDB connection string, and a Slack app or bot with access to your channel. Add your own search URLs and adjust the work hour rule to match your time zone. Expect faster lead response, less manual checking, and reduced duplicate alerts. Great for small sales teams, agencies, and solo consultants who monitor online job boards for service work.

• Scheduled checks every 10 minutes limited to work hours
• Central parameters step to manage search URLs and options
• HTTP call to a scraper service using a secure token
• MongoDB lookup to detect existing items by title and budget
• Merge step to pass only new listings forward
• Database insert with mapped fields for long term tracking
• Slack message to the general channel with clear job details

• Reduce manual scanning from hours to minutes each day
• Automate up to 90 percent of repetitive lead monitoring
• Cut duplicate Slack alerts by filtering on title and budget
• Handle 10 times more listings without extra effort
• Connect data across Apify, MongoDB, and Slack in one flow

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Apify, MongoDB and Slack. See the Tools Required section above for links to create accounts with these services.
3. Create your Apify token: in your Apify account, open the API page and copy your API token. In n8n, open Credentials > New > HTTP Query Auth. Set the query key to token and paste your Apify token as the value. Save the credential with a clear name like Apify Query Token.
4. Connect Slack: in the n8n credentials manager, create a Slack API credential. Follow the on screen steps to allow access to your workspace and grant permission to post to the target channel.
5. Connect MongoDB: get your connection string from MongoDB Atlas. In n8n, create a MongoDB credential and paste the connection string. Test the connection and save it with a clear name like Atlas Primary.
6. Open the Assign parameters node. Add your search URLs in the startUrls array. Keep the structure with url fields. Set proxyCountryCode if needed.
7. Open the Schedule Trigger node. Confirm the interval is every 10 minutes. Adjust if you want a different check rate.
8. Open the If Working Hours node. Set your time zone and define the work time range when alerts should be sent.
9. Open the HTTP Request node. In Authentication, select your Apify Query Token credential. Confirm the endpoint and POST body fields for startUrls and proxyCountryCode are mapped from the previous step.
10. Open the MongoDB nodes. In Find Existing Entries and Add New Entries to MongoDB, select your Atlas credential and the n8n collection. Confirm the fields title and budget are used for matching.
11. Open the Slack node. Choose your Slack credential. Set the Channel field to #general or another channel your bot can post to. Review the message template fields.
12. Run once during your work hours. Check the execution for returned items, confirm a message appears in Slack, and verify new records are inserted in MongoDB.
13. Run again without changing data to confirm no duplicate messages appear. This validates the duplicate check by title and budget.
14. Troubleshooting: if you see a 401 error on the HTTP Request, recheck the Apify token. If Slack errors with channel not found, add the bot to the channel. If database insert fails, confirm the collection name and permissions in MongoDB Atlas.