Integration

Connect Clust and Givecloud

When New Application Closed fires in Clust, your agent runs Get Post in Givecloud, or New Supporter in Givecloud to Create Contact in Clust. Describe the whole flow and it is built, tested on every scenario and kept running.

Clust8 triggers Clust26 actions Givecloud3 triggers Givecloud15 actions

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 Givecloud to do together?

Ask the assistant

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

One 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.ai

Start Claude Code there, approve the server, and sign in in the browser page it opens.

Claude Code guide

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

Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

Setup guide

Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

Setup guide

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

Grok

Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.

Setup guide

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

Example flows

What Clust and Givecloud can do together

From Clust to Givecloud

When New Application Closed in Clustthen Get Post in Givecloud
When New Application Created in Clustthen Create Sponsee in Givecloud

From Givecloud to Clust

When New Supporter in Givecloudthen Create Contact in Clust
When Supporter Updated in Givecloudthen 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 Givecloud

Triggers and actions 11 triggers · 41 actions

Trigger
New Application Closed
Triggers when an application is closed.
Trigger
New Application Created
Triggers when a new application is created.
Trigger
New Application Late
Triggers when an application passes its deadline.
Trigger
New Application Progress Stage Changed
Triggers when an application moves to a different stage.
Trigger
New Application Submitted
Triggers when an application is submitted.
Trigger
New Contact
Triggers when a contact is created.
Trigger
New or Updated Application
Triggers when an application is created or changed.
Trigger
New or Updated Application Item
Triggers when an item of the chosen application is added or changes status (submitted, approved, completed).
Action
Approve Application Item
Approves an application item.
Action
Assign a New Stakeholder to Role
Adds a stakeholder to a role on an existing application.
Action
Close Application
Closes an application.
Action
Create Application
Creates an application from a template and invites the contact to fill it in.
Action
Create Company
Creates a company.
Action
Create Contact
Creates a contact.
Action
Create Tag
Creates a tag.
Action
Delete Application
Deletes an application.
Action
Delete Contact
Deletes a contact.
Action
Find Applications
Returns applications matching a status, contact email, external ID or keyword.
Action
Find Companies
Returns companies matching a keyword.
Action
Find Contacts
Returns contacts matching an email or keyword.
Action
Get Application
Returns one application by ID.
Action
Get Application Item
Returns one application item with its content.
Action
Get Company
Returns one company by ID.
Action
Get Contact
Returns one contact by ID.
Action
Get Template
Returns one application template by ID.
Action
List Application Items
Returns the items (documents, forms, tasks) of an application.
Action
List Tags
Returns the team's tags.
Action
List Team Members
Returns the team's users.
Action
List Templates
Returns the application templates.
Action
Reopen Application
Reopens a closed application.
Action
Submit Application
Submits an application on the client's behalf.
Action
Update Application
Updates an application's title, stage, deadline, external ID or contact details.
Action
Update Contact
Updates a contact.
Action
Update Form Field
Sets the answer of one field in a form item of an application.
Trigger
Contribution Paid
Triggers when a new contribution (donation or purchase) is placed in Givecloud.
Trigger
New Supporter
Triggers when a new supporter (donor) is created in Givecloud.
Trigger
Supporter Updated
Triggers when a Givecloud supporter (donor) is created or updated.
Action
Create Sponsee
Creates a new Givecloud sponsee (a child or project available for sponsorship).
Action
Delete Sponsee
Deletes a Givecloud sponsee.
Action
Get Contribution
Returns one Givecloud contribution (donation or purchase) by ID.
Action
Get Post
Returns one post from a Givecloud feed.
Action
Get Product
Returns one Givecloud product by ID, optionally with its categories and variants.
Action
Get Recurring Profile
Returns one Givecloud recurring giving profile by ID.
Action
Get Sponsee
Returns one Givecloud sponsee by ID.
Action
Get Supporter
Returns one Givecloud supporter (donor) by ID, with addresses and memberships.
Action
List Contributions
Returns Givecloud contributions (donations and purchases), optionally filtered by date or one-time vs. recurring.
Action
List Posts
Returns the posts in a Givecloud feed (such as news or blog entries).
Action
List Products
Returns Givecloud products (donation forms and store items), optionally filtered by code or name.
Action
List Recurring Profiles
Returns Givecloud recurring giving profiles (monthly donations and other scheduled gifts).
Action
List Sponsees
Returns Givecloud sponsees (sponsored children or projects), optionally filtered by name or reference number.
Action
List Supporters
Returns Givecloud supporters (donors), optionally filtered by name, email or recurring-gift status.
Action
Update Sponsee
Updates an existing Givecloud sponsee; only the fields you supply change.

Each app on its own

Reviews

What our customers say

More into Givecloud

Questions

Clust and Givecloud, 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 Givecloud when something happens in Clust?

Any of Givecloud's 15 actions, including Create Sponsee, Update Sponsee, Get Contribution and Get Post. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from Givecloud to Clust?

Yes. When something happens in Givecloud, your agent can act in Clust too. This page covers both directions: Givecloud's triggers and Clust's actions are listed here as well.

Do I have to build a connector for Clust or Givecloud?

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 Givecloud 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.

Connect Clust and Givecloud

What do you want Clust and Givecloud to do together?

What Clust and Givecloud can do together

From Clust to Givecloud

From Givecloud to Clust

Triggers and actions 11 triggers · 41 actions

Each app on its own

What our customers say

More from Clust

More into Givecloud

Clust and Givecloud, answered

What can start an automation from Clust?

What can your agent do in Givecloud when something happens in Clust?

Can it also run from Givecloud to Clust?

Do I have to build a connector for Clust or Givecloud?

Can my AI client use Clust and Givecloud without building an automation?

What happens when something fails?

Is there a free plan?