Integration
Connect Hubhus and Knackly
When New Calendar Event fires in Hubhus, your agent runs Create Record in Knackly, or New Record Created in Knackly to Create User in Hubhus. 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 Hubhus and Knackly 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 Hubhus and Knackly can do together
From Hubhus to Knackly
When New Calendar Event in Hubhus
then Create Record in Knackly
When New Contact in Hubhus
then Create Record and Run App in Knackly
From Knackly to Hubhus
When New Record Created in Knackly
then Create User in Hubhus
When New Record Created in Knackly
then Update calendar event in Hubhus
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 Hubhus and Knackly
Triggers and actions 4 triggers · 29 actions
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.
Trigger
New Record CreatedTriggers when a new record is created in the chosen catalog.
Action
Create RecordCreates a new record in a catalog from the data you supply, without generating documents.
Action
Create Record and Run AppCreates a new record in a catalog from your data and runs an app on it to generate documents (or, with Suspend, leaves the app for a user to finish interactively).
Action
Delete RecordDeletes a record from a catalog, along with its metadata and generated documents.
Action
Get DocumentsReturns the status of an app run on a record and the download links of the documents it generated.
Action
Get Record DataReturns a record from a catalog, including its stored data and the documents each app generated for it.
Action
List CatalogsReturns the catalogs your API key can access in the workspace, with the apps available in each.
Action
List RecordsReturns summaries of the records in a catalog, most recently created or modified first.
Action
Run App on RecordRuns an app on an existing record to generate (or re-generate) documents from the data already stored on it.
Action
Update RecordReplaces all the data stored on a record with the data you supply. Fails if a user currently has the record open in an app.
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 Hubhus
Hubhus to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Hubhus to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Hubhus to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Hubhus to MailchimpMailchimp marketing automation and email platform.
Hubhus to StripeStripe is a payment processing platform for online businesses.
Hubhus to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into Knackly
HubSpot to KnacklyHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to KnacklyGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to KnacklyGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to KnacklyGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to KnacklyGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to KnacklyActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
Hubhus and Knackly, answered
What can start an automation from Hubhus?
Any of Hubhus's 3 triggers in the catalog, including New Calendar Event, New Contact and New Lead. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Knackly when something happens in Hubhus?
Any of Knackly's 9 actions, including Create Record, Create Record and Run App, Update Record and Get Documents. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Knackly to Hubhus?
Yes. When something happens in Knackly, your agent can act in Hubhus too. This page covers both directions: Knackly's triggers and Hubhus's actions are listed here as well.
Do I have to build a connector for Hubhus or Knackly?
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 Hubhus and Knackly 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.