Integration
Connect Open Government, Australia to Gorgias
When something happens in Open Government, Australia, your agent does the next thing in Gorgias. 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, Australia and Gorgias 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, Australia and Gorgias
Triggers and actions 3 triggers · 20 actions
Trigger
Dataset updatedFires when a dataset is updated on the portal, detected by polling package_search sorted by last-modified date.
Action
Find datasetsSearch Australian government open datasets by keyword, tag, organization, or format (CKAN package_search).
Action
Find resourcesSearch dataset resources (files/links) by field values such as format or url (CKAN resource_search).
Action
Get datasetRetrieve full details of a dataset by its id or name, including its resources (CKAN package_show).
Action
Get groupRetrieve details of a dataset group by id or name, including its member datasets (CKAN group_show).
Action
Get organizationRetrieve details of a publishing organization by id or name, including its datasets (CKAN organization_show).
Action
Get resourceRetrieve details of a single dataset resource by its id, including download url and format (CKAN resource_show).
Action
List datasetsList the names of all datasets on the portal (CKAN package_list).
Trigger
New ticketFires when a new ticket is created in Gorgias. Poll GET https://{domain}.gorgias.com/api/tickets ordered by created_datetime, or vendor webhook event ticket-created.
Trigger
New ticket messageFires when a new message is added to a ticket. Poll GET https://{domain}.gorgias.com/api/tickets/{id}/messages, or vendor webhook event message-created.
Action
Add customerCreate a new customer profile. POST https://{domain}.gorgias.com/api/customers
Action
Add tag to ticketApply a tag to a ticket. POST https://{domain}.gorgias.com/api/tickets/{id}/tags or PUT ticket with tags array
Action
Create TicketCreates a ticket
Action
Create Ticket MessageCreates a Ticket Message in an existing ticket
Action
Delete ticketDelete a ticket by id. DELETE https://{domain}.gorgias.com/api/tickets/{id}
Action
Find customers by emailSearch/list customers, filterable by email and other criteria. GET https://{domain}.gorgias.com/api/customers
Action
Get customerRetrieve a single customer by id. GET https://{domain}.gorgias.com/api/customers/{id}
Action
Get ticketRetrieve a single ticket by id. GET https://{domain}.gorgias.com/api/tickets/{id}
Action
Get Ticket MessageLook up one message by its id and return its details, including its body, subject, channel, sender, receiver and whether the customer can see it.
Action
List ticket messagesList messages belonging to a ticket. GET https://{domain}.gorgias.com/api/tickets/{id}/messages
Action
List ticketsList tickets with optional filters (status, customer, tags). GET https://{domain}.gorgias.com/api/tickets
Action
Update customerUpdate fields on an existing customer record. PUT https://{domain}.gorgias.com/api/customers/{id}
Action
Update ticketUpdate fields on an existing ticket (status, priority, assignee, tags). PUT https://{domain}.gorgias.com/api/tickets/{id}
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews