These messages, which include attendee information, such as names, etc., can be set up for ticket sales, revenues, and attendee check-ins. They can also be set up for specific ticket types.

You can use this integration to receive milestone notifications, for example, on every 100th sale, a certain amount of revenue earned, attendees checked in, and their venue presence.

Note – this integration can neither read nor reply to chat messages.

Setting Up Google Chat Notification

In your Google Chat, account:

1. Open the Space to which you want to add a notification.
2. Next to the Space title, click the expand more arrow, and then click Apps & integrations.
3. Click add Add webhooks.
4. In the Name field, enter Ticketing.events.
5. In the Avatar URL field, enter https://ticketing.events/images/meta/meta-logo.png.
6. Click Save.
7. Copy the webhook URL, by clicking the More button.

Back to your Ticketing.events account, go to the Integrations page, i.e., Integrations > Google Chat.

Click on the Settings button.

On the sheet on the new page, enter a title, e.g. the name of the chat space, then paste the URL that you copied.

After that, click on the Submit button to save the changes.

You can repeat the same steps above to set up more notifications for other spaces.

Triggering Notifications

Notification Types

From the Google Chat Settings page, there are four types of notifications that can be set up.

Sales Notifications

With the Sales notifications, chat messages will be posted whenever a ticket is sold or when a regular milestone is reached, for example, on every 50 tickets sold.

To set it up, first, choose the event from the Events dropdown, then choose Sales under the Notification Type dropdown.

After that, choose the ticket you want to receive notifications for, then select the frequency or type and enter your own value. For every ticket sale, you can type and enter “1”.

Check the Enable Notification checkbox, then choose the Google Chat space that should receive the chat notification messages.

Revenue Notifications

With the Revenue notifications, chat messages will be posted whenever a ticket’s revenue earned reaches a regular amount, for example, on every $200 earned.

To set it up, first, choose the event from the Events dropdown, then choose Revenue under the Notification Type dropdown.

After that, choose the ticket you want to receive notifications for, then select the frequency or type and enter your own value. For every ticket revenue earned, you can type and enter “1”.

Check the Enable Notification checkbox, then choose the Google Chat space that should receive the chat notification messages.

Attendee Check-in Notifications

With the Attendee Check-in notifications, chat messages will be posted whenever an attendee’s ticket is validated (checked-in). You can set it up for each ticket validation, or for a regular milestone, e.g., for every 30 check-ins made.

To set it up, first, choose the event from the Events dropdown, then choose Check-ins under the Notification Type dropdown.

After that, choose the ticket you want to receive notifications for, then select the frequency or type and enter your own value. For every check-in, you can type and enter “1”.

Check the Enable Notification checkbox, then choose the Google Chat space that should receive the chat notification messages.

Venue Presence Notifications

With the Venue Presence notifications, chat messages will be sent whenever an attendee’s ticket is validated for movements. You can set it up for either those exiting a venue or for those returning to it.

To set it up, first, choose the event from the Events dropdown, then choose Movement under the Notification Type dropdown.

After that, choose the ticket you want to receive notifications for, then select the movement direction.

Check the Enable Notification checkbox, then choose the Google Chat space that should receive the chat notification messages.

The post Google Chat Notifications appeared first on Ticketing.events.

These messages, which include attendee information, such as names, etc., can be set up for ticket sales, revenues, and attendee check-ins. They can also be set up for specific ticket types.

You can use this integration to receive milestone notifications, for example, on every 10th sale, a certain amount of revenue earned, attendees checked in, and their venue presence.

Note – this integration can neither read nor reply to chat messages.

Setting Up Microsoft Teams Notification

In your MS Teams app, open the channel in which you want to add the webhook and select ••• from the upper-right corner, then select Connectors from the options.

Search for Incoming Webhook and select Add.

Go back to Incoming Webhook then click on Configure.

In the field that asks for a name, enter Ticketing.events.

Replace the default image with the one below.

Click on Create.

Copy and note down the unique webhook URL present in the dialog.

