How do I import "INSEE Enrichment for Agile CRM" into n8n?

Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.

Which integrations does "INSEE Enrichment for Agile CRM" use?

It uses: manual, httpRequest, schedule, agileCrm. The flow diagram above shows how each service connects across the 14 nodes. Filter OpenRuna by integration to find related workflows and tools.

Can I import a sanitized export without credentials?

Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own manual and httpRequest credentials in n8n after import.

What trigger type does "INSEE Enrichment for Agile CRM" use?

Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.

Is "INSEE Enrichment for Agile CRM" free to use?

OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for manual, httpRequest, schedule, agileCrm.

← Workflows

INSEE Enrichment for Agile CRM

14 nodes · manual, httpRequest, schedule, agileCrm

Engine: n8n
Nodes: 14
Trigger: scheduled/triggered
Source file: 1460_Code_Schedule_Automation_Scheduled.json

Workflow flow

IntegrationsManualHTTPScheduleAgileCrmCodeSetNoOpMerge

100%

TRIGGER

When clicking ‘Test workflow’

Manual

TRIGGER

Schedule Trigger

Schedule

Set Insee API Key

Set

Get all Compagnies from Agile CRM

AgileCrm

FilterOut all Company that have the ReadOnly Key set

Code

Find Company in SIREN database

HTTP

clean_route

NoOp

Request all data from SIREN database

HTTP

Merge data from CRM and SIREN database with enriched for the CRM

Merge

Enrich CRM with INSEE Data

AgileCrm

10 steps · flows top to bottom, branches left to right

Browse by integration

manual httpRequest schedule agileCrm

Browse all integrations →

Download n8n JSON Download sanitized JSON Download flow graph

Import into n8n

Download the n8n JSON file (full or sanitized).
In n8n: Workflows → Import from file.
Open each node and reconnect credentials to your accounts.
Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

INSEE Enrichment for Agile CRM (14-node n8n automation, manual, httpRequest, schedule, agileCrm) is free on OpenRuna — view the graph and export the JSON to import into n8n.

What this workflow does

This n8n workflow, "INSEE Enrichment for Agile CRM", wires together manual, httpRequest, schedule, agileCrm in 14 nodes. 14 nodes · manual, httpRequest, schedule, agileCrm It starts from a scheduled/triggered trigger and routes data through every node in order. On OpenRuna you get the visual graph, the integration list, and a downloadable JSON ready to import into n8n. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

Fork it to add error handling, retries, or a notification step without designing the 14-node flow from scratch.
Benchmark it against your current manual integration to spot missing steps or redundant nodes.
Import "INSEE Enrichment for Agile CRM" into n8n, reconnect credentials for manual, httpRequest, schedule, agileCrm, and run the same automation in your own workspace.
Use it as a starting template when wiring manual, httpRequest, schedule, agileCrm — adjust node parameters to your accounts and record IDs.

Example output

Imported into n8n, "INSEE Enrichment for Agile CRM" exposes 14 configured nodes. Trigger type: scheduled/triggered. Integrations: manual, httpRequest, schedule, agileCrm. Reconnect the manual credential first, then walk the remaining nodes top to bottom. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Ask Claude to turn the "INSEE Enrichment for Agile CRM" JSON into a plain-English runbook, node by node. It can flag where manual rate limits or missing retries might bite before you go live.

ChatGPT

Drop the workflow JSON or this OpenRuna page URL into ChatGPT and ask for a step-by-step runbook: triggers, branches, and which fields to customise for manual, httpRequest, schedule, agileCrm. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "INSEE Enrichment for Agile CRM" — extract manual IDs and secrets into environment variables without changing the 14-node structure.

Frequently asked questions

How do I import "INSEE Enrichment for Agile CRM" into n8n?: Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "INSEE Enrichment for Agile CRM" use?: It uses: manual, httpRequest, schedule, agileCrm. The flow diagram above shows how each service connects across the 14 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?: Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own manual and httpRequest credentials in n8n after import.
What trigger type does "INSEE Enrichment for Agile CRM" use?: Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "INSEE Enrichment for Agile CRM" free to use?: OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for manual, httpRequest, schedule, agileCrm.