Connect McTime and Wachete

Both apps 26McTime 17Wachete 9

• Trigger
  New Organization

  Triggered when a new organization is created in McTime.

• Action
  Add Assignment

  Adds a user to an organization with a role (or edits an existing assignment when an Assignment ID is given) in McTime.

• Action
  Add User

  Create (or edit, per vendor's add-or-edit semantics) a user.

• Action
  Create Client

  Creates a new client (an organization of type "client") in McTime.

• Action
  Create Organization

  Creates a new organization (project, client, branch, etc.) in McTime.

• Action
  Create Project

  Creates a new project in McTime. Projects are McTime organization units of type "project" that time entries can be booked against.

• Action
  Delete User

  Deletes a McTime user by ID. All of the user's time entries and payroll results are deleted too.

• Action
  Find Client

  Returns up to 50 McTime clients whose name contains the specified text.

• Action
  Find Organization

  Returns up to 50 organizations whose name contains the specified text.

• Action
  Find Project

  Returns up to 50 McTime projects whose name contains the specified text.

• Action
  Get Time Entry

  Retrieve a single McTime time entry by its ID.

• Action
  Get User

  Retrieves a single McTime user by id, including roles, address, export ids and employment details.

• Action
  List Assignments

  Lists a McTime user's assignments to organizations, grouped by role.

• Action
  List Time Entries

  Retrieve time entries within a date range, optionally filtered by user IDs.

• Action
  List Users

  Retrieves the users the authenticated McTime user is allowed to see, optionally filtered by user ids, organization, role and active status. Returns at most 20 users per page.

• Action
  Start Clocking

  Starts a running clock (stopwatch) for a McTime user. One user can have only one running clock at a time.

• Action
  Stop Clocking

  Stops the running McTime clock for a user, turning it into a normal time entry.

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