Click on Done, to exit the configuration settings.

Back to your Ticketing.events account, go to the Integrations page, i.e., Integrations > Microsoft Teams.

Click on the Settings button.

On the sheet on the new page, enter a title, e.g. the name of the Teams channel, then paste the URL that you copied.

After that, click on the Submit button to save the changes.

You can repeat the same steps above to set up more notifications for other Teams channels.

Triggering Notifications

Notification Types

From the Microsoft Teams Settings page, there are four types of notifications that can be set up.

Sales Notifications

With the Sales notifications, chat messages will be posted whenever a ticket is sold or when a regular milestone is reached, for example, on every 50 tickets sold.

To set it up, first, choose the event from the Events dropdown, then choose Sales under the Notification Type dropdown.

After that, choose the ticket you want to receive notifications for, then select the frequency or type and enter your own value. For every ticket sale, you can enter “1”.

Check the Enable Notification checkbox, then choose the Teams channel that should receive the chat notification messages.

Revenue Notifications

With the Revenue notifications, chat messages will be posted whenever a ticket’s revenue earned reaches a regular amount, for example, on every $200 earned.

To set it up, first, choose the event from the Events dropdown, then choose Revenue under the Notification Type dropdown.

After that, choose the ticket you want to receive notifications for, then select the frequency or type and enter your own value. For every ticket revenue earned, you can enter “1”.

Check the Enable Notification checkbox, then choose the Teams channel that should receive the chat notification messages.

Attendee Check-in Notifications

With the Attendee Check-in notifications, chat messages will be posted whenever an attendee’s ticket is validated (checked-in). You can set it up for each ticket validation, or for a regular milestone, e.g., for every 30 check-ins made.

To set it up, first, choose the event from the Events dropdown, then choose Check-ins under the Notification Type dropdown.

After that, choose the ticket you want to receive notifications for, then select the frequency or type and enter your own value. For every check-in, you can enter “1”.

Check the Enable Notification checkbox, then choose the Teams channel that should receive the chat notification messages.

Venue Presence Notifications

With the Venue Presence notifications, chat messages will be sent whenever an attendee’s ticket is validated for movements. You can set it up for either those exiting a venue or for those returning to it.

To set it up, first, choose the event from the Events dropdown, then choose Movement under the Notification Type dropdown.

After that, choose the ticket you want to receive notifications for, then select the movement direction.

Check the Enable Notification checkbox, then choose the Teams channel that should receive the chat notification messages.

The post Microsoft Teams Notifications appeared first on Ticketing.events.

You would need a URL that can receive HTTP POST requests. The server receiving these requests can then perform other tasks with the data, such as sending emails, notifying other apps, etc.

With the webhook notifications, you can receive notifications for tickets sold, revenues earned, check-ins, and movements tracked.

Depending on the notification type and frequency, posted data may include attendee details such as first name, last name, email address, and any other custom data.

Setting up Webhook Notifications

From the Integrations page, go to the Webhook Notifications section.

Click on the Settings button.

Notification Types

From the Settings page, there are four types of notifications that can be set up.

Sales Notifications

With the Sales notifications, HTTP POST requests will be sent whenever a ticket is sold or when a regular milestone is reached, for example, on every 50 tickets sold.

To set it up, first, choose the event from the Events dropdown, then choose Sales under the Notification Type dropdown.

After that, choose the ticket you want to receive notifications for, then select the frequency or type and enter your own value. For every ticket sale, you can type and enter “1”.

Check the Enable Notification checkbox, then enter the URL where the POST requests should be sent.

Revenue Notifications

With the Revenue notifications, HTTP POST requests will be sent whenever a ticket’s revenue earned reaches a regular amount, for example, on every $200 earned.

To set it up, first, choose the event from the Events dropdown, then choose Revenue under the Notification Type dropdown.

After that, choose the ticket you want to receive notifications for, then select the frequency or type and enter your own value. For every ticket revenue earned, you can type and enter “1”.

