Project 1

Autonomous Job Search Agent

AI powered job board built with Manus AI, Make.com, Telegram Bot and Google Sheets.

Stack: Manus AI · Make.com · Telegram · Sheets Pattern: async event driven pipeline

Goal

Automate daily search for junior and entry level roles in AI Automation and Agentic AI.

One click in Telegram instead of manual LinkedIn search and copy paste.

Trigger

One click Telegram launch

  • Telegram bot exposes a simple /search command.
  • Command acts as a manual but very light trigger for the whole pipeline.
  • No need to type text or burn Make.com credits on free form input.

This is the only user action. Everything else runs fully autonomous.

Telegram bot /search command trigger

Architecture

Async event driven pipeline

Two Make.com scenarios instead of one long run keep the system robust and avoid timeout issues.

Two Make.com scenarios list

Both scenarios live in the same Make.com organization and run independently.

Flow

  1. Telegram sends /search to Scenario 1.
  2. Scenario 1 calls Manus AI and passes a webhook_url.
  3. Manus runs autonomous web search and reasoning.
  4. When ready, Manus posts results to Scenario 2 webhook.
  5. Scenario 2 writes vacancies into two Google Sheets.

Push model: nothing polls Manus AI. The agent calls back when the work is done.

Scenario 1

Manus_Job_Launcher

  • Telegram Bot module watches updates from the bot.
  • A filter keeps only the /search command.
  • HTTP module calls Manus API endpoint /v2/task.create.
  • Request body includes the system prompt and a webhook_url field.

Scenario finishes fast. Manus continues thinking in the background and calls the webhook later.

Make.com scenario Manus_Job_Launcher

Scenario 2

Manus_Data_Receiver

  • Custom webhook receives a JSON array of vacancies from Manus AI.
  • Router sends each item into Global Remote or Armenia Local branch based on location.
  • Iterator unpacks every vacancy entry.
  • Google Sheets modules add one row per vacancy in each sheet.

Flows run immediately as data arrives. No manual step is needed after the trigger.

Make.com scenario Manus_Data_Receiver

Result

Execution history in Make.com

History confirms that Manus_Data_Receiver is actually triggered by the agent and completes successfully.

Make.com scenario history for Manus_Data_Receiver
  • Each run is triggered by a callback from Manus, not by manual execution.
  • Durations show realistic agent thinking time before data arrives.
  • Green status labels prove the pipeline is stable, not just a static diagram.

Result

Google Sheets job board

Two sheets act as a living job board: Global Remote on the left, Armenia Local on the right.

Global Remote Google Sheet with vacancies
Armenia Local Google Sheet with vacancies
  • Global Remote sheet contains remote junior AI roles across regions.
  • Armenia Local sheet keeps only roles in Armenia that match the junior filters.
  • All rows were created automatically from a single /search command.
1 / 7