Integration
Connect Clust to Qstash
When New Application Closed fires in Clust, your agent runs Batch publish messages in Qstash. 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 Qstash 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 Qstash
When New Application Closed in Clust
then Batch publish messages in Qstash
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 Qstash
Triggers and actions 8 triggers · 46 actions
- New Application Closed
Triggers when an application is closed.
- New Application Created
Triggers when a new application is created.
- New Application Late
Triggers when an application passes its deadline.
- New Application Progress Stage Changed
Triggers when an application moves to a different stage.
- New Application Submitted
Triggers when an application is submitted.
- New Contact
Triggers when a contact is created.
- New or Updated Application
Triggers when an application is created or changed.
- New or Updated Application Item
Triggers when an item of the chosen application is added or changes status (submitted, approved, completed).
- Approve Application Item
Approves an application item.
- Assign a New Stakeholder to Role
Adds a stakeholder to a role on an existing application.
- Close Application
Closes an application.
- Create Application
Creates an application from a template and invites the contact to fill it in.
- Create Company
Creates a company.
- Create Contact
Creates a contact.
- Create Tag
Creates a tag.
- Delete Application
Deletes an application.
- Delete Contact
Deletes a contact.
- Find Applications
Returns applications matching a status, contact email, external ID or keyword.
- Find Companies
Returns companies matching a keyword.
- Find Contacts
Returns contacts matching an email or keyword.
- Get Application
Returns one application by ID.
- Get Application Item
Returns one application item with its content.
- Get Company
Returns one company by ID.
- Get Contact
Returns one contact by ID.
- Get Template
Returns one application template by ID.
- List Application Items
Returns the items (documents, forms, tasks) of an application.
- List Tags
Returns the team's tags.
- List Team Members
Returns the team's users.
- List Templates
Returns the application templates.
- Reopen Application
Reopens a closed application.
- Submit Application
Submits an application on the client's behalf.
- Update Application
Updates an application's title, stage, deadline, external ID or contact details.
- Update Contact
Updates a contact.
- Update Form Field
Sets the answer of one field in a form item of an application.
- Add queue
Create or update a queue (upsert), setting parallelism.
- Add schedule
Create a cron-based schedule that periodically publishes a message to a destination.
- Add URL group endpoint
Create a URL group or add/update an endpoint within it (fan-out publishing target).
- Batch publish messages
Publish multiple messages to multiple destinations in one call.
- Delete DLQ message
Remove a message from the dead-letter queue.
- Delete message
Cancel a message that has not yet been delivered.
- Delete queue
Delete a queue by name.
- Delete schedule
Delete a schedule by id.
- Delete URL group
Deletes a QStash URL group and all its endpoints. In-flight messages are not removed.
- Enqueue message
Add a message to a named queue for sequential delivery.
- Get DLQ message
Retrieve a single dead-letter queue message by id.
- Get message
Retrieve a queued/published message by id.
- Get queue
Retrieve a queue's configuration and stats by name.
- Get schedule
Retrieve a schedule by id.
- Get URL group
Retrieve a URL group and its endpoints by name.
- List DLQ messages
List messages that failed delivery and landed in the dead-letter queue.
- List queues
List all queues for the account.
- Publish message
Publish a single message to a URL or URL group for QStash to deliver.
- Retry DLQ message
Re-attempt delivery of a dead-lettered message now.
- Update schedule
Updates an existing QStash schedule by replacing its settings (destination, cron, message and delivery options).
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 Qstash
Questions
Clust and Qstash, 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 Qstash when something happens in Clust?
Any of Qstash's 20 actions, including Update schedule, Add queue, Add schedule and Add URL group endpoint. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Qstash to Clust?
Qstash has no triggers in the catalog today, so automations start in Clust. If you need the other direction, ask: your agent reads Qstash's API documentation and adds it.
Do I have to build a connector for Clust or Qstash?
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 Qstash 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.