# Connect Event Tickets and SQL Server When **New Order** fires in [Event Tickets](https://apiant.ai/connections/event-tickets), your agent runs **Add Row** in [SQL Server](https://apiant.ai/connections/sql-server), or **New or Updated Row** in SQL Server to **Find Tickets and RSVPs** in Event Tickets. Describe the whole flow and it is built, tested on every scenario and kept running. Event Tickets **4** triggers Event Tickets **4** actions SQL Server **4** triggers SQL Server **7** 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 SQL Server to do together? Give your AI client this address. `https://mcp.apiant.ai` 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 and SQL Server can do together ### From Event Tickets to SQL Server - When **New Order** in Event Tickets then **Add Row** in SQL Server - When **Updated Attendees** in Event Tickets then **Update Row** in SQL Server ### From SQL Server to Event Tickets - When **New or Updated Row** in SQL Server then **Find Tickets and RSVPs** in Event Tickets - When **New Row** in SQL Server then **Get ticket** in Event Tickets 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 SQL Server ## Triggers and actions 8 triggers · 11 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. - Trigger **New or Updated Row** Triggers when a new row is added or modified. - Trigger **New or Updated Row (Custom Query)** Fires for each new or changed row returned by a SELECT statement you write against the connected SQL Server database. - Trigger **New Row** Triggers when you add a new row. - Trigger **New Table** Fires when a new table appears in the connected SQL Server database. - Action **Add Row** Add one row to a table on the connected SQL Server database. - Action **Delete Row** Delete the rows in a table whose chosen column equals a value. - Action **Find Row** Find the first row in a table whose chosen column matches a value. - Action **Find Rows via Custom Query** Runs a SELECT statement you write against the connected SQL Server database and returns every row it matches. - Action **Find Row via Custom Query** Runs a SELECT statement you write against the connected SQL Server database and returns the first row it matches. - Action **Run Custom Statement** Runs a statement you write against the connected SQL Server database that changes data rather than returning rows, and reports how many rows it changed. - Action **Update Row** Change column values on every row of a table whose chosen column matches a value. ## Each app on its own - [ **Event Tickets** Sell Tickets and Manage Registration on WordPress.](https://apiant.ai/connections/event-tickets) - [ **SQL Server** Connect directly to a Microsoft SQL Server database and run SQL statements from your automations.](https://apiant.ai/connections/sql-server) 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 SQL Server - [ **HubSpot to SQL Server** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-sql-server) - [ **Slack to SQL Server** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-sql-server) - [ **Mailchimp to SQL Server** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-sql-server) - [ **Shopify to SQL Server** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/shopify-to-sql-server) - [ **QuickBooks Online to SQL Server** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/quickbooks-online-to-sql-server) - [ **Pipedrive to SQL Server** Pipedrive is a sales CRM and pipeline management tool.](https://apiant.ai/connect/pipedrive-to-sql-server) Questions ## Event Tickets and SQL Server, 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 SQL Server when something happens in Event Tickets? Any of SQL Server's 7 actions, including Update Row, Add Row, Find Row and Find Rows via Custom Query. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from SQL Server to Event Tickets? Yes. When something happens in SQL Server, your agent can act in Event Tickets too. This page covers both directions: SQL Server's triggers and Event Tickets's actions are listed here as well. ### ### Do I have to build a connector for Event Tickets or SQL Server? 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. ### ### 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.