Integration
Connect FormHug and Swiftype
When New Or Updated Submission fires in FormHug, your agent runs Create Document in Swiftype, or New Document in Swiftype to Get current user in FormHug. 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 FormHug and Swiftype 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 FormHug and Swiftype can do together
From FormHug to Swiftype
When New Or Updated Submission in FormHug
then Create Document in Swiftype
From Swiftype to FormHug
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 FormHug and Swiftype
Triggers and actions 2 triggers · 25 actions
- New Or Updated Submission
Triggers when a submission is created or edited on the chosen form.
- Add entry
Creates a new entry (submission) on one of your FormHug forms.
- Add folder
Creates a new folder for organizing forms, at the root or inside an existing folder.
- Add form
Creates a new FormHug form, optionally with initial questions, locale, timezone, folder and header theme.
- Get current user
Returns the FormHug user associated with the connected account, including their billing account and current subscription plan.
- Get entry
Returns one submitted entry of a form, including every answer keyed by the form field's API code.
- Get form
Returns a form's details, including its name, settings, folder and the full list of its fields.
- List entries
Returns the entries (submissions) of one of your forms, optionally filtered and sorted.
- List folders
Returns all folders owned by the connected FormHug user, newest first.
- List forms
Returns the forms you created or that were shared with you, optionally filtered by name or folder.
- Update entry
Updates an existing entry on a form. Only the fields you supply change; all other answers stay as they are.
- Update form
Updates a form's name, description, locale, timezone, layout or question list. Only the values you provide are changed.
- New Document
Triggers when a new Document is created.
- Add domain
Add a crawler domain to an Engine.
- Add engine
Create a new Engine (index).
- Create Document
Creates a new Document.
- Delete document
Delete a document by document_id from a document type.
- Delete domain
Remove a crawler domain from an Engine.
- Delete engine
Delete an Engine by id.
- Get document
Retrieve a single document by external_id from a document type.
- Get engine
Retrieve a single Engine by id or name.
- List documents
List documents within a document type/engine.
- List domains
List crawler domains configured on an Engine.
- List engines
List all Engines for the account.
- Recrawl domain
Trigger a recrawl of a domain's crawled content.
- Search documents
Perform full-text search over documents within an Engine.
- Update document
Update fields on an existing document.
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 FormHug
FormHug to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
FormHug to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
FormHug to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
FormHug to Google SheetsGoogle Sheets
FormHug to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
FormHug to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Swiftype
Questions
FormHug and Swiftype, answered
What can start an automation from FormHug?
Any of FormHug's 1 trigger in the catalog, including New Or Updated Submission. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Swiftype when something happens in FormHug?
Any of Swiftype's 14 actions, including Create Document, Update document, Add domain and Add engine. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Swiftype to FormHug?
Yes. When something happens in Swiftype, your agent can act in FormHug too. This page covers both directions: Swiftype's triggers and FormHug's actions are listed here as well.
Do I have to build a connector for FormHug or Swiftype?
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 FormHug and Swiftype 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.