loopyah

Start n8n workflows when something happens in Loopyah: new orders, check-ins, contacts, refunds, point-of-sale sales, reviews, sponsor applications and paid payouts.

Package Information

Released: this month
Downloads: 0 weekly / 0 monthly
Latest Version: 0.2.0
Author: Loopyah

Documentation

loopyah-n8n

The Loopyah node for n8n, published to npm as n8n-nodes-loopyah. Loopyah is an event ticketing platform. This package starts n8n workflows when something happens in your Loopyah account.

Installation

On self-hosted n8n, go to Settings > Community Nodes > Install and enter n8n-nodes-loopyah. n8n's community nodes guide has the details.

Credentials

Create a Loopyah OAuth2 API credential and click Connect. Sign in to Loopyah and choose whether n8n can only read your data or read and change it. There's no client ID or secret to copy: n8n registers itself with Loopyah when you connect.

The connection shows on your Loopyah connectors page, and disconnecting it there ends n8n's access.

Loopyah Trigger

Starts a workflow for each new record, across every event you run.

Trigger on Starts when
New Check-In A guest is let in, by a ticket scan or a check-in by hand
New Contact Someone is added to your contacts
New Customer Refund A customer's own refund request is paid back to them
New Order A customer pays for tickets
New Organizer Refund A refund you issued is paid back to a customer
New Point-of-Sale Sale You take an in-person sale with Tap to Pay
New Review A guest reviews one of your events
New Sponsor Application A sponsor applies to one of your events
Payout Paid Loopyah sends a payout to your bank
  • Organizer: leave it empty to use your own account, or pick an organizer whose team you're on. Your team role decides what you can read.
  • First run: a workflow switched on for the first time starts from your newest record and doesn't replay your history. Changing the trigger, the Organizer or the Loopyah account starts fresh the same way.
  • Each check reads up to 100 new records, each starting the workflow once, oldest first. It also looks back an hour behind the newest record it has seen, so a record that shows up late, such as a contact dated by the purchase it came from, still starts the workflow. Fetch Test Event shows your latest record.
  • Errors show Loopyah's own message with its status code.

Loopyah Instant Trigger

Starts a workflow the moment something happens, with the same triggers, Organizer field and record fields as the Loopyah Trigger. Activating the workflow tells Loopyah where to send, and deactivating it tells Loopyah to stop. Nothing is checked on a schedule, so a rush of orders or check-ins is never cut short and a record that shows up late is never missed.

  • Loopyah needs to reach your n8n at a public https address. n8n on your own computer, on localhost or behind a firewall can't receive sends, so use the Loopyah Trigger there.
  • Loopyah signs every send, and the trigger refuses anything Loopyah didn't sign.
  • Listen for Test Event waits for the next real record.

Example workflows

  • Orders to a spreadsheet: Loopyah Trigger on New Order, then Google Sheets, Append Row, mapping the buyer, event and amount.
  • Welcome guests at the door: Loopyah Trigger on New Check-In, then Slack, Send Message to your event channel.
  • Contacts to your CRM: Loopyah Trigger on New Contact, then HubSpot, Create or Update Contact with the email and name.
  • Refund alerts: Loopyah Trigger on New Organizer Refund, then Gmail, Send Email to your finance inbox.

Amounts arrive in cents, such as amountCents: 2500 for 25.00, and times in UTC.

Compatibility

Tested with n8n 2.46.

Resources

Development

n8n needs Node 24 (.nvmrc).

npm install
npm run dev

That builds the package, starts n8n at http://localhost:5678 with the package loaded and rebuilds on every change.

npm test
npm run lint

The API address is API_URL in credentials/LoopyahOAuth2Api.credentials.ts. Publishing is refused unless it's the live API.

Publishing

.github/workflows/publish.yml publishes to npm with a provenance statement on every version tag, and npm run release makes the tag. Nothing is published from a laptop.

Layout

  • credentials/LoopyahOAuth2Api.credentials.ts: sign-in
  • nodes/Loopyah/LoopyahTrigger.node.ts: the trigger, its Organizer list and polling
  • nodes/Loopyah/lists.ts: the nine Loopyah lists, and where each keeps its rows, IDs and times
  • nodes/Loopyah/newRecords.ts: which records are new since the last check
  • test/: tests against the built package, with Loopyah's API faked

License

MIT

Discussion