> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/review-partner-applications/automate-partner-application-processing/workflow-best-practices-and-faqs.md).
# Workflow Best Practices & FAQs
Take the PXA course
{% embed url="" %}
## Workflows top questions
How can I keep track of accepted applications?
To keep track of which partners your workflow rules have accepted, [create a partner group](/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/partner-groups/create-and-manage-partner-groups.md) for each workflow and assign accepted partners to that partner group when [creating or editing the workflow](/brand/what-would-you-like-to-learn-about/platform-features/review-partner-applications/automate-partner-application-processing/create-workflows-to-automatically-process-partner-applications.md).
What are some good condition combinations to use when setting up workflows?
This depends on your business needs. Here are two sets of conditions that work well together:
1. **Business Models, Partner Size, and Partner Country**
Using these conditions, you can specify the size and type of partner you want to work with and where they should be situated.
{% hint style="info" %}
**Example:** Let's say you want to partner with large content publishers in the United Kingdom, you can set your conditions as follows.
{% endhint %}
2. **Template Terms and Partner Country**
Using these conditions, you can specify on which terms you want to work with partners in specific countries.
{% hint style="info" %}
**Example:** Let’s say you want to work with Coupon partners based in the US.
{% endhint %}
{% hint style="success" %}
**Note:** Include the **Assign Group** and **Process Application** action types.
{% endhint %}
How do I undo workflow-processed partner applications?
If a workflow accepted or rejected an application and you want a different outcome, select **Review Decision** on that application in the *Processed* tab of the *Applications* screen. You can accept a previously rejected application, or expire the contract of a previously accepted one.
To find the applications a specific workflow processed, use the **Groups** and **Status** filters.
See [Change a decision on a processed application](/brand/what-would-you-like-to-learn-about/platform-features/review-partner-applications/process-partners-in-bulk-and-reverse-rejections.md#change-a-decision-on-a-processed-application) for the steps.
## Workflow creation best practices
Below are tips on how to best make use of workflows to process partner applications:
* Keep Workflows mutually exclusive from each other. You can do this by ensuring that conditions across Workflows don't contradict each other. If you have contradicting workflow rules, the action in the most recently updated Workflow will be used.
* When you're first starting up with Workflows, have the Workflow add processed partners to a [unique group](/brand/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/partner-groups/create-and-manage-partner-groups.md) so you can easily find them on the [Applications](https://app.impact.com/secure/advertiser/engage/contracts/activity/adv-manage-pending-public-ios-v2-flow.ihtml) screen with the use of the *Group* filter.
* Keep your first few Workflows basic and broad, then get more precise with them as you get more comfortable with using Workflows.
---
# 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://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/review-partner-applications/automate-partner-application-processing/workflow-best-practices-and-faqs.md?ask=&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.
