Make

Usetix for Make has 27 modules: sixteen instant triggers, ten action, search and list modules, and a universal API module. It uses the same API and account permissions as the Usetix dashboard.

The app is available through an installation invitation. It is not yet approved for Make’s public marketplace.

Install and connect

1. Open the Usetix invitation and sign in to Make.
2. Install the app in the Make organization where you want to build scenarios.
3. Create a scenario, add an Usetix module and create a connection.
4. Sign in to Usetix, select the account the scenario should use and approve access.
5. Check the account name shown on the connection before running the scenario.

You do not need to copy an API token or OAuth client secret. Connect each Usetix account separately. Co-organizers retain their event assignments; account-wide order and voucher access requires an owner or manager.

First scenario

Start with List Events to check the connection without changing an event. Run the scenario once and inspect the returned event names and slugs.

To react to a purchase, use Watch Order Paid as the first module, add the destination module and map the order fields. Enable the scenario and use a real new order from the connected Usetix account. Check the scenario execution history before relying on the workflow.

Instant triggers create their own Usetix webhook subscriptions. Keep each scenario’s connection and webhook together. Removing a trigger should also remove its subscription; check Settings → Webhooks if an old subscription remains.

Available operations

• Create, find, list, update, publish and unpublish events.
• Find an order by public ID or order code.
• List guest tickets, add a guest party and create a promo code.
• React to paid, refunded and cancelled orders; event publication; ticket check-in; and voucher lifecycle changes, including voucher purchases.
• Call the organizer API directly with Make an API call using the same connection.

Choose an event before choosing guest tickets or seats. Publishing retains the normal Usetix requirements. The integration does not bypass inventory, payment or account rules.

Make an API call

Use a relative URL, such as /admin/events, and select GET to read data. Put query parameters in Query String, not in the URL. The module returns Body, Headers and Status code.

For writes, select the documented method, enter a JSON Body, and supply a Unique Request Key when the endpoint supports idempotency. The connection supplies authentication and JSON headers. Full external URLs and redirects are not supported; the module only calls Usetix. See the API documentation for supported paths and fields.

Repeated deliveries and creates

Usetix may deliver the same notification more than once. Its id stays the same across retries. Use a Make Data Store keyed by that id when the destination action cannot safely repeat.

For event, guest-party and promo-code creation, map a stable source identifier into Unique Request Key. The same key with the same input returns the original result for seven days. Reusing a key with different input returns HTTP 409.

Keep errors visible in Make’s execution history. Correct invalid input before retrying; reconnect if access has been revoked. The API documentation describes fields and permissions.

Disconnect

Disable the scenario, then remove the connection in Make when it is no longer needed. In Usetix, open Settings → Automations to revoke the connection. Revocation invalidates its tokens and stops its Usetix webhook subscriptions; the next API request fails until the account is connected again.