Connect Wachete to Hero Parser

Both apps 23Wachete 9Hero Parser 14

• Trigger
  Any new notification

  Fires when there is a new change notification from any monitor in your Wachete account.

• Trigger
  New notification for monitor

  Fires when there is a new change notification from the specified Wachete monitor (taskId).

• Action
  Create monitor

  Create a new Wachete monitor (wachet) that watches a web page or part of a page for changes.

• Action
  Delete monitor

  Delete a Wachete monitor by its ID.

• Action
  Get monitor

  Get information about a specific Wachete monitor by its ID.

• Action
  Get monitor data

  Get the captured data/history for a Wachete monitor, optionally as a diff and within a date range.

• Action
  List folders

  List folder contents, optionally under a parent folder.

• Action
  List notifications

  List change notifications, optionally filtered by monitor (taskId) and date range.

• Action
  Update monitor

  Change the settings of an existing Wachete monitor — name, URL, watched/excluded XPath, regex, note, job type, check frequency and location, crawl options, folder, alerts, notification endpoints, headers and proxies. A partial update: the op first reads the monitor's current record, overlays only the fields you filled in, then writes the merged record back, so anything you leave blank keeps its current value — including settings this op does not expose. Identify the monitor by its id. Check frequency is in seconds (86400 = daily) and is ignored if not positive; the true/false options take the words true or false; alerts, notification endpoints, headers and proxies take JSON. Returns the monitor id, name and URL after the update plus the full monitor record.

• Trigger
  New Candidate

  Triggers when a new candidate is created (CV parsed).

• Trigger
  New Recruitment

  Triggers when a new recruitment is created.

• Action
  Create Recruitment

  Create a Recruitment in the system.

• Action
  Delete resumes

  Delete resumes for a recruitment. DELETE /cv/{recruitmentId}

• Action
  Get candidate

  Get candidate details by id. GET /candidate/{candidateId}

• Action
  Get recruitment

  Get recruitment details by id. GET /recruitment/{recruitmentId}

• Action
  List candidates

  Get list of candidates by recruitment. GET /candidate/recruitment/{recruitmentId}/list

• Action
  List recruitments

  Get the recruitments list. GET /recruitment

• Action
  List resumes

  Get list of resumes by recruitment. GET /cv/{recruitmentId}

• Action
  Process resumes

  Process selected resumes for a recruitment (AI parsing). POST /cv/process/{recruitmentId}

• Action
  Send candidate feedback

  Send feedback to selected candidates. POST /candidate/{recruitmentId}/send-feedback

• Action
  Update candidate status

  Change status for selected candidates. POST /candidate/{recruitmentId}/change-status

• Action
  Update recruitment

  Edit an existing recruitment. POST /recruitment/{id}

• Action
  Upload CV

  Upload a CV to existing recruitment.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.