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

# Self-updating CRM

> How signals update CRM files, and which docs they read.

You do not run updates. Ask your agent to connect email and meetings. Those apps send signals. Omnier updates the files in the background.

## What counts as a signal

* Outlook: sent email, received email, calendar events
* Gmail: sent email, received email, and calendar events
* Circleback: meeting transcripts
* LinkedIn: on demand, when you ask your agent to run `linkedin_sync`

## Customer records

For companies already in `crm/`:

1. A signal arrives.
2. Noise is dropped (personal mail, receipts, and similar).
3. Omnier loads the related company files.
4. It reads the rules files in `docs/rules/`.
5. It rewrites the markdown that should change (`context.md`, people, company, tasks).
6. It appends a line to `events.jsonl`.
7. It commits the change.

The current picture lives in the markdown. The raw event lives in `events.jsonl`.

## What signal updates read in docs/

Email and meeting updates read only `docs/rules/`:

| File | Role |
| - | - |
| `docs/rules/pipeline_stages.md` | Pipeline stages. `company.md` `stage` is that number. |
| `docs/rules/task_rules.md` | When to create a task, and what kind. |
| `docs/rules/update_rules.md` | Any other rule for how Omnier updates CRM files. |

`docs/sales/` and `docs/product/` are for you and your agent. Signal updates do not read them. LinkedIn sync and import read `docs/sales/icp.md` to skip people who are not ICP.


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