RegFox

Connect AI agents to RegFox, the event registration product from Webconnex. Agents pull registration records and read the forms, inventory, and coupons behind them, across a fully read-only surface.

6 actions API key available

RegFox website ↗ Platform Documentation ↗ Capability data verified 2026-08-05

A schedule fires while registration is open on a RegFox form

Agent runs Get Form Inventory for the form

Agent reads sold, remaining and total for each inventory-tracked item

Agent runs Search Records for Registrations created since the previous cycle

Agent compares new registrations against the remaining quantity per item

Agent posts the capacity picture and any item that has gone past its limit

The event owner decides which registrations to honour when an item is oversold

What This Integration Enables

RegFox is the event registration product from Webconnex, and it runs on the Webconnex unified public API, the same API that serves TicketSpice and GiveSmart. This connector always scopes its requests to the RegFox product, so it surfaces RegFox forms and records only. The centre of gravity here is capacity and the record trail behind it. List Forms enumerates the registration forms with an optional publish status filter and cursor paging, Get Form returns a single form's full configuration including its fields and settings, and Get Form Inventory returns sold, remaining and total quantities for every inventory-tracked item on that form: registration options, add-ons and tickets. That last one is what makes a RegFox flow useful before an event rather than after it.

The record side is search, not sync. Search Records queries five unified record types, Registrations, Transactions, Tickets, Orders and Customers, filtered by form and by created or updated date, and paged with a cursor you pass as the starting point for the next page. Get Record pulls one record by type and ID with its full field data, amounts and status. Get Coupon reads a single discount coupon by ID with its code, discount value and usage limits. All six actions read. This connector does not create or edit a form, does not change inventory, and does not create, apply or redeem a coupon; coupons are entered by the registrant on the form itself. There are also no triggers in this release. The Webconnex API does publish a webhook subscription API, but realtime triggers are not part of this connector, so change detection is a schedule plus Search Records with a date filter and the cursor, which is why the workflows here are written around a polling cadence rather than an event.

Without FlowRunner

Capacity checked by refreshing a page Someone opens the form dashboard to see whether a session is still open

Registrations reconciled after the event Attendee, payment and ticket records are lined up once the event has already run

Overselling found at the door An option past its limit is discovered when people arrive expecting a seat

With FlowRunner

Capacity read on a schedule Get Form Inventory reports sold, remaining and total per item without anyone logging in

Records reconciled while it still matters Search Records walks registrations, transactions and tickets in the same run

Overselling surfaced with names attached The item, the count past the limit and the specific registrations reach a named owner

Use Case Scenarios

Session Capacity Watch

A conference form carries a dozen breakout sessions, each an inventory-tracked item. On a schedule through the registration window, the agent runs Get Form Inventory and reads the remaining quantity for every item. Sessions crossing a low-remaining threshold are posted to the events channel with their current numbers, and sessions at zero are flagged separately. The programme team sees which rooms need to move before the waitlist becomes a queue at the door.

Registration and Payment Reconciliation

After each day of registration, the agent runs Search Records for Transactions created in that window, then runs Search Records for Registrations across the same range and matches them on the customer and order references. Records that appear on one side and not the other are pulled in full with Get Record and posted for review. Where a discount is involved, Get Coupon confirms the coupon's stated value and usage limits against the amount actually charged. Finance sees the gaps while the registrations are still fresh, not in a post-event reconciliation.

Attendee Roll-Up for Downstream Systems

The agent walks List Forms to find the published forms for an upcoming programme, runs Search Records for Registrations per form with the cursor, and normalises the field data into a single roster. That roster feeds badge printing, a mailing list in Mailchimp Marketing, and an attendee view in Google Sheets. One flow assembles what would otherwise be several separate exports.

Human-in-Loop Highlight

The gate on RegFox is the oversell. Get Form Inventory reports an inventory-tracked item at zero remaining, and Search Records is still returning Registrations against that same item. Someone has registered for a seat that no longer exists. The agent can see the whole picture, and it can change none of it: this connector cannot adjust inventory, cannot cancel a registration and cannot refund a transaction. Whatever happens next means telling a named person they are in or out, and there is no undo for the message that goes to the person who is out. So the agent does not pick. It assembles the item, the counts, and every registration recorded past the limit with its timestamp and record ID, and routes to the event owner: "Saturday Workshop A shows 0 remaining against 40 total, and 3 registrations landed after the last seat sold. Record 118422 at 09:14, 118451 at 09:16, 118460 at 09:31. Honour all three and raise the cap in RegFox, honour the first and move the other two to the waitlist, or hold all three pending a room change?" The owner decides, in order, with the timestamps in front of them. The agent then carries out the downstream half, the waitlist mail and the roster update, against the decision a person actually made.

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

6 actions

Forms

List Forms Lists RegFox registration forms (events) on the connected Webconnex account. Supports optional filtering by publish status and cursor-based pagination. Results are scoped to the RegFox product automatically.
Get Form Retrieves the full configuration of a single RegFox registration form by its numeric ID, including its fields, path, status and settings. Use List Forms to discover form IDs.
Get Form Inventory Retrieves inventory levels for a RegFox form, showing sold, remaining and total quantities for each inventory-tracked item (registration options, add-ons, tickets). Useful for monitoring capacity and availability.

Records

Search Records Searches registration and transaction records across the RegFox account by record type. Choose Registrations for individual attendee registrations, Transactions for payments, Tickets for issued tickets, Orders for order-level records, or Customers for buyer records. Filter by form and by created/updated date, and page through results with the cursor.
Get Record Retrieves a single record by its numeric ID for a given record type (Registration, Transaction, Ticket, Order or Customer). Returns the full record detail including field data, amounts and status.

Coupons

Get Coupon Retrieves a single discount coupon by its numeric ID, including its code, discount value, usage limits and the form it belongs to.

Frequently Asked Questions

What can FlowRunner do with RegFox?

FlowRunner agents can run List Forms, Get Form, and Get Form Inventory in RegFox, plus 3 more actions.

Does connecting RegFox to FlowRunner require OAuth?

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

Can RegFox trigger a FlowRunner workflow automatically?

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

Start building with RegFox

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

Start Building Free Talk to us