n8n

The Usetix community node connects a self-hosted n8n instance to your account. It uses the same Admin API and permissions as the dashboard.

Package: n8n-nodes-usetix, version 1.0.1 or later. Source: github.com/gobijan/n8n-nodes-usetix.

n8n Cloud availability requires n8n verification. Automated checks have passed, the demo video has been submitted, and manual review is under way. Self-hosted installation is available now.

Install

On a self-hosted n8n instance:

1. Open Settings → Community Nodes → Install.
2. Enter n8n-nodes-usetix.
3. Restart n8n if it asks you to.

Community nodes must be enabled on that instance. Installing the package does not grant access to an Usetix account until you add a credential.

Connect an account

In Usetix, open Settings → API Tokens and create a token.

Token	Use it for
Read	Event lists, order lookup, and other reads.
Write	Creating or changing events, guest parties, promo codes, and webhook subscriptions.

In n8n, create an Usetix API credential and paste the token. The node calls https://app.usetix.io with that token.

Usetix OAuth2 API is for an n8n instance that already has its own registered Usetix OAuth client. Most organizers should use an API token. Co-organizers use a personal token and can only work with events assigned to them. Account-wide order lookup and voucher notifications need an owner or manager.

You can revoke the token in Usetix at any time. Workflows that still use it will fail on the next request.

Actions

The Usetix node can:

• create, find, list, update, publish, and unpublish events
• find an order by its public ID or order code
• list guest tickets for an event
• add a guest party, including a standing area or specific seats when the event uses them
• create a promo code, including a usage limit and an expiration

Choose an event before choosing ticket types or seats. Usetix reserves the inventory when the guest party is created. A stale seat returns an error you can act on.

For any other Admin API operation, use n8n’s HTTP Request node with the same Usetix API credential. The API docs describe the payloads and permissions.

Triggers

Usetix Trigger subscribes to one or more of these notifications:

• order.paid, order.refunded, order.cancelled
• event.published, event.unpublished
• ticket.redeemed
• voucher.issued, voucher.redeemed, voucher.refunded, voucher.adjusted, voucher.expired, voucher.blocked, voucher.unblocked, voucher.voided
• voucher_purchase.paid, voucher_purchase.refunded

You can limit an event-scoped notification to one event. Keep voucher notifications that are not tied to an event on their own trigger.

Activating the workflow creates the subscription. Deactivating or deleting it removes the subscription. Usetix reads the original signed delivery before the workflow sees any fields, so a forged callback body is discarded.

Retries and repeated creates

Usetix may deliver the same notification more than once. The notification id stays the same across retries. In n8n, use Remove Duplicates on that id, or store it in the system you are updating.

When a following step creates an event, guest party, or promo code, put a stable source id into Unique Request Key. The same key and the same input return the original result for seven days and do not run the action again. A different input, or a token that no longer has permission, returns HTTP 409. Use a new key for a new operation.

Zapier and Make

Zapier and Make use the same Usetix API and notifications. Both are available through installation invitations while their public directory requirements remain open.

Follow the Zapier setup guide or the Make setup guide for the invitation, account connection and first workflow.