Integration
Connect FormHug to Checkout Page
When New Or Updated Submission fires in FormHug, your agent runs Create Ticket Group in Checkout Page. 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 Checkout Page 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 FormHug can start in Checkout Page
When New Or Updated Submission in FormHug
then Create Ticket Group in Checkout Page
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 Checkout Page
Triggers and actions 1 trigger · 57 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.
- Archive Checkout Page
Archive checkout page in Checkout Page.
- Archive Event
Archive event in Checkout Page.
- Archive Form
Archive form in Checkout Page.
- Archive Ticket Group
Archive a ticket group in Checkout Page.
- Archive Ticket Type
Archive a ticket type in Checkout Page.
- Create Checkout Page
Create checkout page in Checkout Page.
- Create Event
Create event in Checkout Page.
- Create Field For Checkout Page
Create field for checkout page in Checkout Page.
- Create Field For Event
Create field for event in Checkout Page.
- Create Field For Form
Create field for form in Checkout Page.
- Create Form
Create form in Checkout Page.
- Create Theme
Create a theme in Checkout Page.
- Create Ticket Group
Create ticket group in Checkout Page.
- Create Ticket Type
Create ticket type in Checkout Page.
- Delete Field For Checkout Page
Delete field for checkout page in Checkout Page.
- Delete Field For Event
Delete field for event in Checkout Page.
- Delete Field For Form
Delete field for form in Checkout Page.
- Delete Theme
Delete a theme in Checkout Page.
- Get Checkout Page
Get checkout page in Checkout Page.
- Get Customer
Get customer details in Checkout Page.
- Get Event
Get event in Checkout Page.
- Get Field For Checkout Page
Get field for checkout page in Checkout Page.
- Get Field For Event
Get field for event in Checkout Page.
- Get Field For Form
Get field for form in Checkout Page.
- Get Form
Get form in Checkout Page.
- Get Theme
Retrieve a theme in Checkout Page.
- Get Ticket Group
Get ticket group in Checkout Page.
- Get Ticket Type
Get ticket type in Checkout Page.
- List Customers
List all customers in Checkout Page.
- List Fields For Checkout Page
List fields for checkout page in Checkout Page.
- List Fields For Event
List fields for event in Checkout Page.
- List Fields For Form
List fields for form in Checkout Page.
- List Themes
List themes in Checkout Page.
- List Ticket Groups
List ticket groups in Checkout Page.
- List Ticket Types
List ticket types in Checkout Page.
- Update Checkout Page
Update checkout page in Checkout Page.
- Update Customer
Update a customer in Checkout Page.
- Update Event
Update event in Checkout Page.
- Update Field For Checkout Page
Update field for checkout page in Checkout Page.
- Update Field For Event
Update field for event in Checkout Page.
- Update Field For Form
Update field for form in Checkout Page.
- Update Form
Update form in Checkout Page.
- Update Product
Update product in Checkout Page.
- Update Theme
Update a theme in Checkout Page.
- Update Ticket Group
Update ticket group in Checkout Page.
- Update Ticket Type
Update a ticket type in Checkout Page.
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 is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
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 Checkout Page
Questions
FormHug and Checkout Page, 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 Checkout Page when something happens in FormHug?
Any of Checkout Page's 46 actions, including Create Checkout Page, Create Event, Create Field For Checkout Page and Create Field For Event. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Checkout Page to FormHug?
Checkout Page has no triggers in the catalog today, so automations start in FormHug. If you need the other direction, ask: your agent reads Checkout Page's API documentation and adds it.
Do I have to build a connector for FormHug or Checkout Page?
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 Checkout Page 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.