Source: https://joinfinn.com/integrations/nintex-process-manager

# Nintex Process Manager (Promapp)

## Nintex Process Manager (Promapp) + Finn.

Nintex Process Manager (Promapp) integration with Finn. Nintex Process Manager, formerly Promapp, documents business processes and the steps employees need to follow.

Business function: Workplace operations.

## What you can do with Nintex Process Manager (Promapp).

Nintex Process Manager, formerly Promapp, documents business processes and the steps employees need to follow.

### Take a process change from feedback to published instructions

Finn completes the document-control work behind an improved business process.

**Typically handled by:** Business process coordinator

**Starts when:** An employee submits feedback on a Nintex Process Manager process.

#### What Finn handles

1. Read the feedback and the exact process version, then collect the submitter's example and missing details.
2. Coordinate the subject-matter owners' chosen change and update the process activities, responsibilities and supporting links.
3. Route the revised process to its owner for publication approval and resolve the requested edits.
4. Publish the accepted version, notify the affected teams and close the feedback with the released change.

**The result:** The feedback ends in a published process update and a recorded response to its submitter.

### Run the scheduled process review

Finn handles the follow-up that keeps operating procedures current.

**Typically handled by:** Process governance administrator

**Starts when:** A documented process reaches its scheduled review date.

#### What Finn handles

1. Gather the current Nintex Process Manager version, owner, related documents and unresolved feedback.
2. Ask the relevant teams to confirm what changed in the actual working process.
3. Incorporate the owner's selected updates and obtain the review and publication decision.
4. Publish the resulting version or record the no-change review, then set the next review and close outstanding review tasks.

**The result:** The process has a current review record and the correct published instructions.

### Carry an improvement suggestion through implementation

Finn coordinates the administrative work behind an accepted improvement idea.

**Typically handled by:** Continuous improvement coordinator

**Starts when:** A team submits an improvement suggestion in the Improvements module.

#### What Finn handles

1. Collect the affected process, observed problem, supporting evidence and the submitter's intended outcome.
2. Route the suggestion to its owner for the actual priority, scope and spending decisions.
3. Create the selected implementation tasks in Asana, coordinate contributors and collect evidence that the change was delivered.
4. Update the process documentation, publish the owner's final instructions and close the improvement with its recorded result.

**The result:** The suggestion produces an implemented change and a closed improvement record.

### Close the corrective-action administration after a reported incident

Finn keeps the investigation record and follow-up work organized.

**Typically handled by:** Quality operations coordinator

**Starts when:** A team reports a process incident or quality issue.

#### What Finn handles

1. Create the Improvements record with the incident facts, affected process and evidence supplied by the reporting team.
2. Coordinate the designated investigators' information requests and record their findings without deciding technical or regulated conclusions.
3. Track the corrective actions they select in Asana and collect completion evidence from the responsible people.
4. Update the related process after owner approval and close the record when the authorized reviewer accepts the evidence.

**The result:** The incident has a complete investigation and corrective-action record with the reviewer's closure decision.

### Prepare the process evidence package for an internal review

Finn completes the collection and organization behind a process audit or management review.

**Typically handled by:** Process assurance coordinator

**Starts when:** An internal reviewer requests evidence for selected business processes.

#### What Finn handles

1. Gather the relevant Nintex Process Manager versions, ownership, review history and improvement records.
2. Collect the referenced execution evidence from SharePoint or the operating system that owns it.
3. Organize the package by the reviewer's requested process and period, recording any actual missing item.
4. Deliver the package, answer factual follow-up and create the reviewer's selected corrective tasks.

**The result:** The reviewer receives a traceable evidence package and a recorded follow-up list.

### Complete a process ownership handover

Finn runs the coordination when a procedure changes hands.

**Typically handled by:** Business process operations administrator

**Starts when:** A process owner leaves the role or responsibility moves to another team.

#### What Finn handles

1. Identify the affected Nintex Process Manager processes, active reviews and open improvements.
2. Read the replacement ownership decision and update the relevant process responsibilities and contacts.
3. Coordinate the incoming owner's handover of supporting documents, unresolved feedback and implementation work.
4. Publish any required responsibility change after approval and record the accepted handover.

**The result:** The processes and their open work have an acknowledged new owner.

### Turn a process rollout into completed team adoption work

Finn coordinates the communication and learning administration around a new procedure.

**Typically handled by:** Operational change coordinator

**Starts when:** A process owner publishes a procedure that changes how a team works.

#### What Finn handles

1. Read the published Nintex Process Manager process and identify the teams and roles affected.
2. Send the final instructions and organize the required briefings or training through Outlook and the connected learning system.
3. Collect attendance, acknowledgments and practical questions, recording feedback against the correct process version.
4. Resolve routine questions and bring necessary amendments back through the process owner's publication workflow.

**The result:** The procedure rollout has completed communications and learning records, with feedback connected to its owner.

## Connection setup

Contact Finn to discuss the records your workflow needs and the actions you want it to perform.

Your team chooses what Finn can access, what agents can change, and when a person must approve the work. The connection needs the appropriate account access and permissions from Nintex Process Manager (Promapp).

## Explore Finn

- [Agents](https://joinfinn.com/agents): Help customers. Work with your team. Finish the job.
- [Systems](https://joinfinn.com/systems): Business apps for the work behind the conversation.
- [AI Gateway](https://joinfinn.com/ai-gateway): Control connected AI apps, models, access, and spending.

[All integrations](https://joinfinn.com/integrations)

[Discuss this integration](https://joinfinn.com/contact)

[Discuss your workflow](https://joinfinn.com/contact) · [How it works](https://joinfinn.com/demo/app/#/w/borough/overview) · [Get started](https://joinfinn.com/app/#/signup)