Connect PassEngine and Pipefile

Both apps 26PassEngine 15Pipefile 11

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

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