Zapier

Usetix for Zapier provides sixteen instant triggers, event and order searches, and six actions. It uses the same API and account permissions as the Usetix dashboard.

Version 1.0.2 is available through an installation invitation. The integration is private and has not been approved for Zapier’s public directory.

Add Usetix and connect

1. Open the Usetix invitation and sign in to Zapier.
2. Accept the invitation to use Usetix 1.0.2.
3. Create a Zap and select Usetix for a trigger, search or action.
4. Add a connection, sign in to Usetix and choose the account the Zap should use.
5. Approve access and check the account name shown in Zapier.

You do not need an API token or your own OAuth client. A connection belongs to the selected account. Co-organizers can use only their assigned events; account-wide order and voucher access requires an owner or manager.

First Zap

Use Find Event with an existing event to check the account connection. For a workflow that reacts to sales, choose Order Paid as the trigger, select an event if needed and connect your destination app.

Test the mapping, enable the Zap and check Zap History after a real new order. Editor sample data helps map fields; it does not establish that the enabled Zap has received a live notification.

Instant triggers create their own Usetix webhook subscriptions when enabled and remove them when disabled. If you change accounts or replace a trigger, check Settings → Webhooks in Usetix for any old subscription.

Searches and actions

• Find an event or an order.
• Create, update, publish or unpublish an event.
• Add a guest party and create a promo code.

Event and ticket selectors load options from the connected account. Choose the event first, then select tickets or seats when adding guests. Publishing and inventory changes retain the normal Usetix requirements.

Triggers cover paid, refunded and cancelled orders; published and unpublished events; ticket check-in; and voucher lifecycle changes, including voucher purchases.

Repeated deliveries and creates

Usetix can retry a notification. Its id remains stable, and Zapier uses it for trigger deduplication.

When creating an event, guest party or promo code, map a stable source identifier into Unique Request Key. The same key and input return the original result for seven days. A different input with that key returns HTTP 409. Use a new key for a new operation.

Check failed steps in Zap History. Correct invalid fields before replaying the Zap; reconnect when access has been revoked. The API documentation describes fields and permissions.

Disconnect

Turn off Zaps that use the connection before removing it from Zapier. In Usetix, open Settings → Automations to revoke the connection. This invalidates its tokens and stops its webhook subscriptions. Zaps using the revoked connection must reconnect before they can run again.