Integration
Connect Smily to FilePost
When New And/Or Updated Client fires in Smily, your agent runs Update file in FilePost. 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 FilePost 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 can start in FilePost
When New And/Or Updated Client in Smily
then Update file in FilePost
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 FilePost
Triggers and actions 4 triggers · 29 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.
- Create Intake Link
Creates a FilePost intake link — a public upload page you can send to someone so they can drop files to you, with your own limits on file type, size, count and how long it stays open.
- Delete File
Permanently deletes a file from FilePost. The stored file and its public link are removed and cannot be recovered.
- Delete intake link
Closes a FilePost intake link so it stops accepting uploads. Files already uploaded through it are untouched, and the slot frees up against your plan's limit on active links.
- Get file
Returns the details FilePost holds about one stored file — its name, size, type, download link and when it expires.
- Get intake link
Returns one intake link from your FilePost account, looked up by its intake link ID. FilePost has no single-link endpoint, so the link is selected out of your full list of intake links.
- List Files
Returns the files stored in your FilePost account, newest first, together with the total number of files.
- List intake links
Returns the intake links on your FilePost account, with each link's label, public upload page, limits and expiry.
- Update file
Changes whether a stored file's name appears in its public link, and returns the file with its new link.
- Upload File
Uploads a file to FilePost and returns its shareable link.
- Upload File From URL
Stores a file from a public web link in FilePost and returns its shareable link.
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 FilePost
HubSpot to FilePostHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to FilePostSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to FilePostSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to FilePostGoogle Sheets
Gmail to FilePostGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to FilePostGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Smily and FilePost, 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 FilePost when something happens in Smily?
Any of FilePost's 10 actions, including Create Intake Link, Update file, Upload File and Upload File From URL. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from FilePost to Smily?
FilePost has no triggers in the catalog today, so automations start in Smily. If you need the other direction, ask: your agent reads FilePost's API documentation and adds it.
Do I have to build a connector for Smily or FilePost?
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.