After the show is not you at 1 a.m.

After the show is not you at 1 a.m. with a wet pass and a thumb on a broadcast. Thank-you, join path, merch nudge — that onboarding belongs in a human-gated n8n rail, not in load-out.

The house still has to exist. This spoke is the follow-up after people already found the URL. The money frame is Linktree is a leak — build the house. The door is /artists.

The leak

The default path is:

Set ends → you remember the list at the venue → you type a thank-you in the van → you paste last month’s invite → you post merch in the server because someone asked → you get it wrong, or you get it to twelve people, or you get it to a room that did not opt in.

They scanned something. You were carrying amps. You kept a half-sent note.

The fix is:

Set ends → capture you already built (QR, SMS, ticket email, list at merch) → n8n holds the sends → a human says yes on the classes that can burn you → thank-you, join, merch land when you are asleep.

I will not invent an open rate or a merch lift for that sequence. I will tell you what the rail is allowed to do.

The short answer

• Write the three sends before the date: thank-you, join path, merch nudge. If you cannot write them sober, do not automate them.
• Capture at the show on a URL you own. The house is the form. The van is not the CRM.
• Run it in n8n. Gate money, public posts, and anything brand-sensitive. Internal tags can fire. Broadcasts wait.
• Brand-sensitive acts: do not spray the server without a yes. A moderator is not a firewall.
• Start with the $500 Automation Audit. Map the night. Go or no-go. Quote the rail. Do not buy a canvas because a plugin said “automation.”

What the rail actually sends

Three jobs. Not a newsletter empire.

Thank-you. You were in the room. Here is the set or the night in one sentence. Here is the next date if it is real. Here is one place to stay on the list. No novel. No fake “sold out” language.

Join path. The house URL that puts them in the room you chose — Discord, Skool, Circle, or a paid member flow. The invite in the email should still work in the morning. If the room is paid, the checkout is on the house, not a hope they find a pin. Keep Discord if people live there. Do not make the rail a migration speech.

Merch nudge. One item or one shop URL they can finish on a phone. If the SKU is not ready, do not send the nudge. A dead product link after a good night is how you teach them to ignore you.

$UICIDEBOY$, The Wrecks, KYLE, Neon Trees are destinations. I will not hang a post-show conversion story on those names. You can keep Bandcamp or Shopify. The workflow links to the register you already trust.

Human-gated, not spray

n8n can fire when a form hits, when a ticket flags “attended,” when a merch QR lands. That is the easy half. The half that keeps you employed is the gate.

Default gate:

• Any email or SMS the fan sees
• Any post into Discord, the list, or a public channel
• Any coupon, refund, or “exclusive” claim
• Anything a brand could screenshot next to your name

Default auto is fine:

• Tag the night in the list
• File the row
• Notify the manager that a batch is waiting
• Draft the three sends from a template you already approved

A usable approval is one click: who gets it, what it says, which night, Approve / Reject, a clock. If nobody clicks, it holds. It does not silent-send because a Wait node expired. Same rule as human-in-the-loop approvals: a decision queue, not a Slack graveyard.

Promote a class to automatic only after you have watched it. First nights stay gated.

Brand-sensitive acts

Some rooms cannot take a blast. Label relationships. Guest lists. A guest who did not want the night public. A Discord that is a fan club, not a marketing list. You already know if that is you.

If the act is brand-sensitive, every server post waits for a yes. A merch nudge to people who opted in at the table is a different class than a @everyone after a support slot. If you cannot name the class, it gates.

After-show is not a dump of the set film to every tool you have. Content rails can wait. The onboarding is thank-you, join, merch. Recap shorts are a different brief, and they still do not spray without a yes.

What I will not automate

I will not wire a bot that DMs everyone who typed “merch.” I will not send from a personal Gmail because the domain is “coming.” I will not invent a list you did not capture. No capture at the show means no rail.

Twenty artist sites already shipped. The follow-up is a workflow with an owner, not a speech.

Creator Site at $3,500 can hold the capture URL. Business Site at $8,000 can hold the register the rail writes to. The sprint is how you see the house. The $500 audit is how you see the night.

Where to start

• Book the $500 Automation Audit — process map, go/no-go, the three sends, where the gate sits.
• No house yet: see the house first. A rail into nowhere is still a leak.
• Door: /artists. Hub: build the house.

Can this just post in Discord for me?

It can draft. It should not spray. Brand-sensitive acts do not post to the server without a yes. If the room is a paid clubhouse, treat a broadcast like email, not like a group chat you own.

Do I need n8n, or will Mailchimp after the gig do?

A list tool can send a campaign you schedule by hand. The point of n8n is the night as a graph: capture, tag, gate, join path, merch, hold on failure. If your only job is one email you will click Send on, say that in the audit. I will not upsell a canvas you will not operate.

What if we do not capture emails at the show?

Then we are not automating onboarding. We are decorating. Put a QR on a URL you own, or a merch-table field that is not a napkin. The audit can start there. The rail cannot.

Will this text everyone who bought a ticket?

Only if the ticket tool gives you a lawful, opted-in path and you want that class. A ticket is not a blanket yes for merch SMS. We write the classes in the audit. Unsure stays gated.