Integration
Connect Beanstalk to French Address Search
When something happens in Beanstalk, 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 Beanstalk 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 Beanstalk and French Address Search
Triggers and actions 2 triggers ยท 9 actions
Trigger
New RepositoryPolls for newly created repositories.
- New User
Polls for newly added users.
- Add public key
Add an SSH public key for Git authentication. POST /api/public_keys.json with name, content (single public SSH key).
- Create Repository
Create a new repository in the Beanstalk account.
- Get Repository
Retrieve a single repository by ID.
- Get User
Retrieve a single user by ID.
- List public keys
List SSH public keys for users on the account. GET /api/public_keys.json (optional user_id for admins).
- List Repositories
List all repositories in the Beanstalk account.
- List Users
List all users in the Beanstalk account.
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).
- Find addresses by text
Search 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.