Connect PassEngine to Qstash

Both apps 35PassEngine 15Qstash 20

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

  Create or update a queue (upsert), setting parallelism.

• Action
  Add schedule

  Create a cron-based schedule that periodically publishes a message to a destination.

• Action
  Add URL group endpoint

  Create a URL group or add/update an endpoint within it (fan-out publishing target).

• Action
  Batch publish messages

  Publish multiple messages to multiple destinations in one call.

• Action
  Delete DLQ message

  Remove a message from the dead-letter queue.

• Action
  Delete message

  Cancel a message that has not yet been delivered.

• Action
  Delete queue

  Delete a queue by name.

• Action
  Delete schedule

  Delete a schedule by id.

• Action
  Delete URL group

  Deletes a QStash URL group and all its endpoints. In-flight messages are not removed.

• Action
  Enqueue message

  Add a message to a named queue for sequential delivery.

• Action
  Get DLQ message

  Retrieve a single dead-letter queue message by id.

• Action
  Get message

  Retrieve a queued/published message by id.

• Action
  Get queue

  Retrieve a queue's configuration and stats by name.

• Action
  Get schedule

  Retrieve a schedule by id.

• Action
  Get URL group

  Retrieve a URL group and its endpoints by name.

• Action
  List DLQ messages

  List messages that failed delivery and landed in the dead-letter queue.

• Action
  List queues

  List all queues for the account.

• Action
  Publish message

  Publish a single message to a URL or URL group for QStash to deliver.

• Action
  Retry DLQ message

  Re-attempt delivery of a dead-lettered message now.

• Action
  Update schedule

  Updates an existing QStash schedule by replacing its settings (destination, cron, message and delivery options).

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