Integration
Connect Open Government, Canada to Google Analytics
When something happens in Open Government, Canada, your agent does the next thing in Google Analytics. 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, Canada and Google Analytics 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, Canada and Google Analytics
Triggers and actions 1 trigger · 8 actions
Trigger
New datasetFires when a new dataset is published to the Open Government portal.
Action
Find datasetsSearch the Open Government portal's catalog of published datasets by keyword, tag, or organization.
Action
Find records in a data resourceQuery the tabular records stored in a dataset's DataStore-backed resource, with filtering and search.
Action
Get datasetRetrieve the full record for one published dataset, including its resources and metadata.
Action
Get organizationRetrieve details for one publishing organization, including its datasets.
Action
List organizationsList the government organizations that publish datasets on the portal.
Action
Get AccountTool to retrieve a single account by its resource name. use when you need detailed account info after confirming the account resource name (e.g., accounts/100).
Action
List AccountsTool to list all accounts accessible by the caller. use when you need to enumerate all google analytics accounts your credentials can access.
Action
List AudiencesTool to list all audiences on a property. use when you need to fetch all audiences for a ga4 property after confirming its existence.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.