Integration
Connect Formester and Freshservice
When New Submission fires in Formester, your agent runs Add Attachment to a Ticket in Freshservice, or New or Updated Change in Freshservice to Get Form in Formester. 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 Formester and Freshservice 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 Formester and Freshservice can do together
From Formester to Freshservice
When New Submission in Formester
then Add Attachment to a Ticket in Freshservice
When New Submission in Formester
then Add Attachment to a Ticket (Cisco) in Freshservice
From Freshservice to Formester
When New or Updated Change in Freshservice
then Get Form in Formester
When New or Updated Release in Freshservice
then Get Prefill in Formester
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 Formester and Freshservice
Triggers and actions 11 triggers · 31 actions
Trigger
New SubmissionTriggers when a form receives a new submission.
Action
Delete PrefillDeletes a prefill from a form.
Action
Delete SubmissionDeletes a form submission.
Action
Delete Unique LinkDeletes a unique link and its prefill.
Action
Get FormReturns one form with its fields and their element IDs.
Action
Get PrefillReturns one prefill with its prefilled values.
Action
Get SubmissionReturns one form submission and its answers.
Action
Get Unique LinkReturns one unique link and its submission status.
Action
List FormsReturns the forms in your Formester organization, 20 per page.
Action
List PrefillsReturns the prefills (pre-populated form links) of a form.
Action
List SubmissionsReturns the submissions of a form, newest first by default, 20 per page.
Action
List Unique LinksReturns the per-recipient unique links of a form and their submission status.
Trigger
Deleted TicketTriggered when a ticket is deleted.
Trigger
New or Updated ChangeTriggered by a new or updated change in Freshservice.
Trigger
New or Updated ReleaseTriggered by a new or updated release.
Trigger
Two-way sync new and updated changesTriggered by new and updated changes
Trigger
Two-way sync new and updated problems with PagerDuty IDA trigger for two-way syncing new and updated problems having a PagerDuty ID. Can only be used with two-way sync actions.
Trigger
Two-way sync new and updated releasesTriggered by new or updated release
Trigger
Two-way sync new and updated ticketsA trigger for two-way syncing new and updated tickets. Can only be used with two-way sync actions.
Trigger
Updated ChangeTriggered when a change is updated (created_at differs from updated_at).
Trigger
Updated ProblemTriggered when a problem is updated (created_at != updated_at).
Trigger
Updated ReleaseTriggered when a release is updated.
Action
Add Attachment to a TicketAdds an attachment from a url to a specified ticket.
Action
Add Attachment to a Ticket (Cisco)Adds an attachment from a url to a specified ticket.
Action
Add Note To A ProblemAdds a note to a problem provided its id.
Action
Delete changeDeletes a change request in Freshservice.
Action
Delete ProblemDeletes a problem given its ID.
Action
Delete TicketDeletes a ticket given its ID.
Action
Get agentReturns the details of a single agent in Freshservice, including their custom field values.
Action
Get changeReturns a single change request by its ID, including its custom fields.
Action
Get problemReturns a single Freshservice problem by its ID, including its custom fields.
Action
Get releaseReturns a Freshservice release by its ID, including its planning details, associated assets and changes, and custom fields.
Action
Get requesterReturns a single requester's details, including contact info, departments and custom fields.
Action
Get TicketRetrieves a single ticket by ID.
Action
List AgentsLists agents.
Action
List changesReturns change requests in Freshservice, optionally filtered by view, requester or last-updated time.
Action
List problemsReturns the problems in your Freshservice account, optionally only those updated since a given time.
Action
List releasesReturns the releases in your Freshservice account, optionally only those updated since a given time.
Action
List RequestersLists requesters.
Action
List TicketsLists tickets, optionally filtered.
Action
Reply to a TicketAdds a public reply to a ticket.
Action
Two-way sync delete ticketDeletes a ticket. For use only with two-way sync delete triggers.
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 Formester
Formester to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Formester to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Formester to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Formester to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Formester to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Formester to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Freshservice
ActiveCampaign to FreshserviceActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to FreshserviceOrganize anything with Airtable, a modern database created for everyone.
Asana to FreshserviceAsana is a collaborative information manager for workspace.
ClickUp to FreshserviceClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Discord to FreshserviceDiscord is an all-in-one voice and text chat for gamers.
Freshdesk to FreshserviceFreshdesk is a cloud-based customer support and helpdesk platform.
Questions
Formester and Freshservice, answered
What can start an automation from Formester?
Any of Formester's 1 trigger in the catalog, including New Submission. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Freshservice when something happens in Formester?
Any of Freshservice's 20 actions, including Add Attachment to a Ticket, Add Attachment to a Ticket (Cisco), Add Note To A Problem and Get agent. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Freshservice to Formester?
Yes. When something happens in Freshservice, your agent can act in Formester too. This page covers both directions: Freshservice's triggers and Formester's actions are listed here as well.
Do I have to build a connector for Formester or Freshservice?
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 Formester and Freshservice 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.