Connect PassEngine and Wachete

Both apps 24PassEngine 15Wachete 9

• Trigger
  New Client

  Triggers when a new client is created.

• Trigger
  New Pass

  Triggers when a new pass is created in PassEngine.

• Trigger
  Pass Scanned

  Triggers each time a pass is successfully scanned, with the pass code, scan result, location and the operator who scanned it.

• Trigger
  Pass Status Changed

  Triggers when a pass status changes (active, used, expired, revoked).

• Action
  Activate Pass

  Reactivates a pass, setting its status back to active and notifying wallet apps.

• Action
  Create Client

  Creates a client (customer) in PassEngine with a name and optional email, phone and internal notes.

• Action
  Create Pass

  Creates a new single-use or multi-use pass, optionally attached to a client and emailed to a recipient. Returns the new pass with its code and public link.

• Action
  Get client

  Returns a single client (customer) by ID, including their name, email, phone and notes.

• Action
  Get pass

  Returns a pass by its ID, including its custom fields, attached client, recent email deliveries and public URL.

• Action
  List clients

  Returns the clients in your PassEngine account, optionally filtered by name, email or phone.

• Action
  List passes

  Returns the passes in your PassEngine account, optionally filtered by name/code text or status.

• Action
  Revoke Pass

  Revokes a pass so it can no longer be scanned, and notifies wallet apps of the change.

• Action
  Scan Pass

  Scans (redeems) a pass by its code, validating its status, validity dates and usage limits, and records the scan. Returns whether the scan succeeded and, if not, why.

• Action
  Send pass email

  Emails an existing pass to a recipient. Returns the queued email delivery with its status.

• Action
  Update Pass

  Updates an existing pass's label, note, status, scan limit, validity dates or custom fields. Changing the status notifies subscribers that the pass status changed.

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