← Back to directory
Data & Analytics Medium to set up Automation Enrich

INSEE Company Data Enrichment for Agile CRM

Source reviewed Updated 2026-07-07

Syncs Agile CRM companies with French INSEE OpenData to add SIREN IDs and addresses without overwriting existing info.

E-commerce Operatorops and IT teams

What it does

Get accurate French addresses and SIREN IDs for your Agile CRM companies by syncing with INSEE OpenData without losing existing information. This automation enriches your profiles using government data while keeping a read-only mode to protect current records from accidental overwrites.

Step by step

  1. Configure the Agile CRM trigger to fire on contact or company updates.
  2. Construct the HTTP GET request to the INSEE API using the SIRET or name as query parameters.
  3. Map the JSON response fields such as 'adresse' and 'siren' to the corresponding Agile CRM custom properties.
  4. Implement a boolean flag in the code node to toggle between read-only inspection and actual data overwriting.

Where the LLM does the work

  • Generate robust string normalization logic to handle French accented characters when matching company names against INSEE records.
  • Write error handling code that distinguishes between network timeouts, API rate limits, and invalid SIREN formats.
  • Create user-friendly alert messages for cases where no exact match is found or multiple potential matches exist.

Watch out for

INSEE API responses can be inconsistent with address formatting so you must parse the nested JSON structure carefully to avoid null reference errors.
Company names in Agile CRM may differ slightly from official INSEE records so implement fuzzy matching logic rather than relying on exact string equality.
Accidental overwrites can corrupt existing customer data so always enable the read-only mode by default during initial testing phases.

Tools that fit

Agile CRM Service Source and destination for company records
INSEE OpenData API External database for French company address and SIREN lookup
Code Service Logic to handle readonly checks and data mapping

The agent brief

Everything your agent needs, including the gotchas. Copy it and go.
agent-brief.md
You are helping me build the following AI agent workflow.

## Goal
INSEE Company Data Enrichment for Agile CRM: Syncs Agile CRM companies with French INSEE OpenData to add SIREN IDs and addresses without overwriting existing info.

## Specification
- What it does: Get accurate French addresses and SIREN IDs for your Agile CRM companies by syncing with INSEE OpenData without losing existing information. This automation enriches your profiles using government data while keeping a read-only mode to protect current records from accidental overwrites.
- Trigger: Run manually (Manual · on demand)
- Autonomy: Fully hands-off
- Expected setup effort: about an afternoon
- Tools/services involved:
  - Agile CRM: Source and destination for company records
  - INSEE OpenData: External database for French company address and SIREN lookup
  - Code: Logic to handle readonly checks and data mapping

## Known pitfalls, handle each one explicitly in your implementation
1. INSEE API responses can be inconsistent with address formatting so you must parse the nested JSON structure carefully to avoid null reference errors.
2. Company names in Agile CRM may differ slightly from official INSEE records so implement fuzzy matching logic rather than relying on exact string equality.
3. Accidental overwrites can corrupt existing customer data so always enable the read-only mode by default during initial testing phases.

## Reference implementation
https://n8n.io/workflows/2633 (workflow template)
Fetch and inspect this before building. If it matches my stack, adapt it;
if not, rebuild the pattern with my tools.

## Process requirements
1. Before building: ask me which of the listed tools I actually use and
   what my platform is (n8n / Make / code / other). Do not assume.
2. Adapt the pattern to my answers; do not force the reference stack.
3. Address every pitfall above; tell me how you handled each.
4. Provide a test plan I can run before letting this touch real data.
5. Ask before any step that sends messages, modifies data, or spends money.

Source: https://usecasesforagents.com/use-case/insee-company-data-enrichment-for-agile-crm/ via usecasesforagents.com

Frequently asked questions

Can I use a different CRM than Agile CRM?

Yes. Agile CRM is only the example CRM in this recipe. The same flow works with Attio, Close CRM, Freshworks CRM and GoHighLevel. Swap the CRM connection and keep the rest of the setup as written.

Want this running in your business?

This is what I do. I design and build AI agents like this one, and keep them running. If you want it set up for your team instead of doing it yourself, get in touch.
Get in touch →

Who it's for

Also fits E-commerce Operator.

Ops-IT teams triaging their own internal requests get the same pattern, different queue.

Seen in the wild

← Back to directory