Integration
Connect Clust and Noko
When New Application Closed fires in Clust, your agent runs Mark Invoice as Paid in Noko, or Entry Changed in Noko to Create Contact in Clust. 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 Clust and Noko 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 Clust and Noko can do together
From Clust to Noko
When New Application Closed in Clust
then Mark Invoice as Paid in Noko
When New Application Created in Clust
then Create Project in Noko
From Noko to Clust
When Entry Changed in Noko
then Create Contact in Clust
When Invoice Changed in Noko
then Update Contact in Clust
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 Clust and Noko
Triggers and actions 14 triggers · 40 actions
Trigger
New Application ClosedTriggers when an application is closed.
Trigger
New Application CreatedTriggers when a new application is created.
Trigger
New Application LateTriggers when an application passes its deadline.
Trigger
New Application Progress Stage ChangedTriggers when an application moves to a different stage.
Trigger
New Application SubmittedTriggers when an application is submitted.
Trigger
New ContactTriggers when a contact is created.
Trigger
New or Updated ApplicationTriggers when an application is created or changed.
Trigger
New or Updated Application ItemTriggers when an item of the chosen application is added or changes status (submitted, approved, completed).
Action
Approve Application ItemApproves an application item.
Action
Assign a New Stakeholder to RoleAdds a stakeholder to a role on an existing application.
Action
Close ApplicationCloses an application.
Action
Create ApplicationCreates an application from a template and invites the contact to fill it in.
Action
Create CompanyCreates a company.
Action
Create ContactCreates a contact.
Action
Create TagCreates a tag.
Action
Delete ApplicationDeletes an application.
Action
Delete ContactDeletes a contact.
Action
Find ApplicationsReturns applications matching a status, contact email, external ID or keyword.
Action
Find CompaniesReturns companies matching a keyword.
Action
Find ContactsReturns contacts matching an email or keyword.
Action
Get ApplicationReturns one application by ID.
Action
Get Application ItemReturns one application item with its content.
Action
Get CompanyReturns one company by ID.
Action
Get ContactReturns one contact by ID.
Action
Get TemplateReturns one application template by ID.
Action
List Application ItemsReturns the items (documents, forms, tasks) of an application.
Action
List TagsReturns the team's tags.
Action
List Team MembersReturns the team's users.
Action
List TemplatesReturns the application templates.
Action
Reopen ApplicationReopens a closed application.
Action
Submit ApplicationSubmits an application on the client's behalf.
Action
Update ApplicationUpdates an application's title, stage, deadline, external ID or contact details.
Action
Update ContactUpdates a contact.
Action
Update Form FieldSets the answer of one field in a form item of an application.
Trigger
Entry ChangedTriggers when a Noko time entry is created or changed.
Trigger
Invoice ChangedTriggers when a Noko invoice is created or changed.
Trigger
New EntryTriggers when a new time entry is logged in Noko.
Trigger
New ExpenseTriggers when a new expense is logged in Noko.
Trigger
New InvoiceTriggers when a new invoice is created in Noko.
Trigger
New ProjectTriggers when a new project is created in Noko.
Action
Approve EntryMarks a Noko time entry as approved.
Action
Archive ProjectArchives a Noko project.
Action
Create EntryLogs a new time entry in Noko.
Action
Create ExpenseLogs a new expense against a Noko project.
Action
Create ProjectCreates a new Noko project.
Action
Create TagsCreates one or more Noko tags.
Action
Delete EntryDeletes a Noko time entry.
Action
Find ExpenseFinds the most recent Noko expense matching the filters.
Action
Find InvoiceFinds a Noko invoice by reference, state or company.
Action
Find ProjectFinds a Noko project by name.
Action
Find UserFinds a Noko user by name or email.
Action
Get EntryReturns a single Noko time entry by its ID.
Action
Mark Invoice as PaidMarks a Noko invoice as paid.
Action
Update EntryUpdates a Noko time entry's date, minutes, description, project or user.
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 Clust
Clust to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Clust to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Clust to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Clust to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Clust to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Clust to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Noko
HubSpot to NokoHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to NokoGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to NokoGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to NokoGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to NokoGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to NokoMailchimp marketing automation and email platform.
Questions
Clust and Noko, answered
What can start an automation from Clust?
Any of Clust's 8 triggers in the catalog, including New Application Closed, New Application Created, New Application Late and New Application Progress Stage Changed. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Noko when something happens in Clust?
Any of Noko's 14 actions, including Create Entry, Create Expense, Create Project and Create Tags. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Noko to Clust?
Yes. When something happens in Noko, your agent can act in Clust too. This page covers both directions: Noko's triggers and Clust's actions are listed here as well.
Do I have to build a connector for Clust or Noko?
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 Clust and Noko 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.