> For the complete documentation index, see [llms.txt](https://docs-vnext.kiflo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-vnext.kiflo.com/automation/triggers/workflow-trigger-partner-properties.md).

# Workflow trigger: Partner properties

The *Partner properties* will be triggered each time a partner property is updated if all conditions are matched. Read more to find out how to enable these triggers.

## Configure Partner properties trigger

Partner properties are the details about each one of your partners, and you might want to do specific actions whenever they are updated. Follow these steps to create triggers:

* Go to the **Manage** page and then **Workflows**, create a **New workflow,** **Name** it and click **Add**
* Open **Choose trigger** and choose the workflow to be triggered when **Partner properties** change
* Select one or multiple properties to define your conditions and ensure the workflow is only triggered if all conditions are met
* Click **Confirm**

For example, if you define a condition where the property Country is equal to France. Whenever a partner is updated, even if it’s another field, the trigger will be evaluated and if it matches the country specified, the workflow will be executed. However, if the country property does not match the country you have specified, the workflow won’t be executed.

You have the option to add as many trigger conditions, so you can, for example, have conditions on **Country, Status,** and **Program** properties all at the same time.

{% hint style="info" %}
Workflows based on relative date conditions are triggered every day. For example, if you have the following condition: last registered deal date is less than 3 weeks ago. The workflow will be evaluated every day to check if the date condition is met.
{% endhint %}

Common use cases *Partner properties* triggers examples

*Partner properties* triggers can be beneficial, for example, when detecting inactive partners. For instance, you choose the Last seen date to be 12 weeks ago. If the last time the partner logged in to the partner portal was more than 12 weeks ago, then you might want to trigger actions such as sending a reminder email to the partner or you could create a task to check the reason why they have not logged in.

Another example of when *Partner properties* triggers are essential is when you have a new partner logs in to the partner portal for the first time. Based on the information they add, such as their country and industry, if they meet your criteria, you could send them tasks.

{% hint style="warning" %}
The Partner properties trigger is triggered when any property on partners is updated. Therefore, ensure that the filters are set up correctly and that they use the right re-enrollment settings. For instance, if you have a trigger with a filter on Country, even if the Status property of the partner changes, the workflow will be triggered.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs-vnext.kiflo.com/automation/triggers/workflow-trigger-partner-properties.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.