Integration
Connect OneDeck to Code::Stats
When Record Created fires in OneDeck, 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 OneDeck 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 OneDeck can start in Code::Stats
When Record Created in OneDeck
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 OneDeck and Code::Stats
Triggers and actions 2 triggers · 15 actions
Trigger
Record CreatedTriggers when a new record is created on the selected OneDeck board.
Trigger
Record UpdatedTriggers when a record on the chosen OneDeck board is created or updated.
Action
Add attachmentUploads a file and attaches it to a record on a OneDeck board.
Action
Add boardCreates a new board in a OneDeck workspace, with a default table view.
Action
Add fieldAdds a new field (column) to a OneDeck board. The field is added to every view of the board.
Action
Add workspaceCreates a new workspace in your OneDeck account.
Action
Create RecordCreates a new record on a OneDeck board, with a name and optional field values.
Action
Find RecordFinds records on a OneDeck board that match a search text, optionally narrowed by field filters.
Action
Get recordReturns one record from a board, including its field values, attachments and share link.
Action
List fieldsReturns every field defined on a OneDeck board, including its type and option settings.
Action
List recordsReturns the records on a OneDeck board, optionally filtered by field values or search text.
Action
List usersReturns every user in the OneDeck account with their name, email, status and role.
Action
List workspacesReturns every workspace in the OneDeck account, with each workspace's id, name and icon.
Action
Update boardRenames a board, moves it to another workspace, or both.
Action
Update RecordUpdates the name and field values of an existing record on a OneDeck board.
Action
Update workspaceRenames a workspace or changes its icon. Only the values you fill in are changed.
Action
Get userRetrieve 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 OneDeck
OneDeck to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
OneDeck to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
OneDeck to StripeStripe is a payment processing platform for online businesses.
OneDeck to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
OneDeck to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
OneDeck to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Code::Stats
HubSpot to Code::StatsHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Code::StatsSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Code::StatsSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Code::StatsGoogle Sheets
Gmail to Code::StatsGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Code::StatsGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
OneDeck and Code::Stats, answered
What can start an automation from OneDeck?
Any of OneDeck's 2 triggers in the catalog, including Record Created and Record Updated. 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 OneDeck?
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 OneDeck?
Code::Stats has no triggers in the catalog today, so automations start in OneDeck. 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 OneDeck 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.