Shops

Native Integration for Ticketing Shops

Explore how we helped a ticketing platform provide their customers with an easy way to set up automations by building a Make app and making it available as a native integration.

What’s a Rich Text element?

The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.

Static and dynamic content editing

A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!

How to customize formatting for each rich text

Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.

Food Delivery
  • Benutzerkonten erstellen;
Du kannst deinen Workflow auch über eine API mit Zapier und Make erstellen - wenn du Hilfe benötigst, beraten wir gerne.

#FFF7F1

Native Integration for Ticketing Shops

What’s a Rich Text element?

The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.

Static and dynamic content editing

A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!

How to customize formatting for each rich text

Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.

Food Delivery
  • Benutzerkonten erstellen;
Du kannst deinen Workflow auch über eine API mit Zapier und Make erstellen - wenn du Hilfe benötigst, beraten wir gerne.

#FFF7F1

Even with Make’s extensive array of apps and integrations, you might find yourself using a platform that isn’t supported (yet). This was the case for our client, TicketPAY, an all-in-one ticket shop solution for event organizers of any size. TicketPAY’s platform supports various event types, including concerts, festivals, and trade fairs, offering features such as the management of ticket packages, payments, guest lists, seating plans, pre-orders, and more. As Make Gold Partners, we stepped in to leverage our app-building expertise to fill in the gaps.

Automations for Ticket Shops

TicketPAY approached us at 0hands to provide their customers with a simple way of creating their own automations. This functionality would offer numerous benefits, such as migrating information from TicketPAY to a different platform. It would also be helpful, for instance, if a customer buys a festival ticket without purchasing additional tickets for parking or camping. An automation could then send a follow-up email a few days before the festival, reminding them to buy these additional tickets.

Building a Make App

To assist our client in achieving their goal, we were tasked with developing a Make app for their platform using their API. From their API documentation, we identified seven GET endpoints that needed to be included in the app. Authentication should take place via API key and query parameters should be accepted.

Once we connected all endpoints and the app was built, we also supervised the certification process through Make. This process ensured that the app was made available as a native integration within Make. TicketPAY’s customers could then seamlessly create their own automations using the Make platform, and therefore manage their ticketing operations more easily.

Consultation with 0hands

As questions emerged, we provided ongoing consultation to our client. They inquired about the general differences between watcher modules and list modules. We explained the benefits of each and ultimately concluded that watcher modules fit their needs best, as they proved to be more efficient, saving operations in the long run. Consequently, the client opted to implement watcher modules for all endpoints.

A list module that lists events.
Example of a list module
A watcher module that watches orders.
Example of a watcher module

We engaged in further conversations to determine the specific values for certain parameters, enabling us to incorporate drop-down menus in the watcher modules. Additionally, the client needed to modify their API and create an endpoint that would transfer relevant customer metadata. This adjustment allowed the connection in Make to display the user’s name, making the allocation of information easier.

Make connection displaying the metadata 'wemakefuture'.
Make connection displaying metadata

Finally, we provided general consulting on the Make platform and its individual features, as well. As Make Gold Partners, we were able to offer in-depth information and expert insights into the automation platform.

Enhancing Ticketing with Make

As a result, we successfully built a Make app for TicketPAY and oversaw its certification. After minor adjustments to their API, the app was made available as a fully functional native integration in Make. This allowed TicketPAY’s customers to use this integration to create customized automated scenarios, simplifying tasks such as booking tickets, sending follow-up emails for events, managing payments, and more.

We also provided our client with valuable consultation, helping them find the right solutions for their needs and sharing our expertise on the Make platform.

Ready to have your app built or need more information about Make? Contact us at any time for a free consultation!