Integration
Connect CrewForm and Hubhus
When AI Agent Task Failed fires in CrewForm, your agent runs Create User in Hubhus, or New Calendar Event in Hubhus to Send Task to AI Agent in CrewForm. 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 CrewForm and Hubhus 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 CrewForm and Hubhus can do together
From CrewForm to Hubhus
When AI Agent Task Failed in CrewForm
then Create User in Hubhus
When AI Agent Task Failed in CrewForm
then Update calendar event in Hubhus
From Hubhus to CrewForm
When New Calendar Event in Hubhus
then Send Task to AI Agent in CrewForm
When New Contact in Hubhus
then Update task in CrewForm
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 CrewForm and Hubhus
Triggers and actions 4 triggers · 30 actions
Trigger
AI Agent Task FailedTriggers when a CrewForm AI agent task fails.
Action
Add agentCreates a new AI agent in your CrewForm workspace with the model, instructions and settings you choose.
Action
Delete agentDeletes an AI agent from your CrewForm workspace.
Action
Delete taskDeletes a task from your CrewForm workspace.
Action
Get agentReturns a single CrewForm agent by its id, including its model, prompt and settings.
Action
Get taskReturns a single CrewForm task by its id, including its title, status, priority, assigned agent and results.
Action
List agentsReturns all AI agents in your CrewForm workspace, with each agent's name, model, prompt and settings.
Action
List tasksReturns the tasks in your CrewForm workspace, newest first, optionally only those with a given status.
Action
Send Task to AI AgentCreates a task in CrewForm assigned to an AI agent, which dispatches it to that agent to work on right away. Returns the created task.
Action
Update agentUpdates an existing CrewForm agent's name, model, prompt, temperature, tools, status or configuration. Only the fields you fill in are changed.
Action
Update taskUpdates an existing CrewForm task's title, description, priority, status, assigned agent or team, or metadata.
Trigger
New Calendar EventTriggers when a new calendar event (booking or meeting) is created.
Trigger
New ContactTriggers when a new contact is created in Hubhus.
Trigger
New LeadTriggers when a new lead is added to a Hubhus campaign.
Action
Add calendar resourceCreates a calendar resource in Hubhus — either a user's calendar or a standalone calendar such as a vehicle or meeting room.
Action
Add consentRecords a person's consent to a consent declaration, identified by email and/or phone.
Action
Book time slotBooks a time slot through a Hubhus booking form, creating a calendar event for the chosen calendar resources.
Action
Create UserCreates a user with a name, email, phone, department and role.
Action
Delete Calendar EventDeletes a calendar event.
Action
Delete LeadDeletes a lead.
Action
Find absencesReturns absences matching the given filters, such as type, status, user or date period.
Action
Find Calendar EventsReturns calendar events, optionally filtered by creation or update time, ID or an expression filter.
Action
Find calendar resourcesReturns calendar resources (user calendars and other resources such as rooms or vehicles) matching the given filters.
Action
Find CampaignsReturns the campaigns in the account.
Action
Find ContactsReturns contacts, optionally filtered by creation or update time, ID or an expression filter.
Action
Find LeadsReturns leads in a campaign, optionally filtered by creation or update time, ID or a lead expression filter.
Action
Find ProductsReturns products, optionally filtered.
Action
Find UsersReturns users in the account, optionally filtered.
Action
Get CampaignReturns one campaign by ID.
Action
Get ContactReturns one contact by ID.
Action
Get productReturns a single product from the product catalogue, optionally with its category, image, tags and custom product fields.
Action
Get UserReturns one user by ID.
Action
Update calendar eventUpdates an existing calendar event in Hubhus; fields left blank are not changed.
Action
Update userUpdates an existing Hubhus user's name, contact details, department, role, tags or active status. Fields left blank are not 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 CrewForm
CrewForm to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
CrewForm to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
CrewForm to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
CrewForm to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
CrewForm to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
CrewForm to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Hubhus
Google Sheets to HubhusGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to HubhusGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to HubhusGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to HubhusGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to HubhusActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to HubhusOrganize anything with Airtable, a modern database created for everyone.
Questions
CrewForm and Hubhus, answered
What can start an automation from CrewForm?
Any of CrewForm's 1 trigger in the catalog, including AI Agent Task Failed. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Hubhus when something happens in CrewForm?
Any of Hubhus's 20 actions, including Create User, Update calendar event, Update user and Add calendar resource. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Hubhus to CrewForm?
Yes. When something happens in Hubhus, your agent can act in CrewForm too. This page covers both directions: Hubhus's triggers and CrewForm's actions are listed here as well.
Do I have to build a connector for CrewForm or Hubhus?
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 CrewForm and Hubhus 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.