Connect PassEngine to Signatureapi

Both apps 30PassEngine 15Signatureapi 15

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

• Action
  Add ceremony

  Creates a new signing ceremony for a recipient. Any previous active ceremony for that recipient is revoked. Returns the ceremony, including its URL when the recipient is authenticated by email code or by your own application.

• Action
  Add deliverable

  Creates an additional deliverable (signed PDF package) from a completed envelope. The envelope must be completed.

• Action
  Add envelope

  Creates an envelope with documents and recipients and starts the signing process.

• Action
  Add upload

  Uploads a PDF, DOCX or PNG file to SignatureAPI and returns a URL you can use as a document source when creating an envelope. Uploads expire after 24 hours.

• Action
  Cancel envelope

  Cancel an in-progress envelope so remaining recipients can no longer sign.

• Action
  Delete envelope

  Delete an envelope.

• Action
  Get deliverable

  Retrieves a deliverable by its ID, including its status and, once generated, a download link for the signed PDF.

• Action
  Get envelope

  Retrieve a single envelope by id.

• Action
  Get recipient

  Retrieves a recipient's details, including status, ceremony information and completion timestamp.

• Action
  Get upload

  Fetches an uploaded file's record by ID: its format, size, hash and expiry. An error occurs if the upload is not found.

• Action
  List deliverables

  Returns the deliverables (signed PDFs with audit log) of an envelope, earliest first.

• Action
  List envelopes

  Lists envelopes in the account, most recent first, optionally filtered by status or topic.

• Action
  Resend request

  Resends the signing request to a recipient who has not yet completed their ceremony, e.g. as a reminder or after a lost or soft-bounced email.

• Action
  Update envelope

  Update mutable fields (e.g. title, metadata) of an existing envelope.

• Action
  Update recipient

  Replaces a recipient who has not yet completed with a new person. The original recipient is marked replaced and a new recipient is created with the same type, key, routing position and places.

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