Integration
Connect Open Government, Canada to LaGrowthMachine
When something happens in Open Government, Canada, your agent does the next thing in LaGrowthMachine. 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 LaGrowthMachine 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 LaGrowthMachine
Triggers and actions 1 trigger · 9 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
Create Lead in an AudienceCreate a lead in an LGM audience.
Action
Import Leads From LinkedIn Search URLCreate an LGM audience and import leads from a LinkedIn Regular or Sales Navigator search
Action
List AudiencesList the audiences on the LaGrowthMachine account, with their IDs, names, sizes and source URLs.
Action
List IdentitiesList the identities on the LaGrowthMachine account, including the identity ID required to import leads from a LinkedIn search URL.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.