Integration
Connect Smily to Okta
When New And/Or Updated Client fires in Smily, your agent runs Add User to Group in Okta. 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 Okta 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 Smily can start in Okta
When New And/Or Updated Client in Smily
then Add User to Group in Okta
When New And/Or Updated Payment in Smily
then Create User in Okta
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 Okta
Triggers and actions 4 triggers · 41 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
Activate UserActivates a staged or deprovisioned Okta user and returns their activation link and token. Activation emails the user unless turned off.
Action
Add groupCreates a new Okta-managed group with a name, an optional description, and any custom group profile attributes defined in your org.
Action
Add User to GroupAdds an existing Okta user to an Okta-managed group.
Action
Assign user to applicationAssigns an existing Okta user to an application, optionally setting their app username, password and app profile. Returns the resulting application user.
Action
Create UserCreates a new user in your Okta org, with or without credentials, and returns the new user's id and status.
Action
Deactivate UserDeactivates an Okta user, deprovisioning them from all assigned apps. This cannot be undone by the deactivation itself and may destroy the user's data in those apps.
Action
Delete groupPermanently deletes a group from your Okta org by its ID.
Action
Delete userPermanently deletes a deactivated Okta user. If the user is still active, this deactivates them instead, and running it a second time deletes them.
Action
Find Group by NameReturns the Okta groups whose name matches the name you specify, either exactly or by a partial match.
Action
Find User by EmailReturns the Okta users whose primary email matches the email you specify, including deprovisioned users.
Action
Get groupReturns one Okta group by its id, including its profile name, description and any custom attributes.
Action
Get userReturns one Okta user, including their status, timestamps, credentials summary, and standard and custom profile attributes. An error occurs if the user is not found.
Action
List applicationsReturns the applications in your Okta org, optionally narrowed by a name or label prefix or a filter expression.
Action
List group membersReturns the users who are members of an Okta group, with their profiles, including any custom attributes. Results can be narrowed with a search expression.
Action
List groupsReturns the groups in your Okta organization, optionally narrowed by a search, filter or name match.
Action
List usersReturns the users in your Okta organization, optionally narrowed by a search, filter or name query.
Action
Remove User From GroupRemoves a user from a group managed directly in Okta. The user account itself is not changed.
Action
Reset user passwordStarts a password reset for an Okta user and either emails them the reset link or returns the link. The user moves to Recovery status and can't sign in until they finish the reset.
Action
Suspend UserSuspends an active Okta user so they can't sign in, while keeping their group and app assignments. Suspended users can later be unsuspended or deactivated.
Action
Unsuspend userUnsuspends a suspended Okta user and returns them to the Active state.
Action
Update groupUpdates the name, description or custom attributes of an Okta-managed group. Anything left blank keeps its current value.
Action
Update userUpdates an existing Okta user's profile, including custom profile attributes, or credentials. Fields left blank keep their current values.
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 Okta
HubSpot to OktaHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to OktaSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to OktaSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to OktaGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to OktaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to OktaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Smily and Okta, 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 Okta when something happens in Smily?
Any of Okta's 22 actions, including Create User, Update group, Update user and Activate User. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Okta to Smily?
Okta has no triggers in the catalog today, so automations start in Smily. If you need the other direction, ask: your agent reads Okta's API documentation and adds it.
Do I have to build a connector for Smily or Okta?
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 Okta 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.