INSEE Enrichment for Agile CRM
Configured with Agile Crm, HTTP Request, Schedule Trigger. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Web / API
- Code
- Transform
- Routing
- Integration
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| When clicking ‘Test workflow’ | Trigger | Manual Trigger | See node parameters |
| Find Company in SIREN database | Web / API | HTTP Request | See node parameters |
| Request all data from SIREN database | Web / API | HTTP Request | See node parameters |
| FilterOut all Company that have the ReadOnly Key set | Code | Code | See node parameters |
| Set Insee API Key | Transform | Edit Fields | See node parameters |
| Schedule Trigger | Trigger | Schedule Trigger | See node parameters |
| clean_route | Routing | No Op | See node parameters |
| Get all Compagnies from Agile CRM | Integration | Agile Crm | company / getAll |
| Enrich CRM with INSEE Data | Integration | Agile Crm | company / update |
| Merge data from CRM and SIREN database with enriched for the CRM | Transform | Merge | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
agileCrmApi
Workflow notes
Enrich CRM data with data from French INSEE OpenDatabase API
Enrich CRM data with data from French INSEE OpenDatabase API
This workflow takes all company entries from Agile CRM and enriches their data using the French Insee Opendata API (Free Access)
This will update :
- Official Address of the company headquarters
- Add government company id number (SIREN) in a Custom Field
👨🎤 Setup
👨🎤 Setup
- Add your Agile CRM credentials
- Link each AgileCRM node to the correct Agile CRM credentials
- Add your INSEE API Key to the "Set Insee API Key" node
- Make sure the Custom Fields for the companies are set as below (Admin Settings):
- Label : "SIREN", Type : "Text Field", Description "N° de SIREN"
- Label : "RO", Type : "Number", Description "Locks entry from update"
- Click on Test Workflow to make sure everything is working
- Configure schedule if needed and don't forget to change status to Active
Sticky Note2
👆 You can use any of those two Trigger to start the process.
🗒️ Notes :
🗒️ Notes :
-
This workflow is made to write over any entry already present. You can change this for each company by setting the "RO" Custom Field to 1, making it read-only for this workflow.
-
If you want to make it readonly after the update from this workflow, then add a custom property in the last node Enrich CRM with INSEE Data named "RO", SubType "Number" and Value "1"
INSEE Enrichment for Agile CRM
INSEE Enrichment for Agile CRM
Purpose and structure
This folder contains the INSEE Enrichment for Agile CRM workflow. Its executable nodes use agileCrm, code, httpRequest, manualTrigger, merge, noOp, scheduleTrigger, set. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
When clicking ‘Test workflow’, Schedule Trigger
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Code/1460_Code_Schedule_Automation_Scheduled.json MIT; preserve source notices.