Integration
Connect Community to Agentset
When New Member fires in Community, your agent runs Get document in Agentset. 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 Community and Agentset 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)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 Community can start in Agentset
When New Member in Community
then Get document in Agentset
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 Community and Agentset
Triggers and actions 2 triggers · 28 actions
- New Member
Triggers when a new member joins your community.
- New Subcommunity
Triggers when a new subcommunity is created in your community.
- Assign Member to Subcommunities
Adds a member to one or more subcommunities; existing memberships are kept.
- Block Member
Blocks a member permanently so they stop receiving messages.
- Create Member
Creates a member in your community from their phone number, with optional profile details.
- Create Subcommunity
Creates a subcommunity (a segment of members) in your community.
- Delete Member
Permanently deletes a member and their data from your community.
- Delete Subcommunity
Permanently deletes a subcommunity; its members stay in your community.
- Find Member
Finds the member with a given phone number or email address.
- Get Member
Returns one member of your community by ID, with their profile and subscription state.
- Get Subcommunity
Returns one subcommunity by ID, with its title and member count.
- List Subcommunities
Returns the subcommunities in your community, newest first.
- List Subcommunity Members
Returns the members currently in a subcommunity, newest first.
- Remove Member from Subcommunities
Removes a member from one or more subcommunities; the member stays in your community.
- Report Member
Reports a member to Community with a reason; the member is not changed.
- Update Member
Updates a member's profile fields; fields left blank are not changed.
- Update Subcommunity
Updates a subcommunity's title, description or color; blank fields are not changed.
- Add ingest job
Create an ingest job (text, file or URL payload).
- Add namespace
Create a namespace.
- Delete document
Delete a document.
- Delete ingest job
Delete an ingest job.
- Find chunks in namespace
Search a namespace (semantic search with query, topK, filters).
- Generate upload URL
Create presigned URL for file upload.
- Get document
Retrieve a document.
- Get ingest job
Retrieve an ingest job (status).
- Get namespace
Retrieve a namespace by id.
- List documents
Retrieve a list of documents.
- List ingest jobs
Retrieve a list of ingest jobs.
- List namespaces
Retrieve a list of namespaces.
- Update namespace
Update a namespace.
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 Community
Community to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Community to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Community to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Community to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Community to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Community to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Agentset
Questions
Community and Agentset, answered
What can start an automation from Community?
Any of Community's 2 triggers in the catalog, including New Member and New Subcommunity. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Agentset when something happens in Community?
Any of Agentset's 13 actions, including Update namespace, Add ingest job, Add namespace and Find chunks in namespace. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Agentset to Community?
Agentset has no triggers in the catalog today, so automations start in Community. If you need the other direction, ask: your agent reads Agentset's API documentation and adds it.
Do I have to build a connector for Community or Agentset?
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 Community and Agentset 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.