> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/informatica.md).

# Informatica

Connect to Informatica Intelligent Data Management Cloud to orchestrate Cloud Data Integration from your AI workflows: start mapping tasks on demand, poll a run until it finishes, stop a run that is going wrong, browse the tasks in the org, and pull run history for reporting.

### Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector                         | Authentication |
| --------------------------------- | -------------- |
| Informatica (Username & Password) | Credentials    |

#### Informatica (Username & Password)

Connect to Informatica Intelligent Data Management Cloud to run and monitor Cloud Data Integration mapping tasks. Informatica offers no API key or scoped token for this API, so the connection signs in as an IDMC user and can reach whatever that user can; a dedicated service user with only the Data Integration Task Executor role is the narrower choice.

**Set up in Informatica**

1. Prepare the Informatica account or service that the workflow will access. Grant access to the required resources and operations.
2. **Region (POD):** The IDMC region your organization runs in, taken from the host you sign in at: in <https://dm-us.informaticacloud.com> the region is 'dm-us'. Other examples are dm-em, dm-uk, dm-ap, dm1-apse and dm2-us. Informatica has no endpoint that discovers this, so ask your organization administrator or check the Informatica Product Availability Matrix if you are unsure.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **Informatica (Username & Password)**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field | Required | What to enter                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
| ------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Region (POD)  | Yes      | The IDMC region your organization runs in, taken from the host you sign in at: in <https://dm-us.informaticacloud.com> the region is 'dm-us'. Other examples are dm-em, dm-uk, dm-ap, dm1-apse and dm2-us. Informatica has no endpoint that discovers this, so ask your organization administrator or check the Informatica Product Availability Matrix if you are unsure. [Provider instructions](https://onlinehelp.informatica.com/iics/dev/admin/en/tt-cloud-rest-api/login.html). |
| Username      | Yes      | The IDMC user this connection acts as. Informatica offers no API key or scoped token for this API, so the connection signs in as a real user and can reach whatever that user can. Prefer a dedicated service user holding only the Data Integration Task Executor role, with execute permission on just the projects whose tasks the workflow needs, over a human administrator account.                                                                                              |
| Password      | Yes      | Password for the IDMC user. Stored encrypted and never sent anywhere else.                                                                                                                                                                                                                                                                                                                                                                                                             |

#### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

### Use an action

1. Add the required **Informatica** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

### Actions

#### Run Mapping Task

Start an Informatica mapping task now and get back the run id to track it.

**Inputs**

| Field                         | Type            | Required | Description                                                                                |
| ----------------------------- | --------------- | -------- | ------------------------------------------------------------------------------------------ |
| Mapping task                  | select (string) | No       | The mapping task to run. Options load from the selected connection.                        |
| Show advanced options         | boolean         | No       | Show the Default-folder task id, concurrency and parameter-file overrides. Default: false. |
| Task ID (Default folder only) | string          | No       | For a task in the Default folder, identify it by its plain task id instead.                |
| Allow a concurrent run        | boolean         | No       | Start a run even if this task is already running. Default: false.                          |
| Parameter file name           | string          | No       | Override the parameter file this run reads.                                                |
| Parameter file directory      | string          | No       | Directory on the Secure Agent that holds the parameter file.                               |

**Outputs**

| Field             | Type    | Description                                                             |
| ----------------- | ------- | ----------------------------------------------------------------------- |
| Run ID            | string  | Id of the run that was just started, or of the run already in flight.   |
| Already running   | boolean | True when this returned an in-flight run instead of starting a new one. |
| Task ID           | string  | Id of the task that was started.                                        |
| Task name         | string  | Name of the task that was started.                                      |
| Task type         | string  | Informatica task type of the started run.                               |
| Federated task id | string  | Federated id of the task that was started.                              |

#### Get Job Status

Check whether a mapping task run is still going, and whether it succeeded.

**Inputs**

| Field        | Type            | Required | Description                                                             |
| ------------ | --------------- | -------- | ----------------------------------------------------------------------- |
| Mapping task | select (string) | Yes      | The task the run belongs to. Options load from the selected connection. |
| Run ID       | string          | Yes      | The run to check.                                                       |

