Integration
Connect Open Government, ACT to Reepay
When something happens in Open Government, ACT, your agent does the next thing in Reepay. 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 Reepay 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 Reepay
Triggers and actions 1 trigger · 23 actions
Trigger
New record in datasetPolling trigger that fires when new rows are published to a specified ACT open-data dataset.
- Find datasets
Search the ACT Government open-data catalog for published datasets by keyword, category, or tag (Socrata catalog API).
- Get dataset metadata
Retrieve a dataset's metadata — column schema, description, publisher, update frequency — for a given ACT open-data dataset id.
- List dataset records
Retrieve rows from a specific ACT open-data dataset, with optional filtering, sorting, and paging (Socrata SODA resource API).
Action
Add couponCreate a new coupon. POST /v1/coupon
- Add credit
Create a credit note/credit for a customer. POST /v1/credit
- Add customer
Create a new customer. POST /v1/customer
- Add invoice
Create an invoice for a customer. POST /v1/customer/{handle}/invoice
- Add plan
Create a new subscription plan. POST /v1/plan
- Add subscription
Create a new subscription for a customer. POST /v1/subscription
- Cancel subscription
Cancel a subscription by handle. POST /v1/subscription/{handle}/cancel
- Delete customer
Delete a customer by handle. DELETE /v1/customer/{handle}
- Get charge
Retrieve a charge by handle. GET /v1/charge/{handle}
- Get coupon
Retrieve a coupon by handle. GET /v1/coupon/{handle}
- Get customer
Retrieve a customer by handle. GET /v1/customer/{handle}
- Get invoice
Retrieve an invoice by id. GET /v1/invoice/{id}
- Get plan
Retrieve the current version of a plan by handle. GET /v1/plan/{handle}/current
- Get subscription
Retrieve a subscription by handle. GET /v1/subscription/{handle}
- List customers
List all customers. GET /v1/list/customer
- List invoices
List all invoices. GET /v1/list/invoice
- List plans
List all plans. GET /v1/list/plan
- List subscriptions
List all subscriptions. GET /v1/list/subscription
- Update customer
Update an existing customer by handle. PUT /v1/customer/{handle}
- Update subscription
Change/update an existing subscription by handle. PUT /v1/subscription/{handle}
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.