Integration
Connect Smily to Checkout Page
When New And/Or Updated Client fires in Smily, your agent runs Create Ticket Group in Checkout Page. 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 Checkout Page 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 Smily can start in Checkout Page
When New And/Or Updated Client in Smily
then Create Ticket Group in Checkout Page
When New And/Or Updated Payment in Smily
then Create Checkout Page in Checkout Page
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 Checkout Page
Triggers and actions 4 triggers · 65 actions
Trigger
New And/Or Updated And/Or Canceled BookingTrigger when a booking is created and/or updated and/or canceled (with line item support).
Trigger
New And/Or Updated ClientTrigger when a client is created and/or updated (with line item support).
Trigger
New And/Or Updated PaymentTrigger when a payment is created and/or updated.
Trigger
New InquiryTrigger when a new inquiry is created.
Action
Add bookingCreates a booking (reservation, tentative hold or unavailable block) on a rental's calendar in Smily.
Action
Add paymentRecords a new payment against a booking in Smily.
Action
Add rentalCreates a new rental property in your Smily account. Note that each rental added increases the account's monthly fee.
Action
Create InquiryCreates an inquiry for a rental, recording a guest's contact details, requested dates and message.
Action
Create or Update ClientCreates a new Smily client (guest), or updates an existing one when a client ID is given.
Action
Delete bookingCancels a booking in Smily so it no longer occupies the rental's calendar.
Action
Find Bookings in Date RangeReturns the bookings that overlap a date range, optionally filtered by status, rental or client.
Action
Find Client by EmailFinds Smily clients (guests) whose email address matches the one given, returning the matching client records.
Action
Find PaymentFinds payments by their order ID (one or more, comma-separated).
Action
Get bookingReturns a single booking (reservation) by its ID, including dates, status, guest counts, pricing and linked rental and client.
Action
Get clientReturns a single client (guest) by ID, including their addresses, emails and phone numbers.
Action
Get rentalReturns a single rental (property) by its ID, including its details, pricing, location and related record IDs.
Action
List bookingsReturns 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.
Action
List clientsReturns the clients (guests) in your Smily account, including their addresses, emails and phone numbers.
Action
List inquiriesReturns the inquiries on your Smily account, including guest contact details, requested dates and party size.
Action
List paymentsReturns the payments recorded on your Smily account, optionally filtered by order ID.
Action
List rentalsReturns the rentals (properties) in your Smily account, with their names, locations, capacity and pricing details.
Action
Update BookingUpdates an existing booking (reservation) in Smily — dates, guest counts, prices, deposit, notes, tags and status flags — and returns the updated booking.
Action
Update rentalUpdates an existing rental property in Smily. Only the fields you fill in are changed.
Action
Archive Checkout PageArchive checkout page in Checkout Page.
Action
Archive EventArchive event in Checkout Page.
Action
Archive FormArchive form in Checkout Page.
Action
Archive Ticket GroupArchive a ticket group in Checkout Page.
Action
Archive Ticket TypeArchive a ticket type in Checkout Page.
Action
Create Checkout PageCreate checkout page in Checkout Page.
Action
Create EventCreate event in Checkout Page.
Action
Create Field For Checkout PageCreate field for checkout page in Checkout Page.
Action
Create Field For EventCreate field for event in Checkout Page.
Action
Create Field For FormCreate field for form in Checkout Page.
Action
Create FormCreate form in Checkout Page.
Action
Create ThemeCreate a theme in Checkout Page.
Action
Create Ticket GroupCreate ticket group in Checkout Page.
Action
Create Ticket TypeCreate ticket type in Checkout Page.
Action
Delete Field For Checkout PageDelete field for checkout page in Checkout Page.
Action
Delete Field For EventDelete field for event in Checkout Page.
Action
Delete Field For FormDelete field for form in Checkout Page.
Action
Delete ThemeDelete a theme in Checkout Page.
Action
Get Checkout PageGet checkout page in Checkout Page.
Action
Get CustomerGet customer details in Checkout Page.
Action
Get EventGet event in Checkout Page.
Action
Get Field For Checkout PageGet field for checkout page in Checkout Page.
Action
Get Field For EventGet field for event in Checkout Page.
Action
Get Field For FormGet field for form in Checkout Page.
Action
Get FormGet form in Checkout Page.
Action
Get ThemeRetrieve a theme in Checkout Page.
Action
Get Ticket GroupGet ticket group in Checkout Page.
Action
Get Ticket TypeGet ticket type in Checkout Page.
Action
List CustomersList all customers in Checkout Page.
Action
List Fields For Checkout PageList fields for checkout page in Checkout Page.
Action
List Fields For EventList fields for event in Checkout Page.
Action
List Fields For FormList fields for form in Checkout Page.
Action
List ThemesList themes in Checkout Page.
Action
List Ticket GroupsList ticket groups in Checkout Page.
Action
List Ticket TypesList ticket types in Checkout Page.
Action
Update Checkout PageUpdate checkout page in Checkout Page.
Action
Update CustomerUpdate a customer in Checkout Page.
Action
Update EventUpdate event in Checkout Page.
Action
Update Field For Checkout PageUpdate field for checkout page in Checkout Page.
Action
Update Field For EventUpdate field for event in Checkout Page.
Action
Update Field For FormUpdate field for form in Checkout Page.
Action
Update FormUpdate form in Checkout Page.
Action
Update ProductUpdate product in Checkout Page.
Action
Update ThemeUpdate a theme in Checkout Page.
Action
Update Ticket GroupUpdate ticket group in Checkout Page.
Action
Update Ticket TypeUpdate a ticket type in Checkout Page.
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 Checkout Page
HubSpot to Checkout PageHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Checkout PageSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Checkout PageSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Checkout PageGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Checkout PageGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Checkout PageGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Smily and Checkout Page, 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 Checkout Page when something happens in Smily?
Any of Checkout Page's 46 actions, including Create Checkout Page, Create Event, Create Field For Checkout Page and Create Field For Event. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Checkout Page to Smily?
Checkout Page has no triggers in the catalog today, so automations start in Smily. If you need the other direction, ask: your agent reads Checkout Page's API documentation and adds it.
Do I have to build a connector for Smily or Checkout Page?
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 Smily and Checkout Page 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.