Connect PassEngine and Sorry

Both apps 32PassEngine 15Sorry 17

• 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
  New notice

  Triggers when a new notice (incident, maintenance or general announcement) is created on the selected Sorry status page.

• Action
  Add component

  Creates a new component on a Sorry status page, optionally nested under a parent component.

• Action
  Add notice

  Creates a new incident, maintenance or general notice on a Sorry status page, optionally linking affected components and publishing it to subscribers.

• Action
  Add notice update

  Posts a new update on an existing notice on a Sorry status page, optionally publishing it to your configured integrations.

• Action
  Add subscriber

  Adds an email or SMS subscriber to a status page, optionally limited to specific components, so they receive status notices.

• Action
  Delete notice

  Deletes a notice (incident, maintenance or general) from a Sorry status page.

• Action
  Delete subscriber

  Permanently removes a subscriber from a status page.

• Action
  Get notice

  Returns a single notice from a status page, including its type, state, subject, synopsis and link.

• Action
  Get status page

  Returns a single Sorry status page with its name, state, timezone, support details and notification settings, optionally including related brand, components, notices and more.

• Action
  List components

  Returns all components (the services or infrastructure elements) shown on a Sorry status page, with their current state.

• Action
  List notices

  Returns the notices (incidents, maintenance and general notices) posted on a Sorry status page, optionally filtered by type, state, subject or creation date.

• Action
  List notice updates

  Returns all updates posted on a notice on one of your Sorry status pages, optionally filtered by creation date or content.

• Action
  List status pages

  Returns all status pages in your Sorry account, optionally filtered by name or creation date.

• Action
  List subscribers

  Returns the subscribers on a status page, optionally only those who receive notices for a specific component.

• Action
  Update component

  Updates a component on a Sorry status page, such as its name, description, position or parent component.

• Action
  Update notice

  Updates an existing notice on a Sorry status page — change its subject or state, add a comment, set affected components or reschedule planned maintenance.

• Action
  Update status page

  Updates a status page's settings, such as its name, timezone, support contact details, search visibility and language.

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