> ## Documentation Index
> Fetch the complete documentation index at: https://docs-vnext.kiflo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflow Triggers: All Events That Start Automations

> Reference all Kiflo workflow triggers — invitation status, metric changes, partner properties, and payout validation — with setup steps and use cases.

A trigger is the event that kicks off a workflow. When the conditions you configure are matched, Kiflo automatically enrolls the relevant entity — a partner, a partner team member, or a payout — and runs the workflow's action sequence. Choosing the right trigger is the first and most important decision when building a workflow.

Go to **Manage > Workflows**, open or create a workflow, and click **Choose trigger** to select from the options below.

***

## Partner invitation status changed

This trigger fires when the invitation status of a partner team member changes. Use it to react to new partners joining your portal or to follow up with partners who have not yet activated their account.

<Accordion title="Configuration">
  <Steps>
    <Step title="Select the trigger">
      In the workflow builder, click **Choose trigger** and select **Partner invitation status changed**.
    </Step>

    <Step title="Choose the target status">
      Select which status change should fire the workflow:

      * **Pending or Sent** — fires when you grant a partner team member access to the portal and the invitation is issued, but not yet accepted. Use this to start a follow-up sequence for partners who have not yet logged in.
      * **Accepted** — fires when the partner team member accepts the invitation by logging in to the portal for the first time. Use this to send a welcome email or create an onboarding task.
    </Step>

    <Step title="Confirm">
      Click **Confirm** to save the trigger configuration.
    </Step>
  </Steps>
</Accordion>

<Accordion title="Use cases">
  **Ensure partners activate their portal access**

  Set the status to **Pending or Sent** and build a follow-up sequence: wait three days with a Delay action, then send a reminder email with the activation link. Add another delay and a second email if necessary. Set the end condition to **Partner team member accepted invitation** so the sequence stops automatically once the partner logs in.

  **Send a welcome email on first login**

  Set the status to **Accepted**. When the team member logs in for the first time, the workflow fires immediately. Send a personalized welcome email and optionally create an onboarding task for your team to schedule an intro call.
</Accordion>

***

## Metric changed

This trigger fires when a partner's performance metric crosses a condition you define, such as a deal count or lead count in a given time period. Use it to automatically reward top performers or proactively support underperforming partners.

<Accordion title="Configuration">
  <Steps>
    <Step title="Select the trigger">
      Click **Choose trigger** and select **Metric changed**.
    </Step>

    <Step title="Select the entity">
      Choose the entity whose metric you want to monitor — typically **Partner**.
    </Step>

    <Step title="Choose a metric">
      Select the metric to watch. Available options include:

      * Submitted leads
      * Shared leads
      * Registered deals
      * Won deals
      * And other activity metrics tracked by Kiflo.
    </Step>

    <Step title="Set the period">
      Choose the time window for the metric:

      * Current month / Last month
      * Current quarter / Last quarter
      * And other available periods.
    </Step>

    <Step title="Define the condition">
      Set a threshold condition, for example:

      * **Is more than 3** — fire when the partner exceeds 3 registered deals.
      * **Is less than 2** — fire when the partner has submitted fewer than 2 leads.
    </Step>

    <Step title="Confirm">
      Click **Confirm** to save the trigger configuration.
    </Step>
  </Steps>
</Accordion>

<Accordion title="Use cases">
  **Detect top-performing partners**

  Select the **Registered deals** metric for the **Last month** period with the condition **Is more than 3**. When a partner surpasses that threshold, the workflow fires and sends them a congratulatory email.

  **Detect low-performing partners**

  Select the **Submitted leads** metric with the condition **Is less than 2** for the **Last quarter** period. If a partner falls below the threshold, automatically send an email asking if they need support, or create a task for your team to reach out.
</Accordion>

***

## Partner properties changed

This trigger fires whenever a property on a partner record is updated, if all the conditions you define are met. Use it to react to changes in partner data such as country, program tier, status, or custom properties — including date-based properties like **Last seen date**.

<Accordion title="Configuration">
  <Steps>
    <Step title="Select the trigger">
      Click **Choose trigger** and select **Partner properties**.
    </Step>

    <Step title="Add conditions">
      Add one or more property conditions. The workflow fires only when all conditions are matched at the time of evaluation. Examples:

      * **Country is equal to France** — fire for partners whose country is set to France.
      * **Last seen date is more than 12 weeks ago** — fire for partners who have not logged in recently.
      * **Status is equal to Active** — fire only for active partners.

      You can combine as many conditions as you need.
    </Step>

    <Step title="Confirm">
      Click **Confirm** to save the trigger configuration.
    </Step>
  </Steps>
</Accordion>

<Accordion title="Use cases">
  **Re-engage inactive partners**

  Set a condition where **Last seen date is more than 12 weeks ago**. Workflows based on relative date conditions are evaluated every day, so Kiflo checks this condition daily. When a partner crosses the 12-week threshold, the workflow fires and sends a re-engagement email or creates an internal task.

  **Trigger region-specific actions**

  Set a condition where **Country is equal to France**. Whenever any property on a French partner's record is updated and the country condition still matches, the workflow fires. You can use this to assign a local partner manager task or send a region-specific resource.

  <Warning>
    The Partner properties trigger fires whenever **any** property on the partner record changes — even if it is not the property you are filtering on. Make sure your conditions are precise enough to avoid unintended enrollments. Use re-enrollment settings carefully to avoid running the same partner through the workflow repeatedly.
  </Warning>
</Accordion>

***

## Payout validated

This trigger fires when a payout moves from **Draft** status to **Pending** status — the point at which the payout has been validated and requires action from the partner, such as uploading an invoice or reviewing rewards.

<Accordion title="Configuration">
  <Steps>
    <Step title="Select the trigger">
      Click **Choose trigger** and select **Payout validated**.
    </Step>

    <Step title="Confirm">
      There are no additional conditions to configure for this trigger. Click **Confirm** to save.
    </Step>
  </Steps>

  <Note>
    If a payout moves directly from **Draft** to **Ready** (because no action from the partner is required), the trigger does **not** fire. It only fires on the **Draft → Pending** transition.
  </Note>
</Accordion>

<Accordion title="Use cases">
  **Automate payout follow-up**

  When a payout enters **Pending** status, start a sequence: send an email immediately asking the partner to upload their invoice. Add a five-day delay, then send a second reminder. Add another delay and create a task for your team to follow up directly if the invoice is still missing.
</Accordion>

***

## Re-enrollment settings

By default, once an entity completes a workflow, it will not enter the same workflow again. Re-enrollment settings let you override this behavior so the same partner, team member, or payout can re-enter the workflow if the trigger conditions are matched again.

Configure re-enrollment in the trigger settings when you set up or edit a trigger. This is especially useful for recurring triggers like the **Metric changed** trigger — if you want to send a low-performance alert every quarter a partner falls short, enable re-enrollment so the workflow fires each qualifying period.

<Note>
  Use re-enrollment carefully with the **Partner properties** trigger. Since that trigger evaluates every time any property changes, enabling re-enrollment without precise conditions can cause a partner to cycle through a workflow repeatedly in a short time.
</Note>