> ## Documentation Index
> Fetch the complete documentation index at: https://docs.parsalink.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Automation Templates

> Browse and install pre-built automation workflows for common sales, support, onboarding, and re-engagement scenarios — customize them in minutes.

<div
  style={{
background: "linear-gradient(135deg, #143D4E 0%, #1C758A 55%, #30C8CA 100%)",
borderRadius: "24px",
padding: "28px",
marginBottom: "28px",
color: "#FFFFFF",
boxShadow: "0 20px 50px rgba(20, 61, 78, 0.22)",
position: "relative",
overflow: "hidden",
border: "1px solid rgba(255,255,255,0.08)"
}}
>
  <div
    style={{
position: "absolute",
top: "-36px",
right: "-36px",
width: "170px",
height: "170px",
background: "rgba(255,255,255,0.08)",
borderRadius: "999px"
}}
  />

  <div
    style={{
position: "absolute",
bottom: "-48px",
left: "-24px",
width: "130px",
height: "130px",
background: "rgba(255,255,255,0.06)",
borderRadius: "999px"
}}
  />

  <div
    style={{
  display: "inline-flex",
  alignItems: "center",
  background: "rgba(255,255,255,0.14)",
  color: "#FFFFFF",
  padding: "7px 14px",
  borderRadius: "999px",
  fontSize: "12px",
  fontWeight: "700",
  marginBottom: "12px",
  letterSpacing: "0.08em",
  textTransform: "uppercase"
}}
  >
    TEMPLATES
  </div>

  <p style={{ margin: 0, fontSize: "16px", lineHeight: "1.9", maxWidth: "760px", color: "#FFFFFF" }}>
    Automation templates are pre-built workflows you can install with one click and customize for your team — no need to wire up triggers and steps from scratch.
  </p>
</div>

## Browsing the Template Gallery

To open the gallery: **CRM → Automations → Browse Templates**.

Templates are grouped by category — Sales, Onboarding, Support, Re-engagement, General. Featured templates surface at the top. Each card shows the trigger event, the sequence of actions, and a short description so you can pick one without opening it.

<Note>
  Templates ship as **inactive** drafts when installed. You always get to review wording, timings, and conditions before flipping the switch to live.
</Note>

***

## Installing a Template

<Steps>
  <Step title="Pick a template">
    Click any card in the gallery to open its details. You'll see the full sequence of steps — every email, task, and tag the rule will create.
  </Step>

  <Step title="Install">
    Click **Install in My Workspace**. ParsaLink copies the template into your automation rules and routes you to the editor.
  </Step>

  <Step title="Customize">
    Edit any of the setup hints called out on the template (most templates highlight 1–3 things to tune for your business: tag names, timing, prompt copy).
  </Step>

  <Step title="Activate">
    Toggle the rule to **Active** when you're ready. The rule starts firing on the next matching event.
  </Step>
</Steps>

***

## Featured Templates

The templates below are seeded into every workspace and shown at the top of the gallery.

### Sales

<div
  className="bg-white dark:bg-black dark:border-white/10 dark:text-white [&_*]:dark:text-white"
  style={{
border: "1px solid #E7EAEC",
borderRadius: "18px",
padding: "20px",
marginBottom: "20px"
}}
>
  **New Lead Welcome Sequence** · Trigger: `contact_created`

  A 3-step welcome flow for every new contact: welcome email on day 0, follow-up email on day 3, and a manual follow-up task on day 7 if the contact hasn't moved past the *contacted* stage. Setup hints: customize the welcome copy and tune the cadence to match your sales cycle.
</div>

<div
  className="bg-white dark:bg-black dark:border-white/10 dark:text-white [&_*]:dark:text-white"
  style={{
border: "1px solid #E7EAEC",
borderRadius: "18px",
padding: "20px",
marginBottom: "20px"
}}
>
  **Daily Lead Harvest (Web Search)** · Trigger: `scheduled` (daily at 06:00 UTC)

  Runs your ideal customer profile (ICP) prompt against an LLM with web access every morning, creates Account + Contact records for matching businesses, then queues an AI-generated intro email at +1 hour and a manual follow-up task on day 3. Setup hints: edit the prompt to describe your ICP (industry, location, size), adjust the daily target count, and set the run hour in your workspace timezone. See the [Lead Generation](/crm/lead-generation) guide for the full picker walk-through.
</div>

<div
  className="bg-white dark:bg-black dark:border-white/10 dark:text-white [&_*]:dark:text-white"
  style={{
border: "1px solid #E7EAEC",
borderRadius: "18px",
padding: "20px",
marginBottom: "20px"
}}
>
  **Qualified Contact - Spin up Opportunity** · Trigger: `contact_stage_changed` where stage = `qualified`

  Automatically creates an opportunity and a 2-day discovery-call task whenever a contact reaches the qualified stage. Setup hints: tweak the default opportunity amount and the task wording.
</div>

<div
  className="bg-white dark:bg-black dark:border-white/10 dark:text-white [&_*]:dark:text-white"
  style={{
border: "1px solid #E7EAEC",
borderRadius: "18px",
padding: "20px",
marginBottom: "20px"
}}
>
  **Proposal Follow-Up** · Trigger: `proposal_status_changed` where status = `sent`

  Check-in email on day 2 and an escalation task on day 5 if the proposal hasn't been viewed. Both steps exit cleanly the moment the proposal is opened.
</div>

