ApivomApivom
Get Demo

MuleSoft Automation (RPA & Composer) API Connector

MuleSoft's automation platform APIs — RPA process management, robots and run results, user tasks and backlogs, process evaluation and finance analysis, process monitoring, Composer flows and connections, user analytics, alert targets and organisation users — registered in Apivom Atlas as 97 routes on anypoint.mulesoft.com.

What you can do

  • RPA process management: categories and processes, BPMN export, production run configurations, robot run results and analysis packages
  • Human-in-the-loop: open and personal user tasks, claim, complete or reject a task, personal and team backlogs, process board tasks
  • Robot management: robots, robot API keys, service times; monitoring of robot state, session queues and streamable processes
  • Process evaluation templates, criteria and evaluations; finance analysis and usage summary; deployment maps for test and production
  • Composer: flows and connections through the citizen API; user analytics dashboard; e-mail alert targets; organisation users, invites and roles
  • 97 routes (62 read-only), authenticated with an Anypoint Connected App

Use cases

  • Robot runs on the customer timeline — Read run results and analysis packages for the processes that serve a customer and attach failures or throughput to the account record for the next review.
  • Human tasks handled from one inbox — List open user tasks, claim them and complete or reject them from an Apivom workflow so the people who resolve exceptions do not need a second console.
  • Automation portfolio and ROI reporting — Pull process categories, evaluations and the finance analysis per process on a schedule to report which automations pay off and which robots are under-used.

MuleSoft's automation products — RPA for attended and unattended bots, Composer for clicks-not-code flows — are managed from the same Anypoint control plane as the integration platform, and their APIs expose the whole operating model: processes in categories with BPMN export and production run configurations, the robots that execute them with API keys and service windows, run results and analysis packages per robot, the user tasks a process hands to a person — open tasks, backlogs, claim, complete or reject — plus evaluation templates and criteria, finance analysis per process, usage summaries, deployment maps and live monitoring of robot state and session queues. Composer flows and connections are reached through the citizen API, with user analytics, alert targets and organisation users alongside. Apivom Atlas catalogues 97 of these routes, 62 of them read-only, with the Connected App credential of your Anypoint organisation. No Apivom product workflow uses MuleSoft RPA or Composer today — Apivom's own portal automations run on Apivom's platform — so the connector is available to tenants who operate MuleSoft robots and want their runs, tasks or evaluations visible from an Apivom workflow, scoped per customer.

Authentication

A Connected App on your Anypoint Platform organisation (client id + secret) with the scopes this API family needs. The caller gets a token at /accounts/api/v2/oauth2/token (client credentials) and sends it as Bearer; Apivom Atlas forwards, logs, stores nothing. Secret encrypted in your Iris tenant.

Frequently asked questions

Can I switch this connector on today?

The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.

Does this cover MuleSoft Anypoint Platform too?

No. This connector is the RPA and Composer surface. Exchange, API Manager, CloudHub, Design Center and Access Management are the separate MuleSoft Anypoint Platform connector in this catalogue; both use the same Connected App credential model.

Can Apivom trigger a robot or build a Composer flow?

The catalogued routes manage processes, robots, tasks and flows; starting a process run is part of the process-management family and a Composer flow is created through the citizen API. Any such automation is scoped per customer — none runs in an Apivom product today.

Does Apivom charge per API call for this connector?

No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.

Where are my credentials stored and who can see the traffic?

Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.

More Atlas integrations

AI integration guide (llms.txt)

Machine-readable markdown — feed it to your AI assistant as integration instructions.