Integration
Connect Open Government, Queensland Government to PostHog
When something happens in Open Government, Queensland Government, your agent does the next thing in PostHog. 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, Queensland Government and PostHog 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, Queensland Government and PostHog
Triggers and actions 2 triggers · 20 actions
Trigger
New datasetFires when a new dataset is published on the Queensland Government open data portal.
Action
Find datasets by criteriaSearch datasets on the portal by keyword, tag, organization, or other facets.
Action
Find resources by criteriaSearch across all data resources by field/value criteria.
Action
Get datasetRetrieve the full metadata and resource list for a single dataset by its id or name.
Action
Get groupReturns one thematic group of the Queensland open data catalogue by its short name, with its title, description and dataset count. The portal blocks its own group endpoint, so the group is read from a dataset search instead; a group with no datasets is reported as not found.
Action
Get organizationReturns one publishing organisation of the Queensland open data catalogue by its short name, with its title, description and dataset count. The portal blocks its own organisation endpoint, so the organisation is read from a dataset search instead; an organisation with no datasets is reported as not found.
Action
Get resourceReturns one published file or service of the Queensland open data catalogue by its file id, including its download link, format and size.
Action
List datasetsReturns the short name of each dataset on the Queensland Government open data portal, up to 1000 per call.
Action
List groupsReturns every thematic group datasets are filed under on the Queensland open data portal, with a dataset count for each. The portal blocks its own group-list endpoint, so the groups are read from the dataset search's grouped counts.
Action
List organizationsReturns every publishing organisation on the Queensland open data portal, with a dataset count for each. The portal blocks its own organisation-list endpoint, so the organisations are read from the dataset search's grouped counts.
Action
List tagsReturns the tags used to label datasets on the Queensland open data portal, optionally narrowed to tags containing given text or belonging to one vocabulary.
Trigger
Action PerformedTriggers when an action is performed by a user.
Action
Add annotationCreate a new annotation on the project timeline (content, date_marker, scope). POST /api/projects/:project_id/annotations/
Action
Capture EventCaptures an event.
Action
Evaluate feature flagsEvaluate all feature flag values for a given distinct_id/person, returning flag states for use in automation branching. Public POST /flags endpoint (project token auth).
Action
Get personRetrieve a single person by ID. GET /api/projects/:project_id/persons/:id/
Action
List annotationsList annotations in the project. GET /api/projects/:project_id/annotations/
Action
List cohortsList cohorts defined in the project. GET /api/projects/:project_id/cohorts/
Action
List feature flagsList feature flags defined in the project. GET /api/projects/:project_id/feature_flags/
Action
List insightsList saved insights (charts/graphs) in the project. GET /api/projects/:project_id/insights/
Action
List personsList/search persons in the project, optionally filtered by distinct_id or properties. GET /api/projects/:project_id/persons/
Action
Update personUpdate a person's properties by ID. PATCH /api/projects/:project_id/persons/:id/
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.