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

# People triggers

People triggers start automations from employee lifecycle dates: start date, end date, probation, work anniversary, and birthday. Ideal for orchestrating onboarding and offboarding across teams

People triggers start automations from employee lifecycle dates. They’re ideal for orchestrating onboarding/off boarding and scheduled employee touch points without opening a request first.

Available triggers

* Start date
* End date
* Last working day
* Work anniversary
* Birthday
* Probation period

> **Note** - **End date** and **Last working day** are two separate dates on the People record, and they often differ: someone can stop working weeks before their contract ends. **Last working day** is the day they stop working; **End date** is the day their contract ends. Pick the date each step hangs on according to your offboarding policy: revoking access on **Last working day** closes it as soon as someone stops working, while **End date** keeps it open until the contract ends. **Last working day** only fires for people whose record carries that date, so map it from your HRIS in **Settings → Context management → People fields** before you build a workflow on it.

### When to use

* Onboarding: coordinate tasks across IT, HR, Facilities on the employee’s start date.
* Off boarding: revoke access, collect equipment, and notify stakeholders on end date.
* Check‑ins: probation reminders to manager and HR.
* Recognition: send automated anniversary or birthday messages.<br>

### Conditions you can add

* People attributes: department, location, manager, employment type (employee/contractor), legal entity, job title/level.
* Groups: teams and custom groups you defined.
* App/device context: whether the person owns certain apps or equipment.
* Leaving details: leaving type and regrettable departure, as supplied by your HRIS. Use these to branch one offboarding workflow by exit reason instead of maintaining one workflow per reason.

> **Note** - Leaving fields are not normalised in Siit. The condition matches the value your HRIS sends, so the options you see depend on your HR system's own configuration. Check the value on a real People profile before you rely on it in a live workflow.

### Timing each action around the trigger date

Every action in a People workflow runs on a day offset from the trigger date: on the day, a number of days before, or a number of days after. Set an action to run **before** the trigger date and a **Catch up if missed** checkbox appears next to the offset.

* **Unticked** — the action runs only on that exact day. If that day has already gone by, the action is skipped. This is the default.
* **Ticked** — the action also runs when that day has already gone by, up to and including the trigger date.

**Catch up if missed** is what makes a late setup still work. Take an onboarding workflow with a step set to run seven days before the start date, switched on only three days before a new starter arrives: unticked, that step never runs, because the seventh day before is already behind you. Ticked, it runs on the next pass and the starter still gets it. The catch-up stops at the trigger date, so a step timed before a start date that has already passed runs either way.

Leave the box unticked for steps that only make sense on their own day, such as a reminder timed to land exactly a week ahead, and tick it for onboarding and offboarding steps that have to happen even when the workflow, or the employee record, arrives late.

The step's tab on the canvas shows the choice, so you can read it without opening the step: a step set seven days ahead with the box ticked reads `7 days before • Catch up if missed`.

> **Note** - the checkbox replaces the **Exactly** and **Within** radio buttons. Steps saved in **Within** mode open with the box ticked, and nothing about how they run has changed. The box only shows on **before** delays; **after** and on-the-day steps never had the choice.

### Common workflows

* Day‑1 onboarding
  * Trigger: Start date
  * Conditions: Department = Engineering, Location = London
  * Actions: Okta or google “Add to groups,” create Jira/Linear tasks, send welcome kit email, notify hiring manager
* Off boarding
  * Trigger: End date
  * Conditions: Employment type = Employee
  * Actions: Revoke sessions, Google group removal, remove app access, create pickup request for equipment, DM manager with completion summary
* Probation review
  * Trigger: Probation period
  * Conditions: Department = Sales
  * Actions: Send checklist to manager, open a request if feedback is missing after 3 days
* Celebrations
  * Trigger: Work anniversary
  * Actions: Post a message in #all‑hands and DM the manager with a recognition template

### Best practices

* Keep sensitive steps (de-provision, wipe) behind approvals for contractors if needed.
* Use categories (HR, Security) and roles to restrict who can edit these flows.
* Add “owner” chips to actions that hit external systems for clear accountability.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.siit.io/workflow/people-triggers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
