Integration
Connect Freshservice to Okta
When New or Updated Change fires in Freshservice, 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 Freshservice 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)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 Freshservice can start in Okta
When New or Updated Change in Freshservice
then Add User to Group 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 Freshservice and Okta
Triggers and actions 10 triggers · 49 actions
- Deleted Ticket
Triggered when a ticket is deleted.
- New or Updated Change
Triggered by a new or updated change in Freshservice.
- New or Updated Release
Triggered by a new or updated release.
- Two-way sync new and updated changes
Triggered by new and updated changes
- Two-way sync new and updated problems with PagerDuty ID
A trigger for two-way syncing new and updated problems having a PagerDuty ID. Can only be used with two-way sync actions.
- Two-way sync new and updated releases
Triggered by new or updated release
- Two-way sync new and updated tickets
A trigger for two-way syncing new and updated tickets. Can only be used with two-way sync actions.
- Updated Change
Triggered when a change is updated (created_at differs from updated_at).
- Updated Problem
Triggered when a problem is updated (created_at != updated_at).
- Updated Release
Triggered when a release is updated.
- Add Attachment to a Ticket
Adds an attachment from a url to a specified ticket.
- Add Attachment to a Ticket (Cisco)
Adds an attachment from a url to a specified ticket.
- Add Note To A Problem
Adds a note to a problem provided its id.
- Add Note to a Ticket
Adds a private or public note to a ticket.
- Create Change
Creates a change.
- Create Problem
Creates a problem.
- Create Release
Creates a release.
- Create Ticket
Creates a new ticket in Freshservice.
- Delete change
Deletes a change request in Freshservice.
- Delete Problem
Deletes a problem given its ID.
- Delete Ticket
Deletes a ticket given its ID.
- Get agent
Returns the details of a single agent in Freshservice, including their custom field values.
- Get change
Returns a single change request by its ID, including its custom fields.
- Get problem
Returns a single Freshservice problem by its ID, including its custom fields.
- Get release
Returns a Freshservice release by its ID, including its planning details, associated assets and changes, and custom fields.
- Get requester
Returns a single requester's details, including contact info, departments and custom fields.
- Get Ticket
Retrieves a single ticket by ID.
- List Agents
Lists agents.
- List changes
Returns change requests in Freshservice, optionally filtered by view, requester or last-updated time.
- List problems
Returns the problems in your Freshservice account, optionally only those updated since a given time.
- List releases
Returns the releases in your Freshservice account, optionally only those updated since a given time.
- List Requesters
Lists requesters.
- List Tickets
Lists tickets, optionally filtered.
- Reply to a Ticket
Adds a public reply to a ticket.
- Two-way sync delete ticket
Deletes a ticket. For use only with two-way sync delete triggers.
- Update Change
Updates a change given its ID.
- Update Problem
Updates a problem given its ID.
- Activate User
Activates a staged or deprovisioned Okta user and returns their activation link and token. Activation emails the user unless turned off.
- Add group
Creates a new Okta-managed group with a name, an optional description, and any custom group profile attributes defined in your org.
- Add User to Group
Adds an existing Okta user to an Okta-managed group.
- Assign user to application
Assigns an existing Okta user to an application, optionally setting their app username, password and app profile. Returns the resulting application user.
- Create User
Creates a new user in your Okta org, with or without credentials, and returns the new user's id and status.
- Deactivate User
Deactivates 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.
- Delete group
Permanently deletes a group from your Okta org by its ID.
- Delete user
Permanently deletes a deactivated Okta user. If the user is still active, this deactivates them instead, and running it a second time deletes them.
- Find Group by Name
Returns the Okta groups whose name matches the name you specify, either exactly or by a partial match.
- Find User by Email
Returns the Okta users whose primary email matches the email you specify, including deprovisioned users.
- Get group
Returns one Okta group by its id, including its profile name, description and any custom attributes.
- Get user
Returns one Okta user, including their status, timestamps, credentials summary, and standard and custom profile attributes. An error occurs if the user is not found.
- List applications
Returns the applications in your Okta org, optionally narrowed by a name or label prefix or a filter expression.
- List group members
Returns the users who are members of an Okta group, with their profiles, including any custom attributes. Results can be narrowed with a search expression.
- List groups
Returns the groups in your Okta organization, optionally narrowed by a search, filter or name match.
- List users
Returns the users in your Okta organization, optionally narrowed by a search, filter or name query.
- Remove User From Group
Removes a user from a group managed directly in Okta. The user account itself is not changed.
- Reset user password
Starts 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.
- Suspend User
Suspends 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.
- Unsuspend user
Unsuspends a suspended Okta user and returns them to the Active state.
- Update group
Updates the name, description or custom attributes of an Okta-managed group. Anything left blank keeps its current value.
- Update user
Updates 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 Freshservice
Freshservice to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Freshservice to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Freshservice to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Freshservice to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Freshservice to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Freshservice to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Okta
Questions
Freshservice and Okta, answered
What can start an automation from Freshservice?
Any of Freshservice's 10 triggers in the catalog, including New or Updated Change, New or Updated Release, Two-way sync new and updated changes and Two-way sync new and updated problems with PagerDuty ID. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Okta when something happens in Freshservice?
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 Freshservice?
Okta has no triggers in the catalog today, so automations start in Freshservice. 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 Freshservice 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 Freshservice 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.