Skip to content
Tulina
Book a demo
← Processes

Keep CRM accounts updated

Companies in your CRM are checked every week for new legal filings, and a change of ownership, officers or address, or an insolvency, is flagged on the account.

Book a demo
Salesforce→BODACC
Starts
Weekly schedule
Steps
4
Checks and gates
0
A person decides
Never, runs alone

Trigger · Schedule

Weekly schedule

The run checks every account you already hold once a week, so a legal event surfaces the week it is published.

Claude runs the rest autonomously

  1. 1

    AI lists accounts with a SIREN.

    Salesforce

    Salesforce

    Every account you already hold that carries a SIREN is listed, ready to be checked.

  2. 2

    AI finds new legal filings.

    BODACC

    BODACC

    Every legal event published for those companies since the last run comes back.

  3. 3

    AI keeps events that change a decision.

    Only the event types that matter to your team are kept — ownership, insolvency, address, officers.

  4. 4

    AI flags each changed account.

    Salesforce

    Salesforce

    Each changed account is updated with a note naming the event and its date, so the next call starts informed.

A CRM decays quietly. The record is right on the day it is written and wrong eighteen months later, and nothing announces the change. The company was acquired, changed name, moved, or filed for protection. All of it was published, and none of it reached your CRM.

In France, BODACC publishes those events continuously. What has always been missing is someone reconciling that public feed against every account in the CRM, every week, which is the kind of repetitive check an AI agent can run on a schedule.

What you get

Accounts that moved, whether new ownership, a name change or an insolvency filing, surface the week it happens instead of the quarter after.

What each CRM account is checked against

Once a week the run lists every Salesforce account carrying a SIREN, or whichever field your CRM uses for a French company identifier, in batches rather than one record at a time. If the CRM records when an account was last checked, only the accounts that are due come through.

For each SIREN, BODACC returns the legal announcements published since the last run. A first run looks back 90 days. The lookup is batched by SIREN list where the tool supports it, and falls back to one call per company only where it does not.

Which company changes are worth flagging

Most legal events are noise for a sales team. Annual accounts and minor administrative notices are dropped before anything is written, because publishing all of them into the CRM trains everyone to ignore the flag. What stays are the events that change how a rep would run the account:

  • an ownership change
  • a name change
  • an address change
  • insolvency or collective proceedings
  • a change of officers

When an account has more than one of these since the last run, all of them are kept. Collapsing them to the most recent one would hide the rest.

How the account gets flagged

Each changed account gets its status or flag field updated and a note naming the event type and its publication date, so the next call starts from what happened and when. Accounts without a qualifying event are left untouched. The run records its cutoff date, which is where the next one picks up, and reports how many accounts it checked, how many had an event by type, and any SIREN that BODACC could not resolve.

Where it applies

BODACC is the French legal-announcements registry, so as written this monitors accounts for companies registered in France. The method is the same wherever a public registry publishes legal events: watch it on a schedule, keep the event types that change a decision, and flag the account with the event and its date.

The prompt

The real prompt behind the steps above, detailed enough that an agent with the same tools can run it as written. The Run buttons copy the full version, which also carries the steps for connecting those tools.

# Keep CRM accounts from going stale

You have read/write access to Salesforce and a tool that queries
BODACC (the French legal-announcements registry) for company events.
Run this on a recurring schedule.


## 1. List accounts with a SIREN

- Query Salesforce for every Account carrying a SIREN (or your own
  French-company identifier field), in batches — never one record at
  a time.
- If your CRM tracks when an account was last checked, pull only what's
  due; otherwise pull the full set each run and let the registry's own
  "since date" filter in the next step keep the volume down.

## 2. Find new legal filings

- For each SIREN, query BODACC for legal announcements published since
  the last run (or, on a first run, the last 90 days).
- Batch this by SIREN list where the tool supports it; fall back to
  one call per company only if it doesn't.

## 3. Keep events that change a decision

- Filter to event types that actually change how a rep would run the
  account: ownership change, name change, address change,
  insolvency/collective proceedings, officer changes. Drop routine
  filings (annual accounts, minor administrative notices) — publishing
  everything trains the team to ignore the flag.
- If an account has more than one qualifying event since the last run,
  keep all of them — don't collapse to "most recent only."

## 4. Flag each changed account

- Update the Account's status/flag field and leave a note naming the
  event type and its publication date — not just "something changed."
- Only touch accounts that actually had a qualifying event this run;
  never touch the rest.
- If this runs on a schedule, record the run's cutoff date somewhere so
  the next run knows where to pick up.

## Output

Report: how many accounts checked, how many had a qualifying event
(broken down by event type), and any SIREN that failed to resolve in
BODACC.

Why run it with Tulina

A prompt helps one person. A process moves a team.

Pasted into a chat, the prompt above works once, for whoever pasted it. In Tulina, "Keep CRM accounts updated" becomes a process the team shares, that keeps its history, runs on its own, and stays inside the same security perimeter as the tools it calls.

  • The whole team works on the same one

    PersonalTeamOrganisation

    A process lives where it belongs: yours, your team's or the whole organisation's. Whoever runs it can improve it, and everyone starts from the best version instead of explaining the job again.

  • Every edit is a version

    v1v2v3

    Each change is a new version with the previous one kept, so a bad edit is undone by restoring an earlier one. Every run records the version it followed, and what a run teaches goes back into the process.

  • It runs without you

    schedulewebhookon demand

    A hosted agent runs the process on Tulina's own infrastructure, on a schedule or when an event arrives, and keeps going when you close the chat. Nothing to host. Every run is tracked to its outcome.

  • Inside the same security perimeter

    vaultrolesrun log

    Credentials stay in the vault, never in the prompt. Roles decide who may run what, every call is logged, and a step a person has to approve waits for that person.

Questions about CRM account monitoring

Yes — an agent with access to a public legal-announcements registry and your CRM can check every account you hold against new filings, on a recurring schedule, and flag the ones that changed.

Ownership changes, name changes, insolvency or collective proceedings, and officer changes — the events that change how you'd run the account. Routine filings like annual accounts are noise and get filtered out first.

By filtering hard before writing anything. Publishing every legal event trains a team to ignore the flag entirely, so only the handful that change a real decision get surfaced.

The mechanism is jurisdiction-agnostic — watch a public legal registry, filter to relevant event types, flag the account — even though the specific source here (BODACC) is French.

Also on Salesforce

Other processes that run mainly on Salesforce. The tools they share with this one are lit.

See Tulina in a 30-minute demo.

Book a demo