Built-in Automation

​

Where it lives

Built-in automation is configured in two places under Settings: CRM settings switches on the detection and sync layer, and Segments holds the audiences everything else keys off.

​

Before you start

​

How it works

Introw’s automation comes in three layers, and knowing which layer you are in tells you where to go and how much work it is.

1. Always on. Things Introw does as a consequence of being connected: partner detection, contact and owner import, property sync, dedupe on submissions, attribution, segment re-evaluation, progress tracking. There is no switch, only configuration that shapes them.
2. On by choice. Things that are off until you enable them because they change what partners receive or what happens to your data: automatic partner sync, tier sync, auto-enrollment on a course, auto-issue of a certificate, sleeping-deal nudges, automatic payout runs, AI announcement suggestions.
3. Built by you. The rules specific to your program, on the Workflows canvas.

The order to set them up in follows the same logic. The CRM connection decides who your partners are and what data they carry. Segments turn that data into audiences. Almost everything else, from notification recipients to portal tab visibility to course enrollment to discounts, keys off those segments. Getting the first two right is what makes the rest configuration rather than maintenance.

​

Settings & configuration

The full inventory, automation by automation, is in Every automation that runs out of the box. What follows is the map: the surfaces that own the automation layer, in the order you should visit them.

​

The CRM connection

CRM settings is where the largest group of automations lives. Partner detection picks the CRM object your partners are, and the filters that narrow it to the records that really are partners: only matching records become partners. Detection also brings the people, not just the account, so each partner’s contacts are imported under their People and the CRM account owner is suggested as a team member you accept with one click. Automatic sync is the switch that turns detection from an import into an automation: with it on, any new CRM record matching your filters becomes a partner on its own. Leave it off while you are still tuning filters, then turn it on once detection covers the right set. See Detect partners from your CRM. Field mapping decides which properties travel and in which direction, which is what keeps partner data true on both sides without anyone reconciling it.

​

Segments

Segments are the audience layer the rest of the program keys off, so they are the second thing to get right. A dynamic segment is a set of conditions over live partner, contact, and CRM data, re-evaluated on a schedule, so membership follows the data rather than a list someone maintains. A static segment is a list you curate, and it is the only kind a workflow can add a partner to. Segment membership drives notification recipients, portal tab visibility, content and asset visibility, course auto-enrollment, tier and partner-based discounts, and announcement targeting. See Segments.

​

Notifications and nudges

Notification settings is the catalog of what your program sends on its own: deal and record updates, submission outcomes, task assignments and reminders, learning and certificate signals, commissions and payouts. Recipients are set once organisation-wide on Default settings and overridden per segment; chat delivery is configured per platform on the chat integration. See Notifications. Two nudges are configured on the pipeline section of an experience rather than in the catalog, and both are off until you set them: Sleeping deal, which emails the partner when a deal sits too long in a stage, and Deal updated, where you choose the properties that count as an update so partners are only told when something meaningful changes. The same setting exists per record type you sync, named after that record.

​

Forms

A form’s Automation is what makes a submission an operation rather than a message. It maps answers to CRM properties, creates or updates the CRM objects behind the submission, matches against existing records so you do not collect duplicates, attributes everything to the submitting partner, and can fill only the fields that are still empty. Approvals route the submission before any of it lands. See CRM automations and Submissions and approvals.

​

Learning

A course’s Enrollment can auto-enroll every partner in the segments you attach, including partners who join the segment later. A course’s Certificate can auto-issue on completion, gated on the passing score if the course has a quiz. Progress and certificates sync back to the CRM. See Enrollments and Certificates.

​

Incentives

Commission plans earn lines on their own from CRM or billing data as deals close and invoices are paid, against the eligibility conditions and rates you set. Payout settings can advance payout runs on a schedule instead of someone starting each one. See Commission plans and Payout settings.

​

Journeys and experiences

A journey attached to an experience is applied to partners as they get that experience, so onboarding starts without anyone pressing Apply. See Auto-apply a journey from the experience.

​

AI

The AI layer runs on its own once configured: the partner support agent answers partner questions from your content, deal coaching attaches a next step to deal notifications, channel conflict detection flags overlaps on registrations, and weekly announcement suggestions arrive as drafts for review. See AI Agents.

​

How-to guides

​

Troubleshooting