Informatica (Private Preview)
Overview
Monte Carlo integrates with Informatica Intelligent Cloud Services (IICS) to provide run history and mapping task failure alerts for your Data Integration mapping tasks. Monte Carlo discovers your mapping tasks, adds them to the asset catalog as jobs, and collects their runs, so you can see when a mapping task last ran, whether it succeeded, and how many rows it processed.
When a mapping task fails, Monte Carlo can raise it as an alert, so you get centralized incident triage, notification routing, and reporting across all your data and system issues.
This integration is in private preview. Contact your Monte Carlo representative to enable it.
Feature Support
| Category | Capability | Support |
|---|---|---|
| Mapping tasks | Mapping task failure alerts | ✅ |
| Mapping tasks | Webhook triggered collection | ❌ |
| Mapping tasks | Mapping task run history | ✅ |
| Taskflows | Taskflow collection | ❌ |
| Lineage | Table-to-Table lineage | ❌ |
| Lineage | Column-level lineage | ❌ |
What Monte Carlo Ingests
Monte Carlo collects the following from your IICS organization:
Mapping tasks
Each Data Integration mapping task is collected as a job asset, including mapping tasks that run outside a taskflow. For each mapping task, Monte Carlo captures the mapping it runs and its project and folder path.
Taskflows aren't collected. A mapping task that runs as part of a taskflow is still collected on its own.

Runs
For each mapping task run, Monte Carlo captures:
- status (success, warning, failed, or stopped)
- start and end times
- who or what started the run
- success and failed row counts
- error message (if failure)
- a link to the run in IICS


Prerequisites
Before adding the integration, you'll need:
- A Monte Carlo account with permission to add integrations
- An IICS user, or an OAuth application in your identity provider, with read access to all Data Integration projects and folders that contain your mapping tasks
We recommend creating a dedicated service user for Monte Carlo rather than reusing one created for another purpose. A dedicated user makes it easier to audit API usage, scope permissions precisely, and rotate credentials without affecting other systems.
Installation
Step 1: Add the Informatica Integration in Monte Carlo
- In Monte Carlo, navigate to Settings → Integrations.
- Click Create and select Informatica from the Orchestration section.
- Fill in the form for your authentication method. Monte Carlo supports two methods:
- OAuth 2.0, through an external identity provider
- Informatica user & password
The Base login URL depends on the Informatica POD (point of deployment) for your organization, for example https://dm-us.informaticacloud.com. See the Informatica documentation to find yours.
OAuth 2.0

| Field | Value |
|---|---|
| Integration name | A name for the integration in Monte Carlo. |
| Base login URL | The URL used to authenticate to the IICS REST APIs for your POD. |
| Authentication type | OAuth 2.0 |
| Informatica org ID | Your IICS organization ID. |
| Token endpoint URL | The URL used to obtain an OAuth token from your identity provider. |
| Grant type | Client credentials or Password. |
| OAuth client ID | The client ID of the application registered in your identity provider. |
| OAuth client secret | The client secret of the application registered in your identity provider. |
| IDP username | The identity provider user's username. Only for the Password grant. |
| IDP password | The identity provider user's password. Only for the Password grant. |
| Scope | Optional. The OAuth scope to request, if your identity provider needs one. |
Informatica user & password

| Field | Value |
|---|---|
| Integration name | A name for the integration in Monte Carlo. |
| Base login URL | The URL used to authenticate to the IICS REST APIs for your POD. |
| Authentication type | Informatica user & password |
| Username | The IICS user's username. |
| Password | The IICS user's password. |
- Save the integration. Monte Carlo verifies that it can authenticate to the IICS REST APIs.
Once the integration is saved, Monte Carlo begins collecting your mapping tasks and their runs on an hourly schedule.
Step 2: Confirm data is flowing
- In Monte Carlo, navigate to Assets and search for one of your mapping tasks.
- Open the asset and verify you can see recent runs with their status and duration.
Step 3: Create a job monitor
To be alerted when a mapping task fails, create a job monitor on your Informatica integration. A job monitor can cover all mapping tasks or mapping tasks you pick, and sends alerts to the audiences you choose. See Job monitors for setup steps.
FAQs
Q: How often does Monte Carlo collect Informatica data?
Collections run hourly. Informatica doesn't support webhook-triggered collection, so a failed run is picked up on the next hourly collection.
Q: Why don't I see my taskflows?
This integration collects mapping tasks, not the taskflows they may be part of. Each mapping task in a taskflow is still collected and monitored on its own.
Q: Does Monte Carlo show lineage for Informatica?
Not yet. Mapping tasks appear as job assets with run history, but Monte Carlo doesn't derive lineage between the tables they read and write.
Q: Do mapping tasks disappear from the Assets page if they haven't run recently?
No. A mapping task stays on the Assets page after it stops running, along with its past runs.
Updated 16 days ago
