Integration
Connect Clust to Nango
When New Application Closed fires in Clust, your agent runs Add connection in Nango. 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 Nango 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 can start in Nango
When New Application Closed in Clust
then Add connection in Nango
When New Application Created in Clust
then Add connect session in Nango
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 Nango
Triggers and actions 8 triggers · 37 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.
Action
Add connectionImports (upserts) a connection into a Nango integration using credentials you already hold. If a connection with the same connection ID and integration already exists, its credentials are updated.
Action
Add connect sessionCreates a short-lived (30 minute) Nango connect session and returns its token and connect link, which your end user can use to connect an integration through Nango Connect UI.
Action
Add integrationCreates a new integration in the Nango environment for a given provider.
Action
Delete connectionDeletes a Nango connection for the given integration.
Action
Delete integrationDeletes an integration from the Nango environment.
Action
Get connectionReturns a specific Nango connection, including its current credentials (Nango refreshes an expired access token before returning it).
Action
Get connect sessionGet a Connect session by token.
Action
Get integrationReturns a specific Nango integration by its unique key.
Action
List integrationsReturns every integration configured in the connected Nango environment.
Action
Update connectionEdits a Nango connection's tags or its webhook URL override.
Action
Update integrationEdits an existing Nango integration: rename its ID, change its display name, toggle webhook forwarding, or replace its credentials or provider-specific configuration. Only the fields you fill in 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 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 Nango
Wix to NangoThe Wix website builder gives businesses of any size the tools to create, manage and grow a fully integrated...
Erpnext to NangoOpen-source ERP system for accounting, inventory, manufacturing, sales, projects, and CRM.
HubSpot to NangoHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to NangoSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to NangoSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to NangoGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Questions
Clust and Nango, 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 Nango when something happens in Clust?
Any of Nango's 11 actions, including Update connection, Update integration, Add connection and Add connect session. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Nango to Clust?
Nango has no triggers in the catalog today, so automations start in Clust. If you need the other direction, ask: your agent reads Nango's API documentation and adds it.
Do I have to build a connector for Clust or Nango?
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 Nango 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.