Check the Enable Notification checkbox, then enter the URL where the POST requests should be sent.

Attendee Check-in Notifications

With the Attendee Check-in notifications, HTTP POST requests will be sent whenever an attendee’s ticket is validated (checked-in). You can set it up for each ticket validation, or for a regular milestone, e.g., for every 30 check-ins made.

To set it up, first, choose the event from the Events dropdown, then choose Check-ins under the Notification Type dropdown.

After that, choose the ticket you want to receive notifications for, then select the frequency or type and enter your own value. For every check-in, you can type and enter “1”.

Check the Enable Notification checkbox, then enter the URL where the POST requests should be sent.

Attendee Movement Notifications

With the Attendee Movement notifications, HTTP POST requests will be sent whenever an attendee’s ticket is validated for movements. You can set it up for either those exiting a venue or for those returning to it.

To set it up, first, choose the event from the Events dropdown, then choose Movement under the Notification Type dropdown.

After that, choose the ticket you want to receive notifications for, then select the movement direction.

Check the Enable Notification checkbox, then enter the URL where the POST requests should be sent.

The post Webhook Notifications appeared first on Ticketing.events.

You can receive notifications for ticket sales, revenues earned, or checked-in attendees.

These notifications are specific to a user’s browser, therefore each user who is interested in receiving them would need to set up his/her own notification.

These push notifications, on desktops, are supported on Chrome, Firefox, Opera, and Edge browsers. On mobile devices, only Android OS supports them at this time.

The notifications will only be displayed on the last device that they were enabled on.

Setting up Push Notifications

From the Integrations page, go to the Push Notifications section.

Click on the Enable Notification button, then follow the browser prompts to grant the access permissions.

Once that’s done, click on the Settings button.

Notification Types

From the Settings page, there are three types of notifications that can be set up.

Sales Notifications

These notifications will be displayed whenever a ticket is sold or when a regular milestone is reached, for example, on every 50 tickets sold.

To set it up, first, choose the event from the Events dropdown, then choose Sales under the Notification Type dropdown.

After that, choose the ticket you want to receive notifications for, then select the frequency or type and enter your own value.

Check the Enable Notification checkbox, then choose where the notifications should be displayed, e.g on mobile devices, desktops, or both.

Revenue Notifications

These notifications will be displayed whenever a ticket’s revenue earned reaches a regular amount, for example, on every $200 earned.

To set it up, first, choose the event from the Events dropdown, then choose Revenue under the Notification Type dropdown.

After that, choose the ticket you want to receive notifications for, then select the frequency or type and enter your own value.

Check the Enable Notification checkbox, then choose which devices should receive the notifications.

Attendee Check-in Notifications

These notifications will be displayed whenever an attendee’s ticket is validated (checked-in). You can set it up for each ticket validation, or for a regular milestone, e.g, for every 20 check-ins made.

To set it up, first, choose the event from the Events dropdown, then choose to Check-ins under the Notification Type dropdown.

After that, choose the ticket you want to receive notifications for, then select the frequency or type and enter your own value.

Check the Enable Notification checkbox, then choose which devices should receive the notifications.

Mobile Notifications

To set up mobile notifications, at the top of the page, click on the Mobile Notifications button.

Scan the QR code that will be displayed. The QR code will take you to a mobile page that you can then enable the notification on.

The post Push Notifications appeared first on Ticketing.events.

Data in the trigger includes the ticket details, check-in time, attendee’s name, email address, and any custom fields data you have set up to be filled out by them.

Once the trigger has been executed, a Zapier action can be started to automate the use of the triggered data. For example, data can be added to a Google Sheet, a MailChimp list, etc.

Setting up the Zap trigger

To set the New Check-in Zap trigger up, in your Zap editor, select the “New Ticket Sales in Ticketing.events”.

After that choose the account to authenticate with, then click on Continue.

Continue to the Find Data step. On there click on the Test & Review button. Zapier will attempt to retrieve sample data from your account that matches the event.

