Integration
Connect Smily and SQL Server
When New And/Or Updated Client fires in Smily, your agent runs Add Row in SQL Server, or New or Updated Row in SQL Server to Add payment in Smily. 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 Smily and SQL Server to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Smily and SQL Server can do together
From Smily to SQL Server
When New And/Or Updated Client in Smily
then Add Row in SQL Server
From SQL Server to Smily
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 Smily and SQL Server
Triggers and actions 8 triggers · 26 actions
- New And/Or Updated And/Or Canceled Booking
Trigger when a booking is created and/or updated and/or canceled (with line item support).
- New And/Or Updated Client
Trigger when a client is created and/or updated (with line item support).
- New And/Or Updated Payment
Trigger when a payment is created and/or updated.
- New Inquiry
Trigger when a new inquiry is created.
- Add booking
Creates a booking (reservation, tentative hold or unavailable block) on a rental's calendar in Smily.
- Add payment
Records a new payment against a booking in Smily.
- Add rental
Creates a new rental property in your Smily account. Note that each rental added increases the account's monthly fee.
- Create Inquiry
Creates an inquiry for a rental, recording a guest's contact details, requested dates and message.
- Create or Update Client
Creates a new Smily client (guest), or updates an existing one when a client ID is given.
- Delete booking
Cancels a booking in Smily so it no longer occupies the rental's calendar.
- Find Bookings in Date Range
Returns the bookings that overlap a date range, optionally filtered by status, rental or client.
- Find Client by Email
Finds Smily clients (guests) whose email address matches the one given, returning the matching client records.
- Find Payment
Finds payments by their order ID (one or more, comma-separated).
- Get booking
Returns a single booking (reservation) by its ID, including dates, status, guest counts, pricing and linked rental and client.
- Get client
Returns a single client (guest) by ID, including their addresses, emails and phone numbers.
- Get rental
Returns a single rental (property) by its ID, including its details, pricing, location and related record IDs.
- List bookings
Returns the bookings in your Smily account, optionally filtered by dates, status, rental, client or last update time. By default only future, non-canceled bookings are returned.
- List clients
Returns the clients (guests) in your Smily account, including their addresses, emails and phone numbers.
- List inquiries
Returns the inquiries on your Smily account, including guest contact details, requested dates and party size.
- List payments
Returns the payments recorded on your Smily account, optionally filtered by order ID.
- List rentals
Returns the rentals (properties) in your Smily account, with their names, locations, capacity and pricing details.
- Update Booking
Updates an existing booking (reservation) in Smily — dates, guest counts, prices, deposit, notes, tags and status flags — and returns the updated booking.
- Update rental
Updates an existing rental property in Smily. Only the fields you fill in are changed.
- New or Updated Row
Triggers when a new row is added or modified.
- 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.
- New Row
Triggers when you add a new row.
- New Table
Fires when a new table appears in the connected SQL Server database.
- Add Row
Add one row to a table on the connected SQL Server database.
- Delete Row
Delete the rows in a table whose chosen column equals a value.
- Find Row
Find the first row in a table whose chosen column matches a value.
- Find Rows via Custom Query
Runs a SELECT statement you write against the connected SQL Server database and returns every row it matches.
- Find Row via Custom Query
Runs a SELECT statement you write against the connected SQL Server database and returns the first row it matches.
- 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.
- Update Row
Change column values on every row of a table whose chosen column matches a value.
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 Smily
Smily to StripeStripe is a payment processing platform for online businesses.
Smily to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Smily to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Smily to TwilioCloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...
Smily to TypeformBuild and publish online forms, surveys, and quizzes with Typeform.
Smily to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
More into SQL Server
HubSpot to SQL ServerHubSpot is your all-in-one stop for all of your marketing software needs.
Slack to SQL ServerSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Mailchimp to SQL ServerMailchimp marketing automation and email platform.
Shopify to SQL ServerShopify is a commerce platform for online stores and retail point-of-sale.
QuickBooks Online to SQL ServerQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Pipedrive to SQL ServerPipedrive is a sales CRM and pipeline management tool.
Questions
Smily and SQL Server, answered
What can start an automation from Smily?
Any of Smily's 4 triggers in the catalog, including New And/Or Updated And/Or Canceled Booking, New And/Or Updated Client, New And/Or Updated Payment and New Inquiry. 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 Smily?
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 Smily?
Yes. When something happens in SQL Server, your agent can act in Smily too. This page covers both directions: SQL Server's triggers and Smily's actions are listed here as well.
Do I have to build a connector for Smily 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.