Integration
Connect SQL Server and WeTravel
When New or Updated Row fires in SQL Server, your agent runs Get order in WeTravel, or Lead Updated in WeTravel to Add Row in SQL Server. 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 SQL Server and WeTravel 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)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 SQL Server and WeTravel can do together
From SQL Server to WeTravel
When New or Updated Row in SQL Server
then Get order in WeTravel
When New Row in SQL Server
then List leads in WeTravel
From WeTravel to SQL Server
When Lead Updated in WeTravel
then Add Row in SQL Server
When New Lead in WeTravel
then Update Row in SQL Server
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 SQL Server and WeTravel
Triggers and actions 7 triggers · 17 actions
Trigger
New or Updated RowTriggers 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 RowTriggers when you add a new row.
Trigger
New TableFires when a new table appears in the connected SQL Server database.
Action
Add RowAdd one row to a table on the connected SQL Server database.
Action
Delete RowDelete the rows in a table whose chosen column equals a value.
Action
Find RowFind the first row in a table whose chosen column matches a value.
Action
Find Rows via Custom QueryRuns a SELECT statement you write against the connected SQL Server database and returns every row it matches.
Action
Find Row via Custom QueryRuns a SELECT statement you write against the connected SQL Server database and returns the first row it matches.
Action
Run Custom StatementRuns 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 RowChange column values on every row of a table whose chosen column matches a value.
Trigger
Lead UpdatedTriggers when a WeTravel lead is created or updated (for example, when the person requests again or books).
Trigger
New LeadTriggers when a new lead is captured for one of your WeTravel trips.
Trigger
Transaction UpdatedTriggers when a WeTravel transaction is created or updated, such as a payment, refund or payout changing status.
Action
Add payment linkCreates a WeTravel payment link for a trip with its dates, currency, fee handling and price, optionally with a deposit and installment payment plan.
Action
Add tripCreates a draft trip in WeTravel, which can then be built out and published.
Action
Get orderReturns a single trip order (booking), including amounts paid and due, packages and add-ons, participants and installments.
Action
Get payment linkReturns a WeTravel payment link by its UUID, including its trip and pricing details.
Action
List leadsReturns the leads (trip inquiries) in your WeTravel account, optionally filtered by trip, booking status, lead type and request date.
Action
List ordersReturns the orders (bookings) placed on a trip, with amounts paid and due, buyer and booked packages.
Action
List transactionsReturns the transactions (payments and refunds) on your WeTravel account, optionally filtered.
Action
List tripsReturns all trips in your WeTravel account, with their titles, destinations, dates and listing status.
Action
Publish tripPublishes a draft trip so its booking page goes live on WeTravel, and returns the published trip.
Action
Update tripUpdates an existing draft trip's details, such as title, dates, group size, pricing currency and booking settings. Only the fields you fill in are changed.
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 SQL Server
SQL Server to StripeStripe is a payment processing platform for online businesses.
SQL Server to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
SQL Server to JIRAAtlassian JIRA Cloud — issue tracking and project management.
SQL Server to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
SQL Server to TypeformBuild and publish online forms, surveys, and quizzes with Typeform.
SQL Server to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
More into WeTravel
HubSpot to WeTravelHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to WeTravelSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to WeTravelSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to WeTravelGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to WeTravelGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to WeTravelGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
SQL Server and WeTravel, answered
What can start an automation from SQL Server?
Any of SQL Server's 4 triggers in the catalog, including New or Updated Row, New or Updated Row (Custom Query), New Row and New Table. Describe the moment in plain language and your agent picks the right one.
What can your agent do in WeTravel when something happens in SQL Server?
Any of WeTravel's 10 actions, including Update trip, Add payment link, Add trip and Get order. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from WeTravel to SQL Server?
Yes. When something happens in WeTravel, your agent can act in SQL Server too. This page covers both directions: WeTravel's triggers and SQL Server's actions are listed here as well.
Do I have to build a connector for SQL Server or WeTravel?
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 SQL Server and WeTravel 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.