Integration
Connect PocketSmith and RadiusOS
When something happens in PocketSmith or RadiusOS, your agent does the next thing in the other. Describe it 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 PocketSmith and RadiusOS 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 PocketSmith and RadiusOS can do together
From PocketSmith to RadiusOS
When New transaction in PocketSmith
then Create Contact in RadiusOS
When New transaction in PocketSmith
then Create Task in RadiusOS
From RadiusOS to PocketSmith
When New Contact in RadiusOS
then Add category in PocketSmith
When New Contact in RadiusOS
then Add transaction in PocketSmith
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 PocketSmith and RadiusOS
Triggers and actions 2 triggers · 16 actions
Trigger
New transactionFires when a new transaction appears in the authorised user's PocketSmith accounts.
Action
Add categoryCreate a new category for the authorised user.
Action
Add transactionCreate a new transaction in a PocketSmith transaction account.
Action
Delete categoryDelete a category by id.
Action
Delete transactionDelete a transaction by id.
Action
Get accountRetrieve a single account by id.
Action
Get categoryRetrieve a single category by id.
Action
Get transactionRetrieve a single transaction by id.
Action
List accountsList all bank/investment accounts for the authorised user.
Action
List categoriesList all categories for the authorised user.
Action
List transaction accountsList the transaction accounts (e.g. individual bank feeds) belonging to the authorised user, needed as the parent for creating transactions.
Action
List transactionsList transactions for the authorised user, with filters for date range, category, account, type and search text.
Action
Update categoryUpdate an existing category's title, colour or parent.
Action
Update transactionUpdate fields on an existing transaction (amount, payee, date, category, note, labels).
Trigger
New ContactTriggers when a new contact is created in RadiusOS.
Action
Create ContactAdd a new contact to your RadiusOS workspace.
Action
Create TaskCreates a task in the connected RadiusOS workspace, optionally linked to a contact.
Action
Move Contact to StageMoves a contact to a different pipeline stage in the workspace.
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 PocketSmith
PocketSmith to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
PocketSmith to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
PocketSmith to StripeStripe is a payment processing platform for online businesses.
PocketSmith to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
PocketSmith to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
PocketSmith to NotionA new tool that blends your everyday work apps into one. It's the all-in-one workspace for you and your team.
More into RadiusOS
HubSpot to RadiusOSHubSpot is your all-in-one stop for all of your marketing software needs.
Gmail to RadiusOSGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to RadiusOSGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to RadiusOSGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to RadiusOSMailchimp marketing automation and email platform.
QuickBooks Online to RadiusOSQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Questions
PocketSmith and RadiusOS, answered
What can start an automation from PocketSmith?
Any of PocketSmith's 1 trigger in the catalog, including New transaction. Describe the moment in plain language and your agent picks the right one.
What can your agent do in RadiusOS when something happens in PocketSmith?
Any of RadiusOS's 3 actions, including Create Contact, Create Task and Move Contact to Stage. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from RadiusOS to PocketSmith?
Yes. When something happens in RadiusOS, your agent can act in PocketSmith too. This page covers both directions: RadiusOS's triggers and PocketSmith's actions are listed here as well.
Do I have to build a connector for PocketSmith or RadiusOS?
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.