--- title: "Connect Event Tickets to Flodesk - APIANT.ai" description: "When \"New Order\" fires in Event Tickets, your agent runs \"Find a Subscriber by Email Address\" in Flodesk." canonical: "https://apiant.ai/connect/event-tickets-to-flodesk" --- # Connect Event Tickets to Flodesk When **New Order** fires in [Event Tickets](https://apiant.ai/connections/event-tickets), your agent runs **Find a Subscriber by Email Address** in [Flodesk](https://apiant.ai/connections/flodesk). Describe the whole flow and it is built, tested on every scenario and kept running. Event Tickets **4** triggers Event Tickets **4** actions Flodesk **15** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Event Tickets and Flodesk to do together? Give your AI client this address. `https://mcp.apiant.ai` One 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.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) Example flows ## What Event Tickets can start in Flodesk - When **New Order** in Event Tickets then **Find a Subscriber by Email Address** in Flodesk - When **Updated Attendees** in Event Tickets then **Add custom field** in Flodesk 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 Event Tickets and Flodesk ## Triggers and actions 4 triggers · 19 actions - Trigger **Attendees** Triggers when a new attendee is registered for a ticket or RSVP on your events. - Trigger **Check In** Triggers when an attendee is checked in to an event. - Trigger **New Order** Triggers when a new ticket order is placed, returning the order's attendee record (one per order). - Trigger **Updated Attendees** Triggers when an attendee is added or any of an attendee's details change, such as check-in status. - Action **Find Attendees** Finds ticket attendees by name, email, event, ticket, order status, check-in status and more. - Action **Find Tickets and RSVPs** Searches the tickets and RSVPs on your site by text, optionally limited to an event, provider or availability. - Action **Get attendee** Returns a single attendee by ID, including their ticket, event and check-in status. - Action **Get ticket** Returns a single ticket or RSVP by its ID, including its event, price, capacity and availability. - Action **Add custom field** Creates a new subscriber custom field in your Flodesk account with the label you choose. - Action **Add Existing Subscriber to Segment** Adds an existing Flodesk subscriber to one or more segments and returns the updated subscriber. - Action **Add Existing Subscriber to Workflow** Adds an existing Flodesk subscriber to a workflow, identified by subscriber ID or email address. - Action **Add segment** Creates a new segment in your Flodesk account and returns it. - Action **Create/Update Subscriber** Creates a new Flodesk subscriber, or updates the existing one with the same email address or id, optionally adding them to segments. - Action **Find a Subscriber by Email Address** Looks up a Flodesk subscriber by email address and returns their status, name, segments and custom field values. - Action **Get segment** Returns a single Flodesk segment, including its name, color, type and number of active subscribers. - Action **List campaigns** Returns the email campaigns in your Flodesk account, optionally filtered by status or a search term. - Action **List custom fields** Returns every subscriber custom field defined in your Flodesk account, with each field's key and display label. - Action **List segments** Returns all segments in your Flodesk account, with each segment's name, color, type and active subscriber count. - Action **List subscribers** Returns subscribers in your Flodesk account, optionally filtered by status or segment. - Action **List workflows** Returns the workflows in your Flodesk account, optionally filtered by status (active, paused or draft). - Action **Remove Existing Subscriber From Segment** Removes an existing Flodesk subscriber from one or more segments and returns the updated subscriber. - Action **Remove Existing Subscriber From Workflow** Removes an existing subscriber, identified by subscriber ID or email address, from a Flodesk workflow. - Action **Unsubscribe Subscriber** Unsubscribes a subscriber from all of your Flodesk lists so they no longer receive marketing emails, and returns the updated subscriber. ## Each app on its own - [ **Event Tickets** Sell Tickets and Manage Registration on WordPress.](https://apiant.ai/connections/event-tickets) - [ **Flodesk** Beginners and experts use Flodesk to create stunning emails that grow their business.](https://apiant.ai/connections/flodesk) Reviews ## What our customers say ## More from Event Tickets - [ **Event Tickets to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/event-tickets-to-hubspot) - [ **Event Tickets to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/event-tickets-to-salesforce) - [ **Event Tickets to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/event-tickets-to-slack) - [ **Event Tickets to Google Sheets** Google Sheets](https://apiant.ai/connect/event-tickets-to-google-sheets) - [ **Event Tickets to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/event-tickets-to-gmail) - [ **Event Tickets to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/event-tickets-to-google-calendar) ## More into Flodesk - [ **HubSpot to Flodesk** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-flodesk) - [ **Salesforce to Flodesk** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-flodesk) - [ **Slack to Flodesk** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-flodesk) - [ **Google Sheets to Flodesk** Google Sheets](https://apiant.ai/connect/google-sheets-to-flodesk) - [ **Gmail to Flodesk** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-flodesk) - [ **Google Calendar to Flodesk** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-flodesk) Questions ## Event Tickets and Flodesk, answered ### ### What can start an automation from Event Tickets? Any of Event Tickets's 4 triggers in the catalog, including New Order, Updated Attendees, Attendees and Check In. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Flodesk when something happens in Event Tickets? Any of Flodesk's 15 actions, including Create/Update Subscriber, Add custom field, Add Existing Subscriber to Segment and Add Existing Subscriber to Workflow. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Flodesk to Event Tickets? Flodesk has no triggers in the catalog today, so automations start in Event Tickets. If you need the other direction, ask: your agent reads Flodesk's API documentation and adds it. ### ### Do I have to build a connector for Event Tickets or Flodesk? 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 Event Tickets and Flodesk 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.