Integration
Connect Open Government, Netherlands to SLF
When something happens in Open Government, Netherlands, 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 Open Government, Netherlands 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 Open Government, Netherlands and SLF
Triggers and actions 1 trigger · 9 actions
Trigger
New datasetFires when a new dataset is published on the portal.
- Find datasets
Search the dataset catalog by keyword, tag, organization, or other filters and return matching datasets.
- Find resources
Search dataset resources (files/data tables) by keyword or field values.
- Find tags
Search the portal's dataset tags by keyword.
- Get dataset
Retrieve full metadata and resource listing for a single published dataset.
- Get organization
Retrieve details and dataset listing for a single publishing organization.
- Get resource
Retrieve metadata for a single dataset resource, including its download URL.
- List datasets
List the names of all public datasets published on the portal.
- List organizations
List the government organizations that publish datasets on the portal.
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.