Integration
Connect Spaceflight News to SLF
When something happens in Spaceflight News, your agent does the next thing in SLF. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Spaceflight News and SLF 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 Spaceflight News and SLF
Triggers and actions 3 triggers · 7 actions
Trigger
New articleFires when a new spaceflight news article is published.
- New blog
Fires when a new spaceflight-related blog post is published.
- New report
Fires when a new spaceflight industry report is published.
- Get article
Retrieve a single spaceflight news article by its ID.
- Get blog
Retrieve a single spaceflight-related blog post by its ID.
- Get report
Retrieve a single spaceflight industry report by its ID.
- List articles
Search and list spaceflight news articles, with filters for news site, launch, event, and featured status.
- List blogs
Search and list spaceflight-related blog posts, with filters for news site, launch, event, and featured status.
- List reports
Search and list spaceflight industry reports, with filters for news site, keywords, and publication date.
Action
Get Stadt-Land-Fluss dataFetch the full German Stadt-Land-Fluss (city/country/river word-game) reference dataset via GET https://slftool.github.io/data.json. Static, unauthenticated, single-request JSON blob keyed by letter, each letter holding arrays for stadt (city), land (country), fluss (river), name, beruf (profession), tier (animal), and marke (brand). No query parameters — the vendor exposes no filtering or search; the whole dataset is returned every call and any per-letter/per-category lookup must be done client-side on the response.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.