You may, therefore, need to set up sample data within your account, if nothing was found. Simply validate an attendee’s ticket.

If Zapier finds data, you will be presented with samples to choose from.

Setting up a Zap action

At this point, you would have reached the end of the trigger setup. You now need to set up an Action i.e what should happen when the zap is triggered.

The action can be anything useful that you want. In this guide, we’ll set up an action that automatically creates a new spreadsheet row in a Google Sheet.

Click on the (+) button to add an action.

Search and choose Google Sheets. Thereafter, choose “Create Spreadsheet Row” as the Event Action.

Click on Continue, then choose the Google account to authenticate with.

On the  Customize Spreadsheet Row step, choose and enter the relevant details.

Map data from the trigger by clicking on the button at the end of the fields.

Once the customization is complete, continue to the next step to test the zap.

After the test is successful, you can turn the Zaps on or create further actions that meet your needs.

The post New Check-in Trigger appeared first on Ticketing.events.

Data in the trigger includes the ticket details, transaction details, attendee’s name, email address, and any custom fields data you have set up to be filled out by them.

Once the trigger has been executed, a Zapier action can be started to automate the use of the triggered data. For example, data can be added to a Google Sheet, a MailChimp list, etc.

Setting up the Zap trigger

To set the New Ticket Sales Zap trigger up, in your Zap editor, select the “New Ticket Sales in Ticketing.events”.

After that choose the account to authenticate with, then click on Continue.

Continue to the Find Data step. On there click on the Test & Review button. Zapier will attempt to retrieve sample data from your account that matches the event.

You may, therefore, need to set up sample data within your account, if nothing was found. Simply allocate a ticket to an attendee.

If Zapier finds data, you will be presented with samples to choose from.

Setting up a Zap action

At this point, you would have reached the end of the trigger setup. You now need to set up an Action i.e what should happen when the zap is triggered.

The action can be anything useful that you want. In this guide, we’ll set up an action that automatically creates a new spreadsheet row in a Google Sheet.

Click on the (+) button to add an action.

Search and choose Google Sheets. Thereafter, choose “Create Spreadsheet Row” as the Event Action.

Click on Continue, then choose the Google account to authenticate with.

On the  Customize Spreadsheet Row step, choose and enter the relevant details.

Map data from the trigger by clicking on the button at the end of the fields.

Once the customization is complete, continue to the next step to test the zap.

After the test is successful, you can turn the Zaps on or create further actions that meet your needs.

The post New Ticket Sales Trigger appeared first on Ticketing.events.

Data in the trigger includes the attendee’s name, email address, and any custom fields data you have set up to be filled out by them.

Once the trigger has been executed, a Zapier action can be started to automate the use of the triggered data. For example, data can be added to a Google Sheet, a MailChimp list, etc.

Setting up the Zap trigger

To set the New Attendee Zap trigger up, in your Zap editor, select the “New Attendee in Ticketing.events”.

After that choose the account to authenticate with, then click on Continue.

Continue to the Find Data step. On there click on the Test & Review button. Zapier will attempt to retrieve sample data from your account that matches the event.

You may, therefore, need to set up sample data within your account, if nothing was found. Simply create an attendee.

If Zapier finds data, you will be presented with samples to choose from.

Setting up a Zap action

At this point, you would have reached the end of the trigger setup. You now need to set up an Action i.e what should happen when the zap is triggered.

The action can be anything useful that you want. In this guide, we’ll set up an action that automatically creates a new spreadsheet row in a Google Sheet.

Click on the (+) button to add an action.

Search and choose Google Sheets. Thereafter, choose “Create Spreadsheet Row” as the Event Action.

Click on Continue, then choose the Google account to authenticate with.

On the  Customize Spreadsheet Row step, choose and enter the relevant details.

Map data from the trigger by clicking on the button at the end of the fields.

Once the customization is complete, continue to the next step to test the zap.

After the test is successful, you can turn the Zaps on or create further actions that meet your needs.

The post New Attendee Triggers appeared first on Ticketing.events.