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.Documentation Index
Fetch the complete documentation index at: https://docs.partneros.ai/llms.txt
Use this file to discover all available pages before exploring further.
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.Partner lifecycle triggers
Partner lifecycle triggers
| Trigger | When it fires |
|---|---|
| Partner Created | A new partner record is added to PartnerOS |
| Partner Stage Changed | A partner moves to a different lifecycle stage (optional: filter by from-stage and to-stage) |
| Partner Tier Changed | A partner moves between tier levels |
| Partner Inactive (X Days) | A partner has had no recorded activity for a configurable number of days (default: 30) |
| Contact Added to Partner | A new contact joins a partner organization |
| Partner Agreement Signed | A partner countersigns an agreement |
| Partner Certification Completed | A partner contact finishes a certification or training program |
| Contract Renewal Approaching | A configurable number of days before a partner’s contract renewal date (default: 30 days) |
| Partner Payment Made | A payment is recorded for a partner |
Deal triggers
Deal triggers
| Trigger | When it fires |
|---|---|
| Deal Registered | A partner submits a new deal registration |
| Deal Registration Approved | A deal registration is approved |
| Deal Registration Declined | A deal registration is declined |
| Deal Closed Won | A deal linked to a partner is marked closed-won |
| Deal Closed Lost | A deal linked to a partner is marked closed-lost |
Other triggers
Other triggers
| Trigger | When it fires |
|---|---|
| MDF Request Submitted | A partner submits a market development fund request |
| Manual Trigger | Fired on-demand by clicking Run once in the workflow builder |
Create a workflow
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.
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.
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.
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.
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.
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.
Test a workflow
Before activating a workflow, test it with a manual run to confirm it behaves as expected.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.
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.
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.
To pause a workflow without deleting it, set its status to Inactive. To resume it, switch it back to Active.
Common workflow examples
Welcome a new partner
Welcome a new partner
Trigger: Partner CreatedSteps:
- Send a welcome email to the partner’s primary contact with onboarding instructions.
- Notify the assigned partner manager via email or Slack.
- Add a 7-day delay, then send a follow-up check-in email.
Alert the team when a deal is registered
Alert the team when a deal is registered
Trigger: Deal RegisteredSteps:
- Send an internal email to the partner-team distribution list with deal details.
- Post a Slack message to the #deals channel.
Promote a partner when their tier changes
Promote a partner when their tier changes
Trigger: Partner Tier ChangedSteps:
- Send a congratulatory email to the partner’s primary contact.
- Notify the partner manager of the tier change.
- Update any external CRM records via a webhook action.
Re-engage inactive partners
Re-engage inactive partners
Trigger: Partner Inactive (X Days) — set to 60 daysSteps:
- Send a re-engagement email to the partner’s primary contact.
- Notify the partner manager to schedule a call.
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.