flowgate

Step 1. Integrations tab → select your ticketing platform from the dropdown → enter the platform credential → Connect. For More.com, enter the Teller username/email and password in the two fields shown.

Step 2. Wait 1-2 minutes for first sync. Your events appear in the top dropdown.

Step 3. Select an event → Dashboard loads with KPIs. Use synced capacity where available, set break-even target once if missing, then use FlowGate Command for actions: "optimize my sales", "what is slowing my sales?", "what should I do this week?".

Where to find your platform credential (25+ platforms):

More.com connection. Choose More.com in Connections and enter the Teller email or username and password.

The Teller connection updates events, venues, dates, sold tickets, revenue and entry scans when available. If it does not provide capacity or available seats, add capacity in Production Settings or upload the availability report.

Rules watch your event metrics and trigger when conditions are met. Two ways to create:

FlowGate Orchestrate (recommended): FlowGate Command tab → Orchestrate mode → type plain English ("if sales pace drops below 30/day and days to event below 14, send alert"). FlowGate converts to structured conditions.

Manual: FlowGate tab → New Rule. Choose conditions (sales pace, break-even %, days to event, risk) and actions (notify, promo trigger, price change).

Cooldown is 6h by default to prevent spam. Edit per rule.

Send event data to using your FlowGate connection key in the X-API-Key field.

Payload schema:

{
  "external_id": "your-event-123",
  "name": "Event Name",
  "event_date": "2026-06-15T20:00:00Z",
  "capacity": 5000,
  "metrics": {
    "tickets_sold": 1240,
    "revenue_gross": 37200.00,
    "currency": "EUR"
  }
}

Sending the same external_id updates the existing event. Update frequency depends on the platform limits. For Teller, avoid many repeated updates within one hour unless More.com approves it.

Generate keys: Integrations tab > FlowGate API Keys.

Tickets Sold: total tickets sold for the selected performance or production.

Capacity: the total number of tickets/seats that can be sold. If the ticketing API does not provide it, add it in Production Settings.

Sell-through: sold tickets divided by capacity. This is the percentage shown in the event dropdown.

Missing capacity: FlowGate cannot calculate sell-through until capacity is added or imported from the ticketing platform.

Revenue: total gross revenue from tickets sold so far, in event currency.

Break-even target: the revenue needed for the production to cover costs. Add it once so FlowGate can calculate the gap and required pace.

Break-even path: what needs to happen from today until the event date to reach the target.

Sales pace: how quickly tickets or revenue are moving. It is useful only when the event date, sales data and target are reliable.

Avg Ticket Price: revenue divided by sold tickets.

Days to Event: calendar days until event date.

Active Rules: number of automation rules currently watching this event.

0-10%: red

11-30%: yellow

31-60%: orange

61-80%: green

81%+: platinum

This rule is based only on sell-through percentage, not the absolute number of sold tickets.

Trial: 3 events · 14 days · full features

Starter: 15 events · email support

Pro: 60 events · priority support

Business: unlimited events · dedicated support · team access (RBAC)

Only on-sale events count against the limit. Ended, cancelled, and draft events do not.

What it is. The FlowGate Rule Orchestrator (FlowGate Command tab, Orchestrate mode) turns a sentence in plain English into an automation that runs in the background and watches your event 24/7. Stop checking dashboards every hour, get pinged only when a decision is needed.

How rules are stored. Every rule lives in a per-tenant database table (fg_revenue_rules) with: name, condition (e.g. "sales pace < 20/day"), action (notify / suggest / auto), cooldown (so it never spams), priority, and timestamps. Multi-tenant isolated, your rules are not visible to other organizations.

How rules run. A scheduled job evaluates every enabled rule against your latest event metrics every ~15 minutes. When a condition fires, the rule is marked triggered, the action runs, and a row is written to the Revenue Actions Log so you have a full audit trail of what fired, when, and why.

Rule modes.

• Notify: pings you (alert / email) without changing anything. Safest, default for most templates.
• Suggest: proposes an action (e.g. "launch flash sale") in your Recent Actions feed for you to approve.
• Auto: executes the action without confirmation. Reserved for clearly reversible changes (e.g. tier transitions). Avoid for destructive actions like ad-budget changes unless you trust the trigger.

Ready templates.

• Slow Sales Alert: pings when daily sales drop below 20/day so you catch stagnation early.
• High Demand: when capacity sold exceeds 80%, suggests reviewing tier prices to protect margin.
• Risk Alert: composite trigger (risk > 60 AND < 7 days left) for urgent intervention.
• Flash Sale Trigger: break-even < 50% with < 14 days left, recommends a time-bound discount campaign.
• Auto-Boost FB Ads: if sales drop below 10/day, raises Facebook ad budget by 15% and notifies you. Note: this is the only template that auto-spends money. Review carefully before enabling.
• Decision Maker Nudge: if 5+ buyers stay on checkout > 10 minutes, sends a "Final 5 tickets" urgency reminder.

Why this matters. Sales windows are time-sensitive. A drop in sales pace at 03:00 can cost an entire day of revenue if you only see it at 09:00. Rules close that gap automatically, with a written audit trail you can review later. Plus the cooldown prevents notification fatigue.

Plan availability. Revenue Rules Engine is included on Pro and Business plans. Trial users get full access for 14 days. Starter does not include rules.

Auto-pull platforms (Eventbrite, Ticket Tailor): FlowGate fetches data every 15 min via the platform API. No webhook needed on your side.

Webhook/API platforms: your platform posts to FlowGate, or you POST manually. Same 15-min cadence recommended.

Idempotency: deduplicated by external_id. Re-posting the same payload updates the event, it never creates a duplicate.