Workflow Templates

W11 draft / unreleased: The catalog and usage below mirror the coordinated graph template work. Templates are catalog data that clone into drafts; this page does not claim that any template is active, enrolled, or delivering through a live provider.

Use a template

1. Open Automations > Templates.
2. Choose a template and select Use template.
3. Review the cloned draft in Guided Editor. On a desktop screen, choose

Open Visual Builder when you need to inspect or edit branches.

1. Check the trigger, conditions, merge fields, recipients, and action order.
2. Select Save draft, then use Preview or Test before activation.
3. Select Activate only after the draft passes your review.

The clone receives new graph node and edge identifiers while preserving the template's entry conditions and TRUE/FALSE branch topology. Requirements and merge fields are validated during cloning, so a missing subject field or unsupported action remains visible as a draft error instead of being silently guessed. Editing a clone never changes the catalog template or another workflow made from it. Templates do not enroll records or send messages by themselves.

V1 template catalog

The gallery keeps the complete V1 order and contains these 14 graph templates:

TEST - Speed to Lead - Immediate Response — 8 graph steps

Starts from a new lead, sends an immediate response, records an internal note, creates a representative task, and adds a short follow-up when the lead stays quiet.

TEST - Lead Appointment Reminder — 2 graph steps

Starts when a lead appointment is booked and sends a day-before reminder using the appointment subject and its safe merge fields.

TEST - Job Appointment Reminder — 2 graph steps

Starts when a job is scheduled and sends a reminder two hours before the job window.

TEST - Estimate Follow-Up — 13 graph steps

Starts when an estimate is sent and follows up in stages, stopping or handing off when the estimate is accepted, declined, expired, superseded, or otherwise no longer eligible.

TEST - Post-Job Review Request — 9 graph steps

Starts when a job is completed, requests a review, follows a conditional email path, and includes the bounded XP award step when the review signal is available and XP is enabled. Its review.left branch uses the run fence: an exact review.submitted event can satisfy it, while other runs only see a review created after that run began.

TEST - Post-Job Nurture — 7 graph steps

Starts after job completion and continues a long-tail maintenance follow-up path with the configured waits and customer messages.

Residential - New Lead Booking Tasks — 6 graph steps

Create the first and second booking-call tasks for new residential leads, stopping when the lead is scheduled.

Commercial - New Lead Booking Tasks — 6 graph steps

Create the first and second booking-call tasks for new commercial leads, stopping when the lead is scheduled.

Residential - Estimate Follow-Up Tasks — 6 graph steps

Create staged follow-up tasks for residential estimates while a decision is still pending.

Commercial - Estimate Follow-Up Tasks — 6 graph steps

Create staged follow-up tasks for commercial estimates while a decision is still pending.

Residential - Job Completion Tasks — 3 graph steps

Create invoice and quality-follow-up tasks after a residential job completes.

Commercial - Job Completion Tasks — 3 graph steps

Create invoice and quality-follow-up tasks after a commercial job completes.

Residential - Invoice Collection Tasks — 5 graph steps

Create collection and escalation tasks for unpaid residential invoices, stopping when payment is recorded.

Commercial - Invoice Collection Tasks — 5 graph steps

Create collection and escalation tasks for unpaid commercial invoices, stopping when payment is recorded.

The five legacy linear template keys remain accepted for existing links and saved drafts. They are compatibility inputs, not additional gallery cards.

Template safety

Templates are scoped to the active organization and location context. A clone inherits the recipe shape, not another user's permission or subject scope. The server validates the trigger, graph topology, action payloads, merge fields, and current manage permission before saving or activating.

Preview and Test are provider-free. They do not send email or SMS, make calls, post webhooks, award XP, or write a customer-facing record. Activation creates an immutable published revision; later edits create a new draft and do not rewrite runs already pinned to the earlier revision.