Integration
Connect Open Government, ACT to Print Autopilot
When something happens in Open Government, ACT, your agent does the next thing in Print Autopilot. 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 Print Autopilot 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 Print Autopilot
Triggers and actions 1 trigger ยท 6 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
Create PrinterRegisters a printer in Print Autopilot so it can be used in print queues. You give the printer a name and the paper sizes it supports.
Action
Finish Print JobsMarks a queued Print Autopilot document as finished, reporting whether it printed successfully or failed. Use it to close out a print job after your printer handled it.
Action
List Print JobsReturns the print jobs waiting in your Print Autopilot queue, each with its printer, paper size, and the queued documents.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.