Usetix
Browse guides

Automate Usetix

Choose the connection that fits the tools you already use. Start with the smallest workflow that removes repeated work.

Built-in AI assistant

Use the assistant inside the admin for conversational work on the current account: create or update events, manage shared tasks, tickets and guest lists, configure consent-gated marketing identifiers, upload event sponsor artwork from the latest chat message, create expiring analytics links, look up orders and customers, prepare reports, or draft account content. It uses the same account rules as the normal admin and asks before critical actions.

For sponsor artwork, attach the image in the conversation and name the event plus the intended layout: one wide banner or up to six individual logos. The assistant never silently reuses an attachment from an older message. It can also inspect, switch, or remove existing sponsor artwork; removal requires confirmation.

For the shared task board, ask the assistant to create tasks, assign people, move cards, add comments or attach files from your latest message. The same task management is available through MCP, the CLI and the Admin API.

Best when one organizer wants to complete work without leaving Usetix.

MCP for ChatGPT, Claude, and other AI clients

Connect an MCP client when you want to use Usetix tools from an external AI workspace. Open Settings → AI Connectors, copy the MCP server URL, add it as a custom connector, and approve the account through OAuth.

MCP connections are account-scoped and revocable. They do not require a manually created API token.

CLI for terminal work and scripts

Use the Usetix CLI when a person, shell script, or coding agent should work with an account from the command line. It provides readable commands for tasks, events and orders, stable machine output, profiles, and direct access to the complete Admin API.

The CLI uses an account API token and is a good fit for support lookups, repeatable bulk work, scheduled shell jobs, and CI pipelines.

Admin API for your own software

Use the authenticated Admin API when your software needs to read or change Usetix records directly. It uses the same /admin/... URLs as the dashboard with Accept: application/json and an account API token.

Create a read token for reporting and a write token only when the integration must make changes.

n8n, Make and Zapier for workflows

Install the community node n8n-nodes-usetix on a self-hosted n8n instance. Connect it with an API token from Settings → API Tokens. The node can manage events, look up orders, add guest parties, create promo codes, and start a workflow from sixteen order, event, check-in, and voucher notifications.

n8n Cloud requires n8n’s approval. Automated checks have passed, the demo video is submitted, and manual review is under way.

Make and Zapier connect through OAuth: sign in to Usetix, choose an account and approve access. Use the installation invitation in each guide while public directory approval is pending. Make has 26 available modules; Zapier provides sixteen instant triggers, event and order searches, and six actions.

Use Settings → Automations in Usetix to review or revoke OAuth connections. n8n API tokens are managed separately under Settings → API Tokens.

Webhooks for real-time reactions

Use webhooks when another system should react to paid, refunded, cancelled, published, or redeemed activity without polling. Verify every signature and make the receiving handler idempotent because deliveries may be retried.

A practical starting point

  • One organizer, occasional task: built-in assistant.
  • Existing ChatGPT or Claude workflow: MCP.
  • Terminal workflow, shell script, or coding agent: CLI.
  • Scheduled import, export, or synchronization: Admin API.
  • A workflow should react or make the change: n8n, Make or Zapier.
  • Immediate downstream reaction in your own receiver: webhook, often combined with the API.

Keep humans in control of publishing, refunds, destructive changes, and broad account settings.