Integration
Connect Reply and Smily
When New Email Opened fires in Reply, your agent runs Add payment in Smily, or New And/Or Updated Client in Smily to Add contact list in Reply. 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 Reply and Smily 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 Reply and Smily can do together
From Reply to Smily
When New Email Opened in Reply
then Add payment in Smily
When New Emails Sent in Reply
then Create or Update Client in Smily
From Smily to Reply
When New And/Or Updated Client in Smily
then Add contact list in Reply
When New And/Or Updated Payment in Smily
then Add note to contact in Reply
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 Reply and Smily
Triggers and actions 11 triggers · 35 actions
Trigger
Inbox Category Set for ReplyTriggers when an email reply in Reply is given an inbox category, automatically or by a user.
Trigger
New Email OpenedTriggers when a contact opens a tracked email sent from Reply.
Trigger
New Emails SentTriggers when Reply sends an email from a sequence step.
Trigger
New Link ClickedTriggers when a recipient clicks a tracked link in an email sent from Reply.
Trigger
New Person BounceTriggers when an email sent from Reply bounces or is rejected by the recipient's mail server.
Trigger
New Person Opt OutTriggers when a contact opts out of outreach in Reply (unsubscribe link, manual opt-out, or marked Do Not Contact).
Trigger
Prospect FinishedTriggers when a contact's participation in a Reply sequence ends — completed, replied, bounced, opted out, or finished manually.
Action
Add contact listCreates a new contact list in Reply, optionally shared with your team.
Action
Add note to contactAdds a note to a contact's timeline in Reply.
Action
Add sequenceCreates a new sequence in Reply with its steps, schedule, sending accounts and settings.
Action
Create\Update PersonCreates a Reply contact, or updates the existing contact with the same email address.
Action
Delete contactDeletes a contact from your Reply account.
Action
Find contacts by criteriaReturns the contacts that match a search term and/or field rules, optionally scoped to a contact list, sequence or sequence step.
Action
Get contactReturns one Reply contact by its id, including profile details, owner, opt-out, call and meeting status, stage and custom fields.
Action
Get sequenceReturns one sequence in full: name, status, owner, schedule, settings, connected email and LinkedIn accounts, and its steps.
Action
List contact listsReturns the contact lists you own plus those shared with your team, optionally filtered by name.
Action
List contactsReturns your Reply contacts, optionally narrowed to one email address or LinkedIn profile URL.
Action
List inbox categoriesReturns the inbox categories you can file conversations under.
Action
List Sequence ContactsReturns the contacts enrolled in a sequence, with each contact's status, current step, added date, opt-out and call status.
Action
List sequencesReturns the sequences in your Reply account, optionally filtered by status, owner, folder, archive state or name.
Action
Mark as FinishedMarks one or more contacts as finished in every sequence they are in, so they receive no further sequence steps.
Action
Remove Person From CampaignRemoves a contact from a sequence so they stop progressing through it. The contact and their history stay in your Reply account.
Action
Send Test Webhook EventSends a test event from an existing Reply webhook subscription to its configured URL.
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.
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 Reply
Reply to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Reply to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Reply to StripeStripe is a payment processing platform for online businesses.
Reply to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Reply to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Reply to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
More into Smily
HubSpot to SmilyHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SmilySalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to SmilySlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to SmilyGoogle Sheets
Gmail to SmilyGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SmilyGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Reply and Smily, answered
What can start an automation from Reply?
Any of Reply's 7 triggers in the catalog, including New Email Opened, New Emails Sent, New Link Clicked and New Person Bounce. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Smily when something happens in Reply?
Any of Smily's 19 actions, including Create Inquiry, Create or Update Client, Update Booking and Update rental. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Smily to Reply?
Yes. When something happens in Smily, your agent can act in Reply too. This page covers both directions: Smily's triggers and Reply's actions are listed here as well.
Do I have to build a connector for Reply or Smily?
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.