<div
  className="bg-white dark:bg-black dark:border-white/10 dark:text-white [&_*]:dark:text-white"
  style={{
border: "1px solid #E7EAEC",
borderRadius: "18px",
padding: "20px",
marginBottom: "20px"
}}
>
  **New Opportunity - Discovery Call Task** · Trigger: `opportunity_created`

  Tags every new opportunity with `discovery-needed` and creates a 2-day task to schedule a discovery call. A clean way to make sure no opportunity slips by without a kickoff conversation.
</div>

<div
  className="bg-white dark:bg-black dark:border-white/10 dark:text-white [&_*]:dark:text-white"
  style={{
border: "1px solid #E7EAEC",
borderRadius: "18px",
padding: "20px",
marginBottom: "20px"
}}
>
  **Contact Source = Web - Auto-Assign & Tag** · Trigger: `contact_source_changed` (source contains "web")

  When a contact's source is set to anything containing "web" (e.g. `website`, `web-form`), round-robin assigns it to the sales team, tags it `web-lead`, and sends an in-app notification to the new owner.
</div>

<div
  className="bg-white dark:bg-black dark:border-white/10 dark:text-white [&_*]:dark:text-white"
  style={{
border: "1px solid #E7EAEC",
borderRadius: "18px",
padding: "20px",
marginBottom: "20px"
}}
>
  **Deal Lost - Feedback Request** · Trigger: `opportunity_stage_changed` where stage = `closed_lost`

  Feedback email on day 1, then a re-engage task in 90 days. Keeps lost deals warm without manual reminders.
</div>

### Onboarding

<div
  className="bg-white dark:bg-black dark:border-white/10 dark:text-white [&_*]:dark:text-white"
  style={{
border: "1px solid #E7EAEC",
borderRadius: "18px",
padding: "20px",
marginBottom: "20px"
}}
>
  **Deal Won - Thank You & Onboarding** · Trigger: `opportunity_stage_changed` where stage = `closed_won`

  Thank-you email immediately, an onboarding task at +1 hour, and a workspace notification when the deal closes. Wires the celebration to a tangible kickoff so onboarding never stalls in handoff.
</div>

### Support

<div
  className="bg-white dark:bg-black dark:border-white/10 dark:text-white [&_*]:dark:text-white"
  style={{
border: "1px solid #E7EAEC",
borderRadius: "18px",
padding: "20px",
marginBottom: "20px"
}}
>
  **Urgent Case Escalation** · Trigger: `case_created` where priority = `urgent`

  Instant notification + `urgent-escalation` tag the moment an urgent case is filed, plus a 24-hour escalation task if the case isn't resolved. Setup hints: configure who receives the notification.
</div>

<div
  className="bg-white dark:bg-black dark:border-white/10 dark:text-white [&_*]:dark:text-white"
  style={{
border: "1px solid #E7EAEC",
borderRadius: "18px",
padding: "20px",
marginBottom: "20px"
}}
>
  **Inbound Email - Auto Acknowledge** · Trigger: `email_received` where `is_unsubscribe = false`

  Sends an instant acknowledgement reply and creates an "Reply to {'{'}contact\_name{'}'}" task at +1 hour. Skips unsubscribe replies so opt-outs aren't pestered.
</div>

### Re-engagement

<div
  className="bg-white dark:bg-black dark:border-white/10 dark:text-white [&_*]:dark:text-white"
  style={{
border: "1px solid #E7EAEC",
borderRadius: "18px",
padding: "20px",
marginBottom: "20px"
}}
>
  **Contact Inactivity Re-engagement** · Trigger: `inactivity` (30 days, entity = contact)

  A re-engage email when a contact has been silent for 30 days, plus a follow-up task on day 7 if they don't respond.
</div>

<div
  className="bg-white dark:bg-black dark:border-white/10 dark:text-white [&_*]:dark:text-white"
  style={{
border: "1px solid #E7EAEC",
borderRadius: "18px",
padding: "20px",
marginBottom: "20px"
}}
>
  **Long Inactivity (60 days) - Final Re-engagement** · Trigger: `inactivity` (60 days, entity = contact)

  The follow-on to the 30-day flow: one last touch email then a "consider archiving" task if there's still no response.
</div>

### General

<div
  className="bg-white dark:bg-black dark:border-white/10 dark:text-white [&_*]:dark:text-white"
  style={{
border: "1px solid #E7EAEC",
borderRadius: "18px",
padding: "20px",
marginBottom: "20px"
}}
>
  **New Contact - Auto Assign & Notify** · Trigger: `contact_created`

  Round-robin assigns every new contact across active team members and notifies the assignee. Use this as the baseline ownership rule if no source-specific routing applies.
</div>

<div
  className="bg-white dark:bg-black dark:border-white/10 dark:text-white [&_*]:dark:text-white"
  style={{
border: "1px solid #E7EAEC",
borderRadius: "18px",
padding: "20px",
marginBottom: "20px"
}}
>
  **New Account - Internal Notification** · Trigger: `account_created`

  Tags new accounts with `new-account` and notifies the team so nothing slips by unassigned.
</div>

***

## Customizing After Install

Every installed rule is a normal automation rule — you can edit any step, add steps, change conditions, or pause/delete it from **CRM → Automations**. Templates just give you a working starting point.

<Tip>
  Read the [Triggers](/automations/triggers), [Actions](/automations/actions), and [Conditions](/automations/conditions) pages to understand every knob the editor exposes.
</Tip>