Skip to main content
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.
1

Select the trigger

In the workflow builder, click Choose trigger and select Partner invitation status changed.
2

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.
3

Confirm

Click Confirm to save the trigger configuration.
Ensure partners activate their portal accessSet 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 loginSet 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.

​
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.
1

Select the trigger

Click Choose trigger and select Metric changed.
2

Select the entity

Choose the entity whose metric you want to monitor — typically Partner.
3

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.
4

Set the period

Choose the time window for the metric:
  • Current month / Last month
  • Current quarter / Last quarter
  • And other available periods.
5

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.
6

Confirm

Click Confirm to save the trigger configuration.
Detect top-performing partnersSelect 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 partnersSelect 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.

​
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.
1

Select the trigger

Click Choose trigger and select Partner properties.
2

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.
3

Confirm

Click Confirm to save the trigger configuration.
Re-engage inactive partnersSet 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 actionsSet 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.
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.

​
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.
1

Select the trigger

Click Choose trigger and select Payout validated.
2

Confirm

There are no additional conditions to configure for this trigger. Click Confirm to save.
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.
Automate payout follow-upWhen 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.

​
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.
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.