Humanitix

Read Humanitix event ticketing data in agent workflows. Agents list events, pull orders per event for reconciliation and CRM enrichment, build attendee lists from issued tickets, and run incremental syncs with a modified-since filter.

5 actions API key available

Humanitix website ↗ Platform Documentation ↗ Capability data verified 2026-07-27

A nightly schedule starts the ticketing sync for active events

List Events pulls the current event catalog with status and dates

List Orders runs per event with the Modified Since filter set to the last sync time

Get Order expands each new or changed order, including payment and refund status

The agent compares order totals and refund states against the accounting ledger

Any order whose payment status disagrees with the books goes to the finance lead, who decides the correction before anything is adjusted

The clean sync summary and the exception list post to the events channel

What This Integration Enables

Ticketing data has a short shelf life: an attendee list is only useful before the event, a payment discrepancy is only cheap to fix the week it happens, and a buyer is only warm while the event is fresh. The export button cannot keep up with that clock; a scheduled agent can. This connector puts Humanitix's events, orders, and tickets on tap for FlowRunner agents, so the data moves while it still matters instead of waiting for someone to export it. - Sync events, including drafts, into other tools and databases as the catalog changes - Pull orders per event with buyer details, totals, and payment status for reconciliation and CRM enrichment - Build attendee and check-in lists from individual issued tickets, with collected answers included - Run efficient incremental syncs with the Modified Since filter instead of re-reading everything - Keep event, order, and ticket detail on demand for support and exception workflows The registration questions are an underused asset here. Humanitix captures custom answers per order and per ticket, dietary needs, session interests, how-did-you-hear, and this connector carries them through Get Order and List Tickets, so the CRM record and the event-day roster hold the context people typed in, not just their names. The connector reads; the decisions it feeds, ledger corrections, refund follow-ups, attendee communications, are where FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gates apply.

Without FlowRunner

Roster day is export day Attendee lists exist as CSVs downloaded the morning of the event, stale by doors-open

Reconciliation by squint Ticket revenue and the ledger get compared quarterly, if the intern has time

Buyers invisible to the CRM People who paid to attend your event never become contacts anyone follows up with

With FlowRunner

Rosters that update themselves List Tickets feeds a live attendee sheet with check-in status, refreshed on schedule

Incremental sync, nightly Modified Since pulls only what changed, so orders reconcile against the books every night

Every buyer lands in the pipeline Orders flow into the CRM with event, ticket type, and answers to registration questions attached

Use Case Scenarios

Buyers become contacts the night they buy

Every night the agent runs List Orders with Modified Since set to the previous run, expands each result with Get Order, and upserts the buyer into [HubSpot](/integrations/hubspot) tagged with the event name, ticket types, and their answers to the registration questions. Sales and community teams work a list that grew last night, not a CSV from last month. Because the filter is time-based rather than a full re-read, the sync stays cheap at any event size, and re-running it after a failure never duplicates work.

The attendee sheet that is never stale

For each upcoming event from List Events, the agent runs List Tickets and writes attendee name, ticket type, order reference, and check-in status into [Google Sheets](/integrations/google-sheets), replacing the previous snapshot. A [Slack](/integrations/slack) summary posts counts by ticket type and remaining capacity. On event day, the same sweep runs hourly, so the door team's sheet shows check-ins as they happen instead of as they were at breakfast. When the caterer asks for final numbers by ticket type, the answer comes from the sheet, not from someone's phone in the loading dock.

Ticket revenue reconciled while it is still cheap

Finance wants ticket sales tied out weekly. The agent pulls the week's orders per event, sums totals by payment status, and compares against deposits recorded in [QuickBooks Online](/integrations/quickbooks). Matches log silently. Mismatches, a refund in Humanitix with no ledger entry, a payment status that never settled, become a short exception list for the finance lead with the Get Order detail attached, buyer and line items included, so the investigation starts with evidence instead of a search. The tie-out that used to be a quarterly archaeology project becomes a five-minute weekly review, and the trail of resolved exceptions becomes its own audit evidence.

Human-in-Loop Highlight

Get Order surfaces payment and refund status straight from the ticketing source of truth, and the whole value of syncing it is what you do when it disagrees with your books. That correction is the irreversible part: writing off a discrepancy, adjusting a ledger entry, or contacting a buyer about a payment is not something to let a matching heuristic do on its own authority. So the FlowRunner reconciliation agent draws a hard line at the diff. It reads everything, List Orders for the sweep, Get Order for the detail, compares confidently, and then presents each mismatch to the finance lead as a claim with evidence: order ID, buyer, Humanitix status, ledger state. The person picks the correction. The agent's job is to make the exception list short and the evidence complete, not to spend or adjust anything on its own.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

5 actions

Events

List Events Retrieves a paginated list of the organiser account's events, drafts and published, with ID, name, dates, location, and status. The catalog walk that starts most workflows.
Get Event Retrieves one event in full: description, dates, location, ticket types, pricing, and settings. The detail source for promotion and capacity workflows.

Orders

List Orders Retrieves paginated orders for an event with buyer details, totals, payment status, and purchased ticket types. The Modified Since filter returns only orders created or updated after a given time, which is what makes nightly incremental syncs cheap.
Get Order Retrieves a single order in full: buyer information, line items, question answers, payment and refund status, and the tickets issued under it. The evidence record behind reconciliation and support workflows.

Tickets

List Tickets Retrieves paginated individual tickets for an event with attendee names, ticket type, order reference, check-in status, and collected answers. The source for attendee lists, check-in syncs, and capacity reconciliation.

Frequently Asked Questions

What can FlowRunner do with Humanitix?

FlowRunner agents can run List Events, Get Event, and List Orders in Humanitix, plus 2 more actions.

Does connecting Humanitix to FlowRunner require OAuth?

No. Humanitix connects to FlowRunner with an API key, no OAuth flow required.

Can Humanitix trigger a FlowRunner workflow automatically?

Humanitix doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Humanitix

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us