Integration
Connect Voluum to Mx Technologies
When New Conversion fires in Voluum, your agent runs Add user in Mx Technologies. 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 Voluum and Mx Technologies 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 Voluum can start in Mx Technologies
When New Conversion in Voluum
then Add user in Mx Technologies
When New Conversion in Voluum
then Add account in Mx Technologies
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 Voluum and Mx Technologies
Triggers and actions 1 trigger · 55 actions
Trigger
New ConversionTriggers when a new conversion is recorded in Voluum, with its campaign, offer, traffic source, country, revenue and payout.
Action
Add affiliate networkCreates an affiliate network in Voluum, including its conversion tracking and postback settings.
Action
Add campaignCreates a campaign in Voluum for a traffic source, sending visitors to a flow, a direct URL or an inline flow.
Action
Add landerCreates a lander (landing page) in Voluum.
Action
Add traffic sourceCreates a traffic source in Voluum with its tracking variables and postback settings.
Action
Create OfferCreates an offer in Voluum with a URL, currency and payout, optionally tied to an affiliate network and country.
Action
Delete campaignDeletes (archives) a campaign in Voluum.
Action
Delete offerArchives an offer in Voluum. Fails when the offer is still used by an active campaign.
Action
Get CampaignReturns one Voluum campaign by its id, with its tracking URL, traffic source and redirect target.
Action
Get landerReturns a single Voluum lander by its id, including its name, URL, type, country and tags.
Action
Get OfferReturns one Voluum offer by its id, with its URL, payout, affiliate network and country.
Action
Get traffic sourceReturns a single traffic source with its configuration, postback URL and tracking variables.
Action
List affiliate networksReturns the affiliate networks in your Voluum account, optionally filtered by name, note, conversion tracking method or workspace.
Action
List CampaignsReturns campaigns in your Voluum account, optionally filtered by name or traffic source and paged.
Action
List flowsReturns the flows in your Voluum account, optionally filtered by name, note, redirect mode or workspace.
Action
List landersReturns the landers in your Voluum account, optionally filtered by name, type, URL, country, note, tag or workspace.
Action
List OffersReturns offers in your Voluum account, optionally filtered by name and paged.
Action
List traffic sourcesReturns the traffic sources configured in your Voluum account, including their custom variable names, postback URLs and cost tracking settings.
Action
Update campaignUpdates a campaign's name, cost model, traffic source, destination and settings; fields left blank keep their current values.
Action
Update landerUpdates an existing Voluum lander's name, URL, tracking and other settings, and returns the updated lander.
Action
Update offerUpdates an existing offer's name, URL, payout, currency and other settings. Voluum replaces the whole offer, so supply every value you want to keep.
Action
Add accountCreates a manual account for an MX user. Manual accounts sit under the Manual Institution member and never aggregate data from a financial institution.
Action
Add budgetCreates a budget for a category on an MX user.
Action
Add categoryCreate a custom category for a user.
Action
Add goalCreate a goal for a user.
Action
Add memberCreate a member (connection between a user and a financial institution) to start aggregation.
Action
Add transactionCreates a manual transaction on a manual account belonging to an MX user.
Action
Add userCreates a new MX user. The returned user guid is what other MX actions (such as Add member) use to identify the user.
Action
Aggregate memberStarts an aggregation for a member, pulling the latest account and transaction data from the connected institution. MX may skip the aggregation if the data was updated recently.
Action
Delete accountDelete a manually created account.
Action
Delete budgetDeletes a budget belonging to an MX user.
Action
Delete categoryDelete a custom category.
Action
Delete goalDelete a goal.
Action
Delete memberDelete a member connection.
Action
Delete userDelete a user.
Action
Get accountRead an account's attributes.
Action
Get budgetRetrieves a specific budget for an MX user.
Action
Get institutionRead an institution's attributes.
Action
Get memberRead a member's attributes and connection status.
Action
Get merchantReturns information about a particular merchant, such as its logo, name, and website.
Action
Get transactionRead a transaction's attributes.
Action
Get userRetrieves the attributes of a specific MX user.
Action
List accountsLists all accounts belonging to an MX user. Returns up to 1000 accounts in one call.
Action
List categoriesLists all categories for an MX user, including default and custom categories.
Action
List goalsLists all goals for an MX user.
Action
List institutionsLists financial institutions available through MX, optionally filtered by name, country and supported product.
Action
List membersList all members belonging to a user.
Action
List merchantsLists merchants in the MX system, optionally filtered by a name substring.
Action
List transactionsList all transactions for a user.
Action
Update accountUpdates an account belonging to a member. Manual accounts can have every field updated; aggregated accounts only accept changes to Is Business, Is Hidden and Metadata.
Action
Update budgetUpdate a specific budget.
Action
Update categoryUpdate a custom category.
Action
Update goalUpdates an existing savings or payoff goal for an MX user. Only the fields you fill in are changed.
Action
Update memberUpdates a member's credentials, id, metadata, background aggregation setting or use cases. At least one value to update must be supplied.
Action
Update transactionUpdate a transaction's category, description, or other editable attributes.
Action
Update userUpdate a user's attributes.
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 Voluum
Voluum to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Voluum to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
Voluum to WixThe Wix website builder gives businesses of any size the tools to create, manage and grow a fully integrated...
Voluum to LinkedInLinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...
Voluum to FacebookFacebook is a social media and advertising platform used by individuals and businesses to connect, share...
Voluum to AnthropicAnthropic builds Claude, a family of large language models.
More into Mx Technologies
Felt to Mx TechnologiesCloud-based GIS platform for creating interactive maps and dashboards from geospatial and database data.
HubSpot to Mx TechnologiesHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Mx TechnologiesSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Mx TechnologiesSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Mx TechnologiesGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Mx TechnologiesGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Voluum and Mx Technologies, answered
What can start an automation from Voluum?
Any of Voluum's 1 trigger in the catalog, including New Conversion. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Mx Technologies when something happens in Voluum?
Any of Mx Technologies's 35 actions, including Update account, Update budget, Update category and Update goal. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Mx Technologies to Voluum?
Mx Technologies has no triggers in the catalog today, so automations start in Voluum. If you need the other direction, ask: your agent reads Mx Technologies's API documentation and adds it.
Do I have to build a connector for Voluum or Mx Technologies?
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 Voluum and Mx Technologies 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.