Skip to main content
Most of the automation a partner program needs is already in Introw, and most of it starts working the moment your CRM is connected. This inventory lists it area by area: what each automation does, whether it is on by default or something you switch on, and where it is configured. Read it before you build anything on the Workflows canvas, because the list of rules you actually have to build yourself is shorter than it looks.

What you’ll achieve

A complete, checkable picture of Introw’s out-of-the-box automation, so you can switch on the pieces your program needs, stop enforcing them by hand, and reduce your workflow backlog to the rules that are genuinely specific to how you run partnerships.

Before you start

1

Connect your CRM

Most of this list is a consequence of the CRM connection. See CRM integrations.
2

Know the three states

Always on needs no switch, only configuration. Switch on is off until you enable it, because it changes what partners receive or what happens to your data. Build it means there is no built-in automation and a workflow is the answer.

Partners and their people

Everything here follows from partner detection, and it is the layer worth getting right first: it decides who your partners are and what data the rest of the program automates against.

Audiences

Segments are the single highest-leverage automation in Introw, because so much keys off them. A dynamic segment is also the way to trigger on things no event names directly: “quiet for 30 days”, “crossed a revenue threshold”, “certified but not transacting”. Define the segment, then point a workflow’s Segment membership trigger at it.

Portal access

Records and submissions

Journeys and tasks

Learning

Incentives and money

Messaging

AI

What is left to build

After all of the above, the rules that still need a workflow are the ones tied to your own program design rather than to the mechanics of running a partner program:
  • Promotion on achievement. Tier a partner up, add them to a segment, and log it in the CRM when they certify or finish onboarding. See Reward a finished journey.
  • Deadline chases with escalation. Remind the partner before a task is due, again after it slips, and hand it to the partner manager. See Chase a task to its due date.
  • Fixed rewards. A flat bonus for an action, rather than a percentage of a deal. See Reward a finished journey.
  • Reacting to your own CRM fields. A partner’s segment, region, or program field changing in the CRM moving them onto a different experience. See React to a CRM change on a partner.
  • Multi-step re-engagement. A sequence that nudges, waits, checks whether it worked, and only then involves a human. See Re-engage quiet partners.

Verify it worked

Walk the list against your own program and you should be able to point at each row and say “on, off on purpose, or not for us”. The test that the built-in layer is doing its job: new partners appear without anyone importing them, your partner list and the CRM agree, segment membership is current, submissions arrive as CRM records rather than as messages someone retypes, and the reminders your partners get are ones nobody sent.

Build your first workflow

Build the rules the built-in layer does not cover.

Every notification Introw sends

The full catalog of automatic messages, with triggers and recipients.

Detect partners from your CRM

Set up the detection and sync layer everything else follows from.

Create a dynamic segment

Build the audiences the rest of the program keys off.