**Outputs**

| Field               | Type    | Description                                              |
| ------------------- | ------- | -------------------------------------------------------- |
| Status              | string  | One normalised run status.                               |
| Finished            | boolean | True once the run has reached a state it will not leave. |
| Status source       | string  | Which Informatica surface answered.                      |
| Provider state      | string  | The untranslated value Informatica returned.             |
| Run ID              | string  | The run this status describes.                           |
| Task ID             | string  | The task this run belongs to.                            |
| Task name           | string  | Name of the task that ran.                               |
| Error message       | string  | Why the run failed, when Informatica reported a reason.  |
| Started at          | string  | When the run started.                                    |
| Finished at         | string  | When the run finished.                                   |
| Source rows read    | integer | Rows successfully read from the source.                  |
| Source rows failed  | integer | Rows that failed on read.                                |
| Target rows written | integer | Rows successfully written to the target.                 |
| Target rows failed  | integer | Rows that failed on write.                               |
| Started by          | string  | Who or what started the run.                             |

#### Stop Job

Stop the run currently in progress for a mapping task. IMPORTANT: Informatica cannot stop one nominated run, only the task's current one.

**Inputs**

| Field                         | Type            | Required | Description                                                                                |
| ----------------------------- | --------------- | -------- | ------------------------------------------------------------------------------------------ |
| Mapping task                  | select (string) | No       | The mapping task whose current run should stop. Options load from the selected connection. |
| Clean stop                    | boolean         | No       | Ask Informatica for a clean stop rather than an immediate one. Default: false.             |
| Show advanced options         | boolean         | No       | Show the Default-folder task id override. Default: false.                                  |
| Task ID (Default folder only) | string          | No       | For a task in the Default folder, identify it by its plain task id instead.                |

**Outputs**

| Field                | Type    | Description                                       |
| -------------------- | ------- | ------------------------------------------------- |
| Stop accepted        | boolean | True when Informatica accepted the stop request.  |
| Task identifier sent | string  | The task identifier that was sent to Informatica. |
| Task type            | string  | Informatica task type that was sent.              |
| Clean stop           | boolean | Whether a clean stop was requested.               |

#### List Tasks

Browse the tasks in this Informatica org, with their run history ids.

**Inputs**

| Field       | Type            | Required | Description                                                                                                                                                                                   |
| ----------- | --------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Task type   | select (string) | Yes      | Which kind of Informatica task to list. Available values: Mapping task (MTT), Masking task (DMASK), Replication task (DRS), Synchronization task (DSS), PowerCenter task (PCS). Default: MTT. |
| Max results | integer         | No       | Most tasks to return. Minimum: 1. Maximum: 500. Default: 50.                                                                                                                                  |

**Outputs**

| Field          | Type          | Description                                                       |
| -------------- | ------------- | ----------------------------------------------------------------- |
| Tasks          | object\_array | The tasks found.                                                  |
| Tasks returned | number        | How many tasks are in the result.                                 |
| Truncated      | boolean       | True when the org has more tasks of this type than were returned. |

#### Get Activity Log

Pull recent Informatica run history for reporting or an audit.

**Inputs**

| Field        | Type            | Required | Description                                                                |
| ------------ | --------------- | -------- | -------------------------------------------------------------------------- |
| Mapping task | select (string) | No       | Only show runs of this task. Options load from the selected connection.    |
| Max results  | integer         | No       | Most log entries to return. Minimum: 1. Maximum: 1000. Default: 50.        |
| Offset       | integer         | No       | Continue a previous listing from where it stopped. Minimum: 0. Default: 0. |
| Run ID       | string          | No       | Only show this one run.                                                    |

**Outputs**

| Field            | Type          | Description                                |
| ---------------- | ------------- | ------------------------------------------ |
| Log entries      | object\_array | The run history found.                     |
| Next offset      | number        | Pass back as Offset to fetch more history. |
| Entries returned | number        | How many entries are in the result.        |

### Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/informatica.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
