Integration
Connect Laposta to arcsecond.io
When something happens in Laposta, your agent does the next thing in arcsecond.io. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Laposta and arcsecond.io 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 Laposta and arcsecond.io
Triggers and actions 3 triggers · 6 actions
Trigger
A New Relation Has Been AddedTriggers when een new relation has been added to the list in your Laposta account.
- A Relation Has Been Edited
Triggers when a relation of your Laposta list has been edited.
- A Relation Has Been Removed
Triggers when a relation of your Laposta list has been removed.
- Add or Edit a Relation
Edit an existing relation, or add a new relation, in your Laposta list.
- Delete Relation
Delete an existing relation.
Action
Get exoplanetLook up a single exoplanet by name via GET https://api.arcsecond.io/exoplanets/{name}/ — returns coordinates, parent star, discovery metadata. No auth required.
- Get object
Look up an astronomical object by name via GET https://api.arcsecond.io/objects/{name}/ — returns equatorial/ecliptic/galactic coordinates, constellation, source catalog. No auth required.
- List exoplanets
Paginated list of known exoplanets via GET https://api.arcsecond.io/exoplanets/ — returns name, host star, discovery method/year, orbital params. No auth required. Supports ?page=.
- List instruments
List astronomical instruments via GET https://api.arcsecond.io/instruments/ — returns uuid, name, acronym, telescope link, field-of-view specs. No auth required (public read confirmed 200).
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.