Integration
Connect Privy to Livestorm
When New Contact fires in Privy, your agent runs Create Event in Livestorm. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Privy and Livestorm to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Privy can start in Livestorm
When New Contact in Privy
then Create Event in Livestorm
When New Order in Privy
then Update Event in Livestorm
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Privy and Livestorm
Triggers and actions 2 triggers · 49 actions
Trigger
New ContactTriggers when a new contact is added to your Privy account.
Trigger
New OrderTriggers when a new order is recorded in your Privy account.
Action
Check Coupon CodeCheck a coupon code. Check whether an individual code from a Shopify or BigCommerce pool has been redeemed, read live from the connected store's per-code usage counter (Privy stores no redemption events).
Action
Delete ContactDelete a contact by ID. Soft-delete a contact identified by its unique `id`.
Action
Find ContactList contacts. Retrieve a paginated list of contacts, most recently created first. Optionally filter by email, phone number, or consent status.
Action
Get AccountGet account. Retrieve information about the Privy account associated with the API token.
Action
Get Business Summary ReportGet business report summary. The business-level performance rollup for a period: signups, new subscribers, attributed revenue and orders, engagement rates, and business-wide order and revenue totals for context. Pass `compare=previous_period` to add previous-period values and typed change deltas to every metric.
Action
Get CouponGet a coupon. Retrieve a single coupon pool by its identifier — the list rows' inventory and health, plus `usage_count`, the connected store's pool-wide redemption counter read live.
Action
Get Display ReportGet display performance. The full performance stat set for one display over a period, including average order value and, when the display has run an A/B test, per-variation participants, conversions, and conversion rates.
Action
Get FlowGet a flow. Retrieve a single flow by its identifier, including its full configuration: re-entry behavior, flow filters, effective exit behavior, a server-generated behavior summary, and the node tree — each step's configuration (`data`) plus the branch graph, with split conditions and the nodes on each branch.
Action
Get ImportGet a contact import. Retrieve a single contact import — the same row `/v1/imports` lists for it.
Action
Get ProductGet a product. Retrieve a single product from your connected store's catalog by its store product id.
Action
Get Product CollectionGet a product collection. Retrieve one collection (Shopify) or category (BigCommerce) of your connected store by its store id, the `id` a `purchase_history` segment condition's `collection` filter holds.
Action
Get SegmentGet a segment. Retrieve a single segment by its identifier. The members themselves are `/v1/segments/{id}/contacts`. A campaign's `audience` segment ids resolve here when the segment was saved to the account. There is no per-segment performance report anywhere in the API.
Action
Get Segment CountsReturns how many contacts a segment reaches today: total, mailable and textable counts.
Action
Get TagGet a tag. Retrieve a single tag by its prefixed id — the same row `/v1/tags` lists for it. This is how to name the `tag_…` and `stag_…` ids that appear in a flow's condition tree.
Action
List Campaign ReportsList campaign performance. Every message campaign **sent in the period**, ranked by attributed revenue, each row carrying the full channel stat block (delivery, engagement, unsubscribes, attribution) scoped to the same period — so period comparisons need no per-campaign detail calls. Zero-revenue sends are listed too, ranked after the revenue rows; at most 100 campaigns are ranked, and a send with
Action
List CampaignsList campaigns. Retrieve a paginated list of your message campaigns, newest first.
Action
List Collection ProductsList a collection's products. Retrieve the products in one collection (Shopify) or category (BigCommerce) of your connected store, in the same shape as `/v1/products`.
Action
List Contact ActivityList a contact's activity. Retrieve the contact's activity timeline — signups, email and SMS sends, opens and clicks, orders, checkouts, tag changes — newest first. This is the same record the Privy dashboard's contact page shows, so "why did this contact get X?" can be answered from the API alone: find the send, the signup that triggered it, and the display or campaign each traces to.
Action
List CouponsList coupons. Retrieve a paginated list of your coupon pools with their code inventory and health status.
Action
List Display ReportsList display performance. Rank your displays by performance over a period — signups by default, or any of the documented sort keys. Displays whose value for the chosen sort key is zero are left out entirely, and ranking stops at 50 displays, which also caps the reported `total_count`. Use `/v1/reports/displays/{display_id}` for one display's full stat set, including average order value and A/B tes
Action
List DisplaysList displays. Retrieve a paginated list of your on-site displays, newest first. Archived displays are excluded by default — pass `status=archived` to list them.
Action
List Email TemplatesList email templates. The templates an email draft may start from: the account's own saved newsletter templates, listed first, and then Privy's gallery. Names and facets only; the design and HTML stay on the server, and a template is branded for the account only when a draft uses it. Templates with product blocks are offered only to an account with a connected catalog store. Templates whose produc
Action
List Flow ReportsList flow performance. Rank your flows by performance over a period — best performers first, remaining flows by recency. Each row combines email and SMS stats across the flow's message steps. Use `/v1/reports/flows/{flow_id}` for one flow's report including the per-node message breakdown.
Action
List FlowsList flows. Retrieve a paginated list of your automation flows, including each flow's trigger and steps.
Action
List ImportsList contact imports. Retrieve a paginated list of your contact imports — CSV uploads and connected-provider syncs — most recently requested first. Each row mirrors the dashboard's import history: type, processing status, contact counts, who requested it, when, and its review status.
Action
List OrdersList orders. Retrieve a paginated list of your orders across every source (Shopify, BigCommerce, Weebly, Wix, and orders reported via this API), most recently created first.
Action
List Product CollectionsList product collections. Retrieve the collections of your connected store, proxied live from the store's API: Shopify collections, or BigCommerce categories.
Action
List Product Collections For ProductList a product's collections. Retrieve the collections (Shopify) or categories (BigCommerce) one product of your connected store belongs to, by its store product id.
Action
List ProductsList products. Retrieve the product catalog of your connected store (Shopify or BigCommerce), proxied live from the store's API.
Action
List Segment ContactsList a segment's contacts. Retrieve the segment's members as a paginated list of contacts, in the same shape as the Contacts API, most recently created first.
Action
List SegmentsList segments. Retrieve a paginated list of your customer segments with their mailable/textable member counts.
Action
List TagsList tags. Retrieve a paginated list of the account's contact tags, ordered by name. Tag names are lower-cased and trimmed. Some older tags have not been merged yet, so the same name can appear on more than one row, each with its own id.
Action
List Top Products ReportList top products. Retrieve your store's top products ranked by views or sales over a 30, 60, or 90 day window, or all-time where the platform supports it.
Action
Create EventCreates a new Livestorm event with its first session, either from scratch or by duplicating the settings of an existing event.
Action
Create RegistrantRegisters a person for an upcoming Livestorm event session, with their email, name, registration fields and UTM tracking data.
Action
Create SessionSchedules a new session for an existing Livestorm event. Returns the created session, including its room link, status and scheduled start time.
Action
Find PeopleFinds people in your Livestorm workspace by email address, optionally limited to participants or team members.
Action
Find SessionFinds event sessions in your Livestorm workspace whose name matches the one you give, optionally narrowed by status and date range. Returns the matching sessions and the first match.
Action
Get eventReturns a single Livestorm event, including its title, status, registration link, settings, owner and registration fields.
Action
Get personReturns the details of a person in your Livestorm workspace, such as their name, email, role and timezone.
Action
Get sessionReturns a single Livestorm session, including its status, schedule, room link and attendee counts, optionally with its event, people, chat messages, questions or recordings.
Action
List eventsReturns the events in your Livestorm workspace, optionally filtered by title, scheduling status, tag, or creation and update dates.
Action
List session questionsReturns all the questions attendees asked during a Livestorm session, with any answers given.
Action
List sessionsReturns the sessions across all events in your Livestorm workspace, optionally filtered by status, scheduled start date, creation date or last update date.
Action
Remove EventDeletes a single Livestorm event.
Action
Remove RegistrantRemoves a registrant from a Livestorm event session, cancelling their registration.
Action
Remove SessionDeletes a single Livestorm event session.
Action
Update EventUpdates an existing Livestorm event, changing only the details you fill in, such as its title, description, status or room settings.
Action
Update SessionUpdates a Livestorm session's name, start date/time or timezone. Fields left blank keep their current values.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Privy
Privy to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Privy to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Privy to StripeStripe is a payment processing platform for online businesses.
Privy to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Privy to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Privy to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
More into Livestorm
HubSpot to LivestormHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to LivestormSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to LivestormSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to LivestormGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to LivestormGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to LivestormGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Privy and Livestorm, answered
What can start an automation from Privy?
Any of Privy's 2 triggers in the catalog, including New Contact and New Order. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Livestorm when something happens in Privy?
Any of Livestorm's 16 actions, including Create Event, Create Registrant, Create Session and Update Event. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Livestorm to Privy?
Livestorm has no triggers in the catalog today, so automations start in Privy. If you need the other direction, ask: your agent reads Livestorm's API documentation and adds it.
Do I have to build a connector for Privy or Livestorm?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Privy and Livestorm without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.