Connect Contractbook and Wachete

Both apps 17Contractbook 8Wachete 9

• Trigger
  Draft Edited

  Triggers when a draft document in Contractbook is edited.

• Trigger
  New Draft

  Triggers when a new draft document is created in Contractbook.

• Trigger
  New Template

  Triggers when a new template is added to your Contractbook account.

• Action
  Create Contract

  Creates a new contract document in Contractbook from one of your templates, optionally overriding its title, parties, data fields and other settings.

• Action
  Create Contract With Custom Parties

  Creates a new contract from a Contractbook template, with the parties and signees you specify.

• Action
  Create Draft

  Creates a new draft document from a Contractbook template, without sending it for signature.

• Action
  Create Draft With Custom Parties

  Creates a draft document from a template with the parties and signees you specify, without sending it for signature.

• Action
  Get Document

  Returns a Contractbook document (draft or contract) by its ID, including its parties, signees, data fields, state and events.

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