Integration
Connect Open Government, Canada to Emailr
When something happens in Open Government, Canada, your agent does the next thing in Emailr. 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 Emailr 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 Emailr
Triggers and actions 1 trigger · 17 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.
Action
Add contactCreate a contact. POST /v1/contacts
- Add segment
Create a contact segment. POST /v1/segments
- Add template
Create an email template. POST /v1/templates
- Delete contact
Delete a contact by ID. DELETE /v1/contacts/{id}
- Delete segment
Delete a segment by ID. DELETE /v1/segments/{id}
- Delete template
Delete a template by ID. DELETE /v1/templates/{id}
- Get contact
Fetch a contact by ID. GET /v1/contacts/{id}
- Get template
Fetch a template by ID. GET /v1/templates/{id}
- List segments
List contact segments. GET /v1/segments
- Update contact
Update a contact by ID. PUT /v1/contacts/{id}
- Update segment
Update a segment by ID. PUT /v1/segments/{id}
- Update template
Update a template by ID. PUT /v1/templates/{id}
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.