Build solutions, not workarounds.
What do you want Moxo and Softwium 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 Moxo can start in Softwium
When New Account in Moxo
then Add book in Softwium
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 Moxo and Softwium
Triggers and actions 2 triggers · 42 actions
- New Account
Triggers when a new client account is created in Moxo.
- New User
Triggers when a new user (team member or client) is added to Moxo.
- Add Data Table Record
Adds a record to a data table.
- Cancel Flow
Cancels a running flow.
- Complete Step
Completes a step in a flow, optionally with a note.
- Create Account
Creates a client account (company) in Moxo.
- Create Group Conversation
Creates a group conversation with the given participants.
- Create User
Creates an internal team member or an external (client) user in Moxo, optionally sending an invitation.
- Deactivate User
Deactivates a Moxo user so they can no longer sign in.
- Get Account
Returns one client account with its users.
- Get Action
Returns one action with its status and assignees.
- Get Flow
Returns one flow with its template, status and progress.
- Get User
Returns one Moxo user by ID, with their name, email, kind, status, accounts and personas.
- List Accounts
Returns the client accounts (companies) in your Moxo organization.
- List Conversations
Returns your conversations.
- List Data Tables
Returns your data tables with their columns.
- List Flows
Returns flows, optionally filtered by status, template, account or search term.
- List Templates
Returns the flow templates in your Moxo organization.
- Post Flow Chat Message
Posts a chat message in a flow's conversation.
- Send Action
Sends a standalone action (form, approval, acknowledgement, file request, to-do and more) to one or more people.
- Send Conversation Message
Sends a message to a conversation.
- Start Flow
Starts a new flow from a published Moxo template, optionally naming it and setting a due date.
- Update Account
Updates a client account's name, domain or status.
- Update User
Updates a Moxo user's profile: name, title, department, phone or account.
- Add book
creates a new fake book, returns HTTP 201. Note: the vendor does not actually persist writes (test/mock API).
- Add currency
creates a new fake currency, returns HTTP 201. Note: the vendor does not actually persist writes (test/mock API).
- Add people
creates a new fake person record, returns HTTP 201. Note: the vendor does not actually persist writes (test/mock API).
- Add pokemon
creates a new fake pokemon, returns HTTP 201. Note: the vendor does not actually persist writes (test/mock API).
- Delete book
deletes the fake book with the given ID. Note: the vendor does not actually persist writes (test/mock API).
- Delete currency
deletes the fake currency with the given ID. Note: the vendor does not actually persist writes (test/mock API).
- Delete people
deletes the fake person record with the given ID. Note: the vendor does not actually persist writes (test/mock API).
- Delete pokemon
deletes the fake pokemon with the given ID. Note: the vendor does not actually persist writes (test/mock API).
- Get book
returns the fake book with the given ID, or HTTP 404 if not found.
- Get currency
returns the fake currency with the given ID, or HTTP 404 if not found.
- Get people
returns the fake person record with the given ID, or HTTP 404 if not found.
- Get pokemon
returns the fake pokemon with the given ID, or HTTP 404 if not found.
- List books
returns all fake books (optional ?limit=N query param to cap the count). Read-only test data, no auth.
- List currencies
returns all fake currencies (optional ?limit=N query param to cap the count). Read-only test data, no auth.
- List peoples
returns all fake people records (optional ?limit=N query param to cap the count). Read-only test data, no auth.
- List pokemons
returns all fake pokemon records (optional ?limit=N query param to cap the count). Read-only test data, no auth.
- Update book
partially updates the fake book with the given ID. Note: the vendor does not actually persist writes (test/mock API).
- Update currency
partially updates the fake currency with the given ID. Note: the vendor does not actually persist writes (test/mock API).
- Update people
partially updates the fake person record with the given ID. Note: the vendor does not actually persist writes (test/mock API).
- Update pokemon
partially updates the fake pokemon with the given ID. Note: the vendor does not actually persist writes (test/mock API).
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 Moxo
Moxo to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Moxo to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Moxo to StripeStripe is a payment processing platform for online businesses.
Moxo to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Moxo to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Moxo to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Softwium
HubSpot to SoftwiumHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to SoftwiumGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to SoftwiumGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SoftwiumGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Moxo and Softwium, answered
What can start an automation from Moxo?
Any of Moxo's 2 triggers in the catalog, including New Account and New User. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Softwium when something happens in Moxo?
Any of Softwium's 20 actions, including Update book, Update currency, Update people and Update pokemon. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Softwium to Moxo?
Softwium has no triggers in the catalog today, so automations start in Moxo. If you need the other direction, ask: your agent reads Softwium's API documentation and adds it.
Do I have to build a connector for Moxo or Softwium?
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 Moxo and Softwium 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.