Skip to main content
Workflows in PartnerOS are event-triggered automations. You define a trigger — something that happens in the platform — and then build a sequence of steps that run automatically when that event fires. Common uses include sending a welcome email when a new partner is created, notifying your team when a deal registration is submitted, and re-engaging partners who have been inactive for too long. Workflows run in the background without any manual intervention once activated. You can view each run’s status and step-level output in the workflow detail page.

​
Available triggers

A trigger is the event that starts your workflow. Choose the trigger that matches the moment in the partner lifecycle you want to act on.
Some triggers support configuration. For example, Partner Stage Changed lets you filter to only fire when a partner transitions from a specific stage to another. Partner Inactive and Contract Renewal Approaching accept a configurable number of days.

​
Create a workflow

1

Go to Workflows

In the left sidebar, click Workflows. The workflow list shows all workflows for your organization, along with their current status (Draft, Active, or Inactive) and how many minutes of work per week they save.
2

Click New workflow

Select New workflow. Enter a name and an optional description, then choose the partner lifecycle stage this workflow belongs to (Recruit, Onboard, Enable, Execute, or Optimize). Click Create.
3

Open the workflow editor

The new workflow opens in the visual editor. The canvas starts with a Manual Trigger node — you will replace this with your chosen trigger.
4

Set the trigger

Click the trigger node and select a different trigger from the list. If the trigger has configuration options (such as stage filters or a day count), fill those in.
5

Add action steps

Click the + button below the trigger to add the first action step. PartnerOS provides action node types for sending emails, updating records, adding delays, and branching logic. Connect nodes by dragging from one node’s output handle to the next node’s input.
6

Use the AI workflow generator (optional)

Instead of building manually, click Generate with AI and describe what you want to automate in plain language — for example, “Send a welcome email to the partner manager and schedule a check-in for 30 days after a new partner is created.” PartnerOS generates a full workflow graph from your description. Review the suggested nodes and adjust as needed.
7

Save

Click Save at any point. Workflows in draft state are saved but do not run automatically.

​
Test a workflow

Before activating a workflow, test it with a manual run to confirm it behaves as expected.
1

Open the workflow

From the Workflows list, click the workflow you want to test.
2

Click Run once

In the workflow detail or editor, click Run once. PartnerOS creates a test run using sample data that matches your trigger type — for example, a workflow triggered by Deal Registered will use a sample deal and partner from your organization.
3

Watch the run

The run panel shows each step executing in sequence. Green indicates success, red indicates an error. Click any step to see its input, output, and timing.
4

Inspect and adjust

If a step fails or produces unexpected output, return to the editor, fix the node configuration, and run again.
Manual test runs use real data from your organization but do not fire live emails or create permanent records unless your action nodes are configured to do so. Review your action-node settings before testing in production.

​
Activate a workflow

When you are satisfied with the workflow, activate it so it runs automatically.
1

Open the workflow

Navigate to the workflow from the Workflows list.
2

Set the status to Active

Click the Status toggle or use the status dropdown to switch from Draft to Active. PartnerOS saves the change and the workflow will now fire whenever the trigger event occurs.
To pause a workflow without deleting it, set its status to Inactive. To resume it, switch it back to Active.
Activating a workflow means it will run against real events immediately. Make sure you have tested the workflow and reviewed all action-node configurations before activating.

​
Common workflow examples

Trigger: Partner CreatedSteps:
  1. Send a welcome email to the partner’s primary contact with onboarding instructions.
  2. Notify the assigned partner manager via email or Slack.
  3. Add a 7-day delay, then send a follow-up check-in email.
This workflow ensures every new partner gets a consistent onboarding experience from day one.
Trigger: Deal RegisteredSteps:
  1. Send an internal email to the partner-team distribution list with deal details.
  2. Post a Slack message to the #deals channel.
This workflow keeps your team aware of incoming deal registrations without requiring anyone to monitor the PartnerOS inbox.
Trigger: Partner Tier ChangedSteps:
  1. Send a congratulatory email to the partner’s primary contact.
  2. Notify the partner manager of the tier change.
  3. Update any external CRM records via a webhook action.
Use the from-stage and to-stage configuration on the trigger to fire only for the specific tier transitions that matter to your program.
Trigger: Partner Inactive (X Days) — set to 60 daysSteps:
  1. Send a re-engagement email to the partner’s primary contact.
  2. Notify the partner manager to schedule a call.
This workflow surfaces quiet partners before they fully disengage.

​
Manage existing workflows

From the Workflows list you can:
  • Search by name to find a specific workflow.
  • Filter by stage (Recruit, Onboard, Enable, Execute, Optimize) or status (Draft, Active, Inactive).
  • Rename a workflow from the row action menu.
  • Delete a workflow from the row action menu. Deleting a workflow removes it permanently and stops all future runs.
The summary cards at the top of the page show the total number of active workflows, how many team members have created workflows, and the estimated time saved per week across all active automations.