Connect MuleSoft to Pigment and automate planning data flows
Run Pigment imports and exports through the MuleSoft flows your integration team already builds and governs. Bring source-system data into Pigment for analysis and forecasting, then send planning outputs back to other systems for reporting and data parity.

MuleSoft
Connect MuleSoft to Pigment to move planning data in and out of Pigment through the integration platform your IT team already runs.
Category
Integration method
Best for
Enterprise data integration · ERP and HR data import · Reporting and data parity
Why connect MuleSoft with Pigment?
- Run planning data through MuleSoft. Your integration team manages Pigment data flows in MuleSoft next to its other flows, so planning doesn't add another integration tool to maintain.
- Build on existing Anypoint tooling. Flows reach Pigment through the HTTP Request module that already ships with Anypoint Studio, so there's nothing extra to install.
- Limit each flow's data access. Pigment API keys act with their owner's access rights, so a flow only touches the data that person is allowed to see.
- Keep downstream systems on plan. Send planning results from Pigment back to source and reporting systems so they reflect what teams decided in Pigment.
What can you do with MuleSoft and Pigment?
- Forecast from current SAP revenue. Build a flow that moves revenue data from SAP into Pigment, so Finance can analyze it and update the forecast.
- Create Workday hires from approvals. Export completed hiring approvals from Pigment and send them to Workday to create the hiring record.
- Refresh saved Pigment imports. Trigger a saved integration, Metric, or List import from a MuleSoft flow, so the destination stays defined in Pigment.
- Catch failed loads early. Check each import's status and read its report of inserted, updated, deleted, and skipped rows, including why rows were skipped.
How the MuleSoft integration works
Your integration team adds Pigment to the MuleSoft flows it already runs, so planners get source data in their models without uploading files by hand. Flows call Pigment's public Import and Export APIs over HTTPS through MuleSoft's standard HTTP Request module, authenticated with Pigment API keys.
Imports need an import API key and an Import configuration ID, which defines where the data lands. Exports need an export API key, an application ID, and a view ID, and return flattened CSV data. Pigment also provides an optional sample Anypoint Studio project to start from.
Key capabilities
- Send extracts straight to Pigment. Push a CSV file from the flow to an Import configuration, with no manual upload step in between.
- Start from working examples. The optional sample project adds 3 Mule flows to Anypoint Studio: Import service, Export metrics and tables, and Export transaction lists.
- Export the views reports need. Pull data from Metric, List, and Table Blocks by view ID and route it to the systems your flows connect to.
- Fit exports to each target. Choose ISO 8601 or legacy date formats and a semicolon or comma delimiter for exported CSV files.
- Separate import and export access. Create dedicated Import and Export API keys, each with its own name and expiration date.
- Keep credentials out of flows. Store API keys, configuration IDs, and view IDs in a properties file, as Pigment recommends, instead of hard-coding them.
- Reduce key leak risk. Restrict where Pigment API keys can be used with an IP allow list.
- Trace activity to each key. The Audit Logs API records which API key performed events such as exports.
- Troubleshoot imports inside Pigment. Each API import appears in the Block's Update History, attributed to the person who created or last edited the import configuration.
Frequently Asked Questions
What data can MuleSoft export from Pigment?
MuleSoft can export views of Metric, List, and Table Blocks, using an export API key, an application ID, and a view ID. Exports come from the default Scenario and return flattened, unformatted CSV data. The export only includes data the key owner has access to.
What are the options for importing data into Pigment from MuleSoft?
A flow can push a CSV file directly to a Pigment Import configuration, or trigger an integration or Metric/List import that's already configured in Pigment. The flow can then check whether the import is in progress, completed, or failed. A detailed report lists inserted, updated, deleted, and skipped rows.
Can Finance forecast in Pigment from SAP data moved by MuleSoft?
Yes. Pigment's MuleSoft guide gives this as an example: a flow exports revenue data from SAP and imports it into Pigment for analysis and forecasting.
Can approved hiring plans in Pigment flow back to Workday?
Yes. A MuleSoft flow can export completed hiring approvals from Pigment and send them to Workday to create the hiring record. That keeps Workday consistent with the approved workforce plan.
Related integrations
See Pigment in action
The fastest way to understand Pigment is to see it in action. Sign up today and explore how agentic AI can transform the way you plan.

From 8 days to 4 min
Update P&L actuals & financial forecasting
80%
Time cut on data aggregation
12 hours
Saved per month on executive reporting
6 days faster
For scenarios creation and analysis