Last modified July 15, 2020 by John Mcgrath


Qminder logoQminder is a queuing solution for safe, touch-free customer service—greet, inform, and interact with your customers while maintaining safe physical distance. Create Qminder tickets based on user actions within the app and trigger ticket status update messages from Swrve with Swrve’s Qminder integration.

Supported actions

Swrve’s Qminder integration supports the following actions:

Outbound actions

  • Create a new Qminder ticket; for example, add a customer to a queue.

Inbound actions

  • Process ticket status update events from Qminder.

Use cases

Create Ticket

Using the Qminder connector, Swrve triggers the creation of a ticket in Qminder upon receipt of a selected user action that is configured as a mobile event. There are two main steps involved in triggering ticket creation via the Qminder integration:

  1. Create a custom event in the Swrve SDK for the user action that you want to use to trigger the creation of a ticket; for example, create_ticket.
  2. Create a rule in Swrve that is triggered on receipt of the designated event and uses the Create Ticket action to create the ticket.
The Create Ticket action configuration includes mandatory fields, such as the Swrve User ID and Line ID. If the values vary by user and you want to include them as dynamic content when configuring the rule, ensure the values are included as part of the trigger event payload or set up in Swrve as a user property.

Send push notification

The Qminder connector sends ticket status events to Swrve, which you can use to trigger push notifications in Swrve. For example, when a customer’s ticket is called, use the receipt of the Ticket Called event to trigger a rule in Swrve that sends a push notification to a user with pertinent details about their ticket (line number, ticket status, desk number, and so forth).

Qminder configuration

In most instances, your CSM will set up your Qminder configuration, however you might need to provide them with certain credentials. To view your active Swrve integrations, on the Manage menu, select Adaptors.

Step 1: To access the configuration settings, on the Qminder card, select Configure.

Step 2: Complete the following fields as required:

Field Description
API Key Your Qminder API access key

Step 3: To save the configuration settings, select Save.

After you select Save, the configuration status changes to Active and the Deactivate button is available. If you Activate or Deactivate the configuration at any time, the changes apply to both the outbound and inbound actions.

Configuring Qminder actions

This section describes the fields that are included when creating a new rule using the selected action. For certain inbound actions, Swrve automatically creates a rule, while your CSM will likely configure any outbound actions. Most fields have the option to manually enter the value or to select a user property from the list to have Swrve automatically populate the value when the rule is processed.

Create Ticket

Adds a user to a line in Qminder. Complete the following fields to include the values required to create the ticket.

Field Description
Swrve User ID The Swrve User ID of the user to create the ticket for.
Line The Line ID to create the ticket under.
First Name The user’s first name. (Optional)
Last Name The user’s last name. (Optional)
Phone Number The user’s phone number. (Optional)
Email The user’s email address. (Optional)
Source PHONE, MANUAL, or NAME. (Optional)
Extra Attributes Custom fields/values to attach to the ticket. (Optional)
Scheduling Options Send Immediately – the action is performed as soon as the rule is triggered.
Send after – the action is performed after X minutes, hours or days.

Inbound actions

The Qminder inbound actions use webhooks with the Qminder system to receive asynchronous ticket status update events. The webhooks are set up when you activate the Qminder integration. Qminder sends the following events to Swrve:

Event Description
Ticket Called Ticket has been called.
Ticket Cancelled Ticket has been cancelled (removed).
Ticket Changed Ticket has been changed (edited) or a label was added.
Ticket Created Ticket has been created.
Ticket Recalled Ticket has been recalled.
Ticket Served Ticket has been served.