Skip to content


Subscriptions are a powerful tool in QReserve to schedule automated repetitive tasks such as creating reservations, recording credentials, sending invoices, or running reports.

Subscriptions Overview

A subscription is like a recipe that is performed on a regular basis automatically by the QReserve platform. Each subscription has the following components:

  • A name for the subscription that will appear to end users.
  • A user whom the subscription is run for.
  • A reoccurrence schedule (e.g. the 1st of each month, every Monday, etc.)
  • A time of day to approximately run the subscription.
  • An active or paused status (or a template status to easily generate new subscriptions).
  • One or more tasks that the subscription should execute each time it runs.

Each subscription task may or may not generate output that can flow into subsequent tasks. For example, a reservation task can create a reservation as output that can flow into an invoice task to automatically schedule the reservation and then generate an invoice.

Tasks can further be chained together so you could generate 5 reservations that all flow into a final invoice task to create a single invoice with those five reservations as line items!

Creating Subscriptions

Subscriptions can be created from the Workflows page in Administration and can only be edited or activated by site moderators or administrators at this time. Users will have access to a read-only summary of any subscriptions created on their behalf.

Subscription Tasks

Refer to Workflow Tasks.

Subscription Notifications

Subscriptions can be a powerful tool to generate monthly subscription invoices, parking reservations, or recurring access credentials. With invoice tasks, credit card payment processing integrations, and stored cards on file, you can even automatically invoice and charge a credit cards! These tasks may not always succeed if, for example, a reservation is blocked due to a conflict or a payment attempt fails due to an expired credit card or invalid payment method.

To keep you informed, each subscription can have a succeeded and/or a failed notifications email address (or multiple). Each day, a summary email with all subscriptions will be sent with a list of succeeded and failed workflows. This allows you to easily spot problem subscriptions and remedy them manually.