Integration
Connect EasyCSV to French Address Search
When something happens in EasyCSV, your agent does the next thing in French Address Search. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want EasyCSV and French Address Search to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with EasyCSV and French Address Search
Triggers and actions 1 trigger ยท 4 actions
Trigger
New Spreadsheet Row ImportFires instantly for each row/record as EasyCSV imports a spreadsheet. In EasyCSV, open your import's Sheet Details, check "Post imports to Webhook", and paste this trigger's minted URL. EasyCSV sends one POST per row; the payload binds as {{ trigger.body.* }} (record_data holds the row's column values, plus import_id/import_name/sheet_name/importer_email metadata).
Action
Create CSV FileCreates a CSV File that can be used in your Zap, automatically emailed as an attachment, or uploaded to a specific place via SFTP.
Action
Parse CSV FileParse a CSV file and return a JSON array of rows
Action
Find address by latitude and longitudeReverse-geocode a latitude/longitude pair into the nearest matching French address, place, or administrative area. Uses GET https://data.geopf.fr/geocodage/reverse (lon, lat, plus optional type filter).
Action
Find addresses by textSearch for French addresses, streets, or places matching a text query and return matched candidates with geographic coordinates and postal/city details. Uses GET https://data.geopf.fr/geocodage/search (q, plus optional filters like postcode, citycode, type, lat/lon, limit).
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.