Integration
Connect Carbon Voice to Code::Stats
When New Action Item Created fires in Carbon Voice, your agent runs Get user in Code::Stats. 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 Carbon Voice and Code::Stats to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Carbon Voice can start in Code::Stats
When New Action Item Created in Carbon Voice
then Get user in Code::Stats
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 Carbon Voice and Code::Stats
Triggers and actions 7 triggers · 25 actions
- Action Item Deleted
Triggers when an action item is deleted.
- New Action Item Created
Triggers when an action item is created.
- New AI Prompt Response Generated
Triggers when AI Prompt happened to a message(s).
- New AI System Prompt Response Generated
Triggers when AI System Prompt happened to a message(s).
- New Message Posted to Conversation
Triggers when a message is posted into a conversation.
- New Message Received
Triggers when a message is received in any conversation (Not includes your own messages).
- New Voice Memo Created
Triggers when a voice memo is created.
- Add folder
Create a folder.
- Add Link Attachments to Message
Add one or more link attachments to a Message.
- Create Action Item
Create an Action Item.
- Create AI Prompt Response
Creates a new Ai response for given prompt and message(s).
- Create Message Share Link
Create a share link for a message.
- Create Voice Memo
Create a Voice Memo from audio file, transcript or links.
- Delete action item
Delete an action item.
- Delete folder
Delete a folder and nested content.
- Find users by email, phone or name
Search users by email, phone or name.
- Get AI Prompt Response
Returns one AI prompt response (prompt, generated responses per language, source messages) by id.
- Get conversation
Get a conversation by id.
- Get message
Get a message by id.
- Get Message Share Link
Returns one message share link by id.
- Get user
Get a user by id.
- List AI Prompts
/prompts (optional owner_type=user|workspace|system, workspace_id) — lists the AI prompts available to the account, returning each prompt's id. Read-only.
- List conversations
List all of the user's conversations (id and name only).
- List conversation users
List users in a conversation.
- List folders
List root folders.
- List messages
List messages.
- List workspaces
List workspaces the user can access.
- Send Direct Message to User(s)
Send a Direct Message to specific User(s).
- Send Message to Conversation
Send a Message to specific Conversation.
- Update Action Item
Update an Action Item.
- Update folder
Rename a folder.
- Get user
Retrieve a public user's profile (total XP, new XP in last 12h, per-machine, per-language and per-date XP).
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 Carbon Voice
Carbon Voice to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Carbon Voice to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Carbon Voice to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Carbon Voice to Google SheetsGoogle Sheets
Carbon Voice to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Carbon Voice to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Code::Stats
Questions
Carbon Voice and Code::Stats, answered
What can start an automation from Carbon Voice?
Any of Carbon Voice's 7 triggers in the catalog, including New Action Item Created, New AI Prompt Response Generated, New AI System Prompt Response Generated and New Message Posted to Conversation. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Code::Stats when something happens in Carbon Voice?
Any of Code::Stats's 1 action, including Get user. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Code::Stats to Carbon Voice?
Code::Stats has no triggers in the catalog today, so automations start in Carbon Voice. If you need the other direction, ask: your agent reads Code::Stats's API documentation and adds it.
Do I have to build a connector for Carbon Voice or Code::Stats?
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.
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.