TicketPAY
SchedulingConnect AI agents to TicketPAY, a German event ticketing and event management platform. Agents read events, catalog items, sales, finance, campaign metrics, and accreditation records through an export API that creates and modifies nothing.
What This Integration Enables
TicketPAY is a German event ticketing and event management platform, and this connector wraps its Export API. That is a reporting API and nothing more, which is the most important thing to understand before designing a flow around it. The vendor states plainly that the Export API does not create, cancel or modify events, orders or tickets, and all fifteen operations here are reads. Agents pull events with their times, status, location and shop assignment, ticket shops with address and organizer URL, shop visitor counter statistics, and the products, packages and articles offered in each shop. On the sales side they read orders with buyer details and payment method, individual tickets with holder, barcode value, validity and check-in status, sold merchandise and add-ons, paid donations, and the cancellations and refunds performed in the account. On the finance side they read fees with type, rate and payout status, payment transactions with amount, handle and payout status, and vouchers with balance and usage scope. List Campaigns reads marketing campaign metrics, the clicks, sales and conversion rate behind a tracking link, rather than creating or sending a campaign. List Employees reads accreditation records, the access profile, assigned areas and time ranges and the check-in QR value, rather than issuing or revoking accreditation. Get API Key Info returns the name of the key in use.
There are no triggers. TicketPAY exposes no event subscription through this API, so flows run on a schedule. Every list operation pages with Per Page and Page, and filters either by an explicit From and To range or by a relative Time Period combined with Time Range, applied through Filter By to either the created or the updated timestamp. That last choice is not cosmetic. A settlement figure assembled with Filter By set to updated will include a refund processed today against a sale from last month, and the same figure assembled on created will not. The connector gives an agent every number an event produces. Deciding which window those numbers describe is where a person still belongs.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Post-Event Settlement Pack
The morning after an event, the agent runs List Orders, List Tickets and List Sold Articles for the event, then List Fees, List Transactions and List Cancellations across the identical From and To range. It reconciles gross sales against fees and refunds, groups the result by payout status, and assembles a settlement pack with the window and the Filter By setting stated at the top. Finance receives one document instead of five exports, and every figure in it names the range it came from.
Live Sales and Capacity Read
While a shop is open, the agent runs List Products to read the sales and validity windows on each article, then List Tickets and List Orders on a relative Time Period to see what has actually moved. It reports pace against remaining validity per product and posts the picture to the promoter channel. Shows that are underselling are visible while there is still time to act rather than in the post-event report.
Campaign Attribution Roll-Up
The agent runs List Campaigns to read clicks, sales counts, conversion rate and sales totals per tracking link, then joins those against List Orders on the same event and window to see which buyers actually converted and at what value. The result lands in a reporting view built with Google Sheets or pushed to the CRM with HubSpot. Campaign spend gets judged against orders rather than against clicks alone.
Human-in-Loop Highlight
Nothing this connector does writes to TicketPAY, so the irreversible act sits entirely downstream, and it is a number. A settlement figure assembled from List Orders, List Fees, List Transactions and List Cancellations is only meaningful alongside the window that produced it, and the Export API offers two different windows for the same data: Filter By applied to the created timestamp, or to the updated timestamp. A refund processed this morning against a ticket sold in March lands inside one and outside the other. Once that figure is posted to the ledger and a payout is released against it, correcting it is a journal entry and a conversation, not a rerun. So the agent stages the pack rather than publishing it, and routes to the finance owner: "Settlement for Sommerfest 2026, window 01.07 to 31.07, Filter By created. Gross 184,220.00 EUR across 3,911 orders, fees 9,204.00, cancellations 6,140.00 of which 2,380.00 relate to orders created in June. Switching Filter By to updated moves those 2,380.00 into this window. Post on created, post on updated, or split the June cancellations out?" A person picks the boundary. The agent then posts the figure with the chosen setting recorded beside it, so the next reconciliation starts from a documented decision rather than a guess.
Agent Capabilities
15 actionsEvents
3- List Events Retrieves your TicketPAY events with their name, start/end time, status, location, and shop assignment. Supports filtering by event ID, shop, status, a date range, or a relative time period, and returns paginated results with total, page, and size metadata.
- List Shops Retrieves your ticket shops, where your events are assigned, including name, localized title, address, contact details, and the public organizer URL. Supports filtering by shop ID, a date range, or a relative time period.
- Get Shop Visitors Retrieves visitor counter statistics for your ticket event shops, including today, yesterday, 7-day, 30-day, 90-day, and total visit counts. Optionally filter to a single event's shop.
Catalog
1- List Products Retrieves the articles and packages offered in your event shops, including localized names, prices, VAT, sales and validity windows, visibility, and article grouping. Supports filtering by product ID, event, product type, a date range, or a relative time period.
Sales
5- List Orders Retrieves shop orders with buyer details, amounts, currency, payment method, status, and the public ticket link. Supports filtering by order ID, event, shop, status, buyer email, SSO user ID, a date range, or a relative time period.
- List Tickets Retrieves individual tickets with holder details, ticket name and type, price, barcode/QR value, validity window, check-in and personalization status, seat, and the public ticket link. Supports filtering by order, event, shop, status, ticket number, or buyer email, plus a date range or relative time period.
- List Sold Articles Retrieves sold articles (merchandise and add-ons) with their name, amount, channel, status, and source order/article references. Supports filtering by sold-article ID, order, event, shop, article ID, a date range, or a relative time period.
- List Donations Retrieves paid donations collected through your shops, including donation name, amount, status, and the associated shop, event, and order. Supports filtering by donation ID, order, event, shop, a date range, or a relative time period.
- List Cancellations Retrieves cancellations and refunds performed in your account, including the cancellation type, related ticket or order, action, reason (localized), and who performed it. Supports filtering by cancellation ID, related record, event, a date range, or a relative time period.
Finance
3- List Fees Retrieves fees applied to orders, including fee type and name, amount, quantity, rate, channel, and payout status. Supports filtering by fee ID, order, event, shop, fee type, a date range, or a relative time period.
- List Transactions Retrieves payment transactions with amount, payment handle, channel, reference, transaction type, and payout status. Supports filtering by order, event, shop, status, a date range, or a relative time period.
- List Vouchers Retrieves vouchers with code, PIN, initial and remaining balance, refundable amounts, validity, and usage scope. Supports filtering by order, event, shop, status, a date range, or a relative time period.
Marketing
1- List Campaigns Retrieves marketing campaigns with their name, description, tracking link, click and sales counts, conversion rate, and sales totals (in euro cents). Supports filtering by campaign ID, event, a date range, or a relative time period.
Accreditation
1- List Employees Retrieves accreditation employees with personal details, access profile, assigned areas and time ranges, partner and project references, and check-in QR code value. Available when the accreditation system is in use. Supports filtering by employee ID, email, QR code, project, partner, profile, status, a date range, or a relative time period.
Account
1- Get API Key Info Returns the name of the API key used for the current request. Useful for confirming that a configured key is valid and identifying which key is in use.
Frequently Asked Questions
What can FlowRunner do with TicketPAY?
FlowRunner agents can run List Events, List Shops, and Get Shop Visitors in TicketPAY, plus 12 more actions.
Does connecting TicketPAY to FlowRunner require OAuth?
No. TicketPAY connects to FlowRunner with an API key, no OAuth flow required.
Can TicketPAY trigger a FlowRunner workflow automatically?
TicketPAY doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with TicketPAY
$100 in credits. No card required. Connect in minutes.