Integration
Connect Open Government, Finland to DocStruct
When something happens in Open Government, Finland, your agent does the next thing in DocStruct. 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, Finland and DocStruct 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, Finland and DocStruct
Triggers and actions 1 trigger · 9 actions
Trigger
New datasetFires when a new dataset is published to the Finnish open-data catalog (polls CKAN package_search sorted by creation date).
- Find datasets
Search the Finnish open-data catalog for datasets matching a keyword, tag, organization, or other criteria (CKAN package_search).
- Get dataset
Retrieve the full metadata and resource list for one published dataset by its id or name (CKAN package_show).
- Get organization
Retrieve details and datasets for one publishing organization by id or name (CKAN organization_show).
- Get resource
Retrieve one data resource (file/link/format) belonging to a dataset by its resource id (CKAN resource_show).
- List datasets
List the names of all published datasets in the catalog (CKAN package_list).
- List groups
List the topical groups/categories used to organize datasets in the catalog (CKAN group_list).
- List organizations
List the government organizations and agencies that publish datasets in the catalog (CKAN organization_list).
- List tags
List the tags used across datasets in the catalog, optionally filtered by a query string (CKAN tag_list).
Action
Extract document dataExtract structured fields (line items, totals, dates, party names, contract terms, etc.) from an invoice, receipt, bank statement, or contract submitted as text, returning the result as JSON or CSV. Endpoint: POST /v1/extract.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.