Integration
Connect BuildData and FormHug
When New permit fires in BuildData, your agent runs Get current user in FormHug, or New Or Updated Submission in FormHug to Geocode address in BuildData. 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 BuildData and FormHug to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 BuildData and FormHug can do together
From BuildData to FormHug
When New permit in BuildData
then Get current user in FormHug
From FormHug to BuildData
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 BuildData and FormHug
Triggers and actions 2 triggers · 23 actions
- New permit
- Geocode address
- Get permit
- Get property
- Get zoning
/zoning (point-in-polygon zoning lookup by coordinate)
- List business licences
- List contractors
- List development permits
- List inspections
- List major projects
- List permits
- List planning applications
- List property assessments
- 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.
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 BuildData
BuildData to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
BuildData to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
BuildData to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
BuildData to Google SheetsGoogle Sheets
BuildData to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
BuildData to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into FormHug
ActiveCampaign to FormHugActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to FormHugOrganize anything with Airtable, a modern database created for everyone.
Asana to FormHugAsana is a collaborative information manager for workspace.
ClickUp to FormHugClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Discord to FormHugDiscord is an all-in-one voice and text chat for gamers.
Brevo to FormHugBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Questions
BuildData and FormHug, answered
What can start an automation from BuildData?
Any of BuildData's 1 trigger in the catalog, including New permit. Describe the moment in plain language and your agent picks the right one.
What can your agent do in FormHug when something happens in BuildData?
Any of FormHug's 11 actions, including Update entry, Update form, Add entry and Add folder. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from FormHug to BuildData?
Yes. When something happens in FormHug, your agent can act in BuildData too. This page covers both directions: FormHug's triggers and BuildData's actions are listed here as well.
Do I have to build a connector for BuildData or FormHug?
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.
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.