# Handle theater ticket bookings with Anthropic: n8n workflow

> Started by another system calling it. It calls services over plain HTTP rather than through connectors. It hands the judgement calls to Claude.

Source: https://millionrounds.com/workflow/handle-theater-ticket-bookings-with-anthropic (Millionrounds; every figure on the page links to its filing or article)

[Automation library](https://millionrounds.com/workflows) · [Customer support](https://millionrounds.com/workflows?category=Customer+support#library)

# Handle theater ticket bookings with Anthropic

Started by another system calling it. It calls services over plain HTTP rather than through connectors. It hands the judgement calls to Claude. 21 steps, 3 loops or waits: large, and worth reading before you trust it with anything live.

Large Calls a model: Claude

[Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fhandle-theater-ticket-bookings-with-anthropic)

**21 steps** Large: read it before trusting it with anything live

**0** Branches: places the flow splits

**3** Loops or waits

**0** Services by connector: it calls them over plain HTTP

## The flow

Starts it 2 Model 4 Logic 11 Service 4

The steps in the order they run, from what starts it.

- 1 **Webhook - Receive Booking Request** Webhook *Starts it*
- 2 **Anthropic - Validation Model** Lm Chat Anthropic *Model*
- 3 **Anthropic - Confirmation Model** Lm Chat Anthropic *Model*
- 4 **Prepare Booking Context** Set *Logic*
- 5 **AI - Validate & Normalize Booking** Agent *Model*
- 6 **AI - Generate Confirmation Message** Agent *Model*
- 7 **JS - Parse Validation Output** Code *Logic*
- 8 **JS - Parse Confirmation Output** Code *Logic*
- 9 **Filter - Valid Bookings Only** Filter *Logic*
- 10 **Wait for API Result** Wait *Logic*
- 11 **Wait - API Rate Limit** Wait *Logic*
- 12 **JS - Format Final Booking Record** Code *Logic*
- 13 **Fetch Seat Map from Google Sheets** Http Request *Service*
- 14 **Save Booking to Google Sheets Tracker** Http Request *Service*
- 15 **Send Confirmation Email** Http Request *Service*
- 16 **Send SMS Notification** Http Request *Service*
- 17 **JS - Check Availability & Assign Seats** Code *Logic*
- 18 **Respond to Webhook** Respond To Webhook *Starts it*
- 19 **Filter - Seats Available** Filter *Logic*
- 20 **JS - Calculate Ticket Pricing** Code *Logic*
- 21 **Wait for API** Wait *Logic*

## How it's built

- **Starts on:** Another system calling it
- **Steps:** 21, 3 loops or waits
- **Size:** Large: read it before trusting it with anything live
- **Connects to:** Nothing by connector; it calls services over plain HTTP
- **Model:** Claude

## Questions

What does it need to run?

An n8n account, and a key for Claude. You connect your own accounts after importing it; none are included.

What starts it?

It starts on another system calling it.

Does it use AI?

Yes. It calls Claude. Model calls are billed by the provider, not by n8n.

How long does it take to set up?

Take your time. At 21 steps it is large: read it before trusting it with anything live.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

**Before you run it**

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 21 steps before you point it at anything that matters.

## Run it in n8n

- **Create your n8n account** Free to start. n8n is where the workflow runs. [Create an n8n account ↗](https://millionrounds.com/n8n)
- **Download the workflow** Free with a Millionrounds account. [Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fhandle-theater-ticket-bookings-with-anthropic)
- **Paste it into n8n** Open a new workflow in n8n and paste. Then connect your own accounts.

Stored with the author's traces removed: canvas notes, instance identifiers, saved credential names and any live document they had left behind.

## Workflows like it

Also customer support, with the same services where possible, closest in size first.

- [**Answer HR and IT policy questions on Telegram with OpenAI** 21 steps · calls a model · Telegram](https://millionrounds.com/workflow/answer-hr-and-it-policy-questions-on-telegram-with-openai)
- [**Automate Service Ticket Triage with OpenAI and Taiga** 21 steps · calls a model](https://millionrounds.com/workflow/automate-service-ticket-triage-with-openai-and-taiga)
- [**Automate multi-channel customer support with Gmail** 21 steps · calls a model · Gmail, Google Sheets](https://millionrounds.com/workflow/automate-multi-channel-customer-support-with-gmail)
- [**Automate support QA reviews with Intercom and OpenAI** 21 steps · calls a model · Google Sheets](https://millionrounds.com/workflow/automate-support-qa-reviews-with-intercom-and-openai)
- [**Automated Slack IT helpdesk with OpenAI and Supabase** 21 steps · calls a model · Slack, Supabase vectors](https://millionrounds.com/workflow/automated-slack-it-helpdesk-with-openai-and-supabase)
- [**Build a Telegram AI assistant with MemMachine and OpenAI** 21 steps · calls a model · Gmail, Google Calendar](https://millionrounds.com/workflow/build-a-telegram-ai-assistant-with-memmachine-and-openai)