> For the complete documentation index, see [llms.txt](https://docs.rubica.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rubica.au/workflow-automation/service-mappings-and-automation-triggers.md).

# Service Mappings and Automation Triggers

Two more ways to get a Job started or moved forward, without a date-based Workflow Trigger — a sale, or something happening outside Salesforce.

[Workflow Triggers](/workflow-automation/workflow-triggers-creating-a-trigger.md) create a Job off a **date** — 14 days before a Review Date, say. These two features cover the other two common starting points: a **sale**, and something happening **outside Salesforce entirely**.

## Service Mappings — create a Job from a sale

A Service Mapping links a Job Template to a specific Service/Product. When a client is sold something that matches, a new Job is created from that template automatically — the sale-based equivalent of a Workflow Trigger.

**Typical use:** an Annual Review workflow that should only start for clients on a specific ongoing advice service — not everyone, only the ones actually paying for it.

### Where to find it

**Home → Settings → Workflow Templates →** pick a template **→ Service Mappings** tab **→ + Add Mapping**. Link it to the Opportunity/Service combination that should trigger this template.

{% hint style="info" %}
This runs on its own separate engine from the day-to-day Job engine — it watches Opportunity and line-item changes specifically (a sale closing, a product being added), not stage entry/exit. It keeps its own audit trail too, so a Job created this way is traceable back to the sale that started it.
{% endhint %}

## Automation Triggers — react to something outside Salesforce

An Automation Trigger doesn't create a new Job — it moves an **already-open** one forward in reaction to a real-world event Salesforce wouldn't otherwise know about. The current version reacts to **Calendly bookings**: when a client books a meeting via Calendly, the matching open Job can jump straight to a "Meeting Booked" stage/outcome, without anyone touching the record.

**Typical use:** "when they book their review via Calendly, skip the 'Awaiting booking' stage automatically."

### Where to find it

**Home → Settings → Workflow Templates →** pick a template **→ Automation Triggers** tab.

## How this fits with everything else

| If you want to...                                                    | Use                                                        |
| -------------------------------------------------------------------- | ---------------------------------------------------------- |
| Create a Job off a date (Review Date, contract anniversary)          | Workflow Trigger                                           |
| Create a Job because they bought something                           | Service Mapping                                            |
| Move an *existing* Job because something happened outside Salesforce | Automation Trigger                                         |
| Move an *existing* Job because time passed inside a stage            | Stage Action                                               |
| Start a Job right now, on demand, no trigger needed                  | [Launch Workflow](/workflow-automation/launch-workflow.md) |

## See also

* [Workflow Triggers — Creating a Trigger](/workflow-automation/workflow-triggers-creating-a-trigger.md)
* [Duplicating & Deleting Templates](/workflow-automation/duplicating-and-deleting-templates.md) — Service Mappings and Automation Triggers both copy over when you duplicate a template