Connect Pipefile and Wachete

Both apps 20Pipefile 11Wachete 9

• Trigger
  File Request Created

  Triggers when a file request is created.

• Action
  Add File Request From Template

  Create a new file request from an existing template for one recipient (name/email/phone), optionally on behalf of a team member via X-Pipefile-On-Behalf-Of.

• Action
  Create Contact

  Add to contacts

• Action
  Delete Contact

  Delete a contact by id. Returns 204 No Content on success.

• Action
  Get Contact

  Retrieve one contact by id.

• Action
  Get File Request

  Retrieve detailed information about one file request by id, including contents, items, files, and tracking events.

• Action
  List Contacts

  Retrieve a paginated list of contacts, filterable by name/email/phone partial match.

• Action
  List File Request Templates

  Retrieve the list of file request templates available for creating new file requests, with optional name search.

• Action
  Search File Requests

  Finds all file requests matching this search query (contact name, email, tags, etc).

• Action
  Send Request

  Create and send a new request

• Action
  Update Contact

  Update name/email/phone of an existing contact by id.

• 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.

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