Integration
Connect Open Government, ACT to CrowdKit
When something happens in Open Government, ACT, your agent does the next thing in CrowdKit. 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, ACT and CrowdKit 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, ACT and CrowdKit
Triggers and actions 1 trigger ยท 11 actions
Trigger
New record in datasetPolling trigger that fires when new rows are published to a specified ACT open-data dataset.
Action
Find datasetsSearch the ACT Government open-data catalog for published datasets by keyword, category, or tag (Socrata catalog API).
Action
Get dataset metadataRetrieve a dataset's metadata โ column schema, description, publisher, update frequency โ for a given ACT open-data dataset id.
Action
List dataset recordsRetrieve rows from a specific ACT open-data dataset, with optional filtering, sorting, and paging (Socrata SODA resource API).
Action
Delete LocationDelete a location by id. DELETE /locations/{locationId}.
Action
Delete PorterDelete a Porter by id. DELETE /porters/{porterId}.
Action
Get LocationRetrieve a single location by id. GET /locations/{locationId}.
Action
Get PorterRetrieve a single Porter by id. GET /porters/{porterId}.
Action
List LocationsReturn all locations for the authenticated user. GET /locations.
Action
List PortersReturn all Porters in the account. GET /porters.
Action
Update LocationUpdate fields on an existing location. PATCH /locations/{locationId}.
Action
Update PorterUpdate fields on an existing Porter. PATCH /porters/{porterId}.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.