Integration
Connect Open Government, Canada to Customer.guru
When something happens in Open Government, Canada, your agent does the next thing in Customer.guru. 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 Customer.guru 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 Customer.guru
Triggers and actions 2 triggers · 7 actions
Trigger
New datasetFires when a new dataset is published to the Open Government portal.
- Find datasets
Search the Open Government portal's catalog of published datasets by keyword, tag, or organization.
- Find records in a data resource
Query the tabular records stored in a dataset's DataStore-backed resource, with filtering and search.
- Get dataset
Retrieve the full record for one published dataset, including its resources and metadata.
- Get organization
Retrieve details for one publishing organization, including its datasets.
- List organizations
List the government organizations that publish datasets on the portal.
Trigger
New RatingTriggered when a customer submits a new rating on one of your Customer.guru surveys, giving you their score, their comment and how they engaged with the survey email.
- Find Customer
Looks up a customer in your Customer.guru account by email address and returns that customer's record — their id, when they were added, their most recent survey score and comment, and whether they have unsubscribed.
- Schedule Survey
Sends a Customer.guru NPS survey to one or more customers, either straight away or scheduled for a later date, and reports how many went out.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.