TicketStacker

Help › API and integrations

Connect TicketStacker to other apps

Use Zapier, Make or n8n to link TicketStacker with Slack, Google Sheets, QuickBooks and thousands of other apps, without writing code.

TicketStacker works with the rest of your tools. The easiest way to connect them is an automation service like Zapier, Make or n8n. They talk to thousands of apps, and they talk to TicketStacker through our webhooks and API.

The TicketStacker app for Zapier (by invitation)

Our Zapier app is in private beta. It adds TicketStacker to Zapier's menus, so you pick your stack and fill in its fields by name instead of pasting addresses:

  • Triggers: New Ticket, Updated Ticket
  • Actions: Create Ticket, Update Ticket, Move Ticket, Move Ticket to Another Stack, Close Ticket, Add Comment, Clone Stack

Email hello@ticketstacker.com for an invite. You connect it with an API token from Settings → API & webhooks.

Without the app: webhooks and the API

The two building blocks below work with Zapier, Make, n8n and anything else that can call a web address. They take about ten minutes to set up.

When something happens in TicketStacker, do something elsewhere

Use a webhook as the trigger.

  1. In your automation tool, start a new automation with its webhook trigger. In Zapier it's Webhooks by Zapier → Catch Hook; in Make it's Webhooks → Custom webhook; in n8n, the Webhook node. Copy the address it gives you.
  2. In TicketStacker, open the stack's editor, pick the step that should trigger it, and add Call a web address (webhook) with that address. Publish changes.
  3. Move a test ticket into that step, so the automation tool sees a sample. Every ticket detail is in it: ticket.title, ticket.key, ticket.fields.cost, ticket.url and more.
  4. Add the action you want.

Ideas:

  • Post in a Slack or Teams channel when a ticket reaches Urgent.
  • Add a row to a Google Sheet when an order is Done, for your bookkeeper.
  • Create an invoice in QuickBooks when a repair closes with a cost.
  • Text the on-call manager when a ticket lands in After hours.

When something happens elsewhere, make or update a ticket

Use the API as the action. In Zapier that's Webhooks by Zapier → POST (or Custom Request); in Make, HTTP → Make a request; in n8n, the HTTP Request node.

  • URL: https://app.ticketstacker.com/api/v1/stacks/{stackId}/tickets
  • Header: Authorization: Bearer ts_your_token (make a token in Settings → API & webhooks)
  • Body (JSON): { "title": "…", "fields": { … } }

Get your stack ID and field keys from GET /stacks (see the API reference).

Ideas:

  • A new booking in your scheduling tool becomes a ticket in Appointments.
  • A form on another website (Typeform, Jotform, Squarespace) files a ticket.
  • A new row in a Google Sheet becomes a ticket. Bringing over a whole sheet at once is easier with an import.
  • An email to a shared inbox with a certain label becomes a ticket (or just give the stack its own email address).

Prefer to write code?

Everything above is plain HTTPS and JSON, so any language works. Start with the API reference and Webhooks.

Tell us what you connect. If there's an app you'd like a ready-made connection for, email hello@ticketstacker.com. It helps us decide what to build first.

Related

Still stuck? Email hello@ticketstacker.com. A real person reads every message.