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

# Automation recipes

> Install ready-made automations in a few clicks, preview them on your own data, keep them up to date and move your own between organizations.

Automations ("אוטומציות") run steps when something happens: a lead comes in, a quote is approved, a payment arrives. Instead of building a rule from scratch, start from the **automation library** ("ספריית אוטומציות"): about forty ready recipes that read like the problem they solve, such as "ליד חדש ← שיוך למי שחוזר אליו" or "הצעה אושרה ← פרויקט וטופס קליטה".

A recipe becomes a normal automation rule. It runs on the same engine, shows in the same run log, sends the same webhooks and counts against your plan's rule limit exactly like a rule you built by hand.

## Install a recipe

**1. Open the library**

**Automations** → **Automation library**. Filter by category (sales, collections, delivery, support, retention, or by business type), by your kind of business (agency, clinic, consultant, contractor, studio, office, tutor, freelancer), or search. **Popular** sorts the most useful first.

**2. Fill in up to three details**

Press **Install** ("התקנה"). The dialog asks only for the recipe's blanks: who handles it, which package, which pipeline stage, which tag, which WhatsApp template, an amount or a form. Your own name is picked as the team member by default.

**3. Check what would have happened**

**What would have happened** ("מה היה קורה") tries the recipe on your latest five records of that kind (leads, quotes, payments…) and lists what each step would have done. Nothing is sent or changed.

**4. Install and turn on**

**Install and turn on** ("התקנה והפעלה") creates the rule. It appears in **My automations** with a **From a recipe** chip.

## When something is missing

Each recipe card shows its status for your organization:

| Status | Meaning | What to do |
| - | - | - |
| Ready | Everything the recipe needs is in place. | Install it. |
| Needs setup ("צריך הכנה") | A connection (WhatsApp, card payments, email sending) or a record (a package, a pipeline stage, an onboarding form) is missing. The card names the step and links to the page that fixes it. | Fix it, or save the recipe as inactive now and turn it on later. Turning it on stays refused until the step is done. When a blank can only be filled after the fix (a WhatsApp template before WhatsApp is connected, a package before the catalog has one), fix the step first: the dialog says which blank is waiting. |
| Locked (padlock) | Your plan does not include something the recipe uses, such as WhatsApp. | Upgrade, or start a module trial where one is offered. |

At your plan's automation-rule limit, the install button shows the plan lock with your usage.

## Describe what you want

Type a sentence in **Describe in words what you want to happen** ("תארו במילים מה אתם רוצים שיקרה"), for example "כשנכנס ליד חדש, שמישהו יחזור אליו תוך שעה". Lancer suggests the closest recipe with its details filled in from your team, packages and tags. Nothing is created until you confirm in the install dialog.

When your plan includes AI, the suggestion comes from the model and uses AI credits. Otherwise, or past your monthly AI cap, Lancer matches by keywords.

## Updates

When Lancer improves a recipe, rules installed from the older version show **Update available** ("עדכון זמין"). **Update to the new version** rebuilds the rule with the details you chose at install; its name and on/off state stay as they are, and its version goes up in the run log.

## Your own recipes

Any rule can become a recipe: open the rule's menu (⋮) in **My automations** → **Save as recipe** ("שמירה כתבנית"). The team members, packages, stages, tags, forms and WhatsApp templates it names become blanks, so it carries no ids from your organization. A recipe can have at most three blanks.

Your recipes are listed under **My recipes** ("התבניות שלי") in the library:

* **Copy code** gives a code to paste in another organization (an agency copying its setup to a client, for example). The code holds no ids and no secrets, and is at most 20 KB.
* **Import a code** in the other organization adds it to its own recipes; installing it asks for that organization's team members, packages and tags.

Codes that contain ids, are too large or are not a Lancer recipe are refused.

## What recipes do not do yet

Recipes use today's events and steps. Reminders before an appointment, follow-ups after a delay, and other schedule- or timer-based automations arrive with the workflow builder. A task in Lancer lives on a project, so recipes that react to a new lead assign the lead to the person who calls back instead of adding a task.

Automations never charge, refund or issue documents: they can create a task or tag a client so a person handles it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.