Connect Open Government, Queensland Government to Moxie

Both apps 56Open Government, Queensland Government 11Moxie 45

• Trigger
  New dataset

  Fires when a new dataset is published on the Queensland Government open data portal.

• Action
  Find datasets by criteria

  Search datasets on the portal by keyword, tag, organization, or other facets.

• Action
  Find resources by criteria

  Search across all data resources by field/value criteria.

• Action
  Get dataset

  Retrieve the full metadata and resource list for a single dataset by its id or name.

• Action
  Get group

  Returns 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 organization

  Returns 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 resource

  Returns one published file or service of the Queensland open data catalogue by its file id, including its download link, format and size.

• Action
  List datasets

  Returns the short name of each dataset on the Queensland Government open data portal, up to 1000 per call.

• Action
  List groups

  Returns 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 organizations

  Returns 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 tags

  Returns 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
  Agreement Sent

  Triggers when a proposal is sent either via link or email.

• Trigger
  Agreement Signed

  Triggers when an agreement is accepted and signed with e-signature.

• Trigger
  Agreement Viewed

  Triggers when a user views the proposal.

• Trigger
  Client Created

  Triggers when a new client is created in Moxie.

• Trigger
  Client Deleted

  Triggers when a client record is deleted in Moxie.

• Trigger
  Client Updated

  Triggers when a client record is updated in Moxie.

• Trigger
  Form Completed

  Triggers when a form is completed.

• Trigger
  Invoice Sent

  Triggers when an invoice is sent in Moxie.

• Trigger
  Meeting Cancelled

  Triggers when a meeting is cancelled

• Trigger
  Meeting Scheduled

  Triggers when a new meeting is scheduled

• Trigger
  Meeting Updated

  Triggers when a meeting is updated or rescheduled

• Trigger
  Opportunity Created

  Triggered with a pipeline opportunity is created

• Trigger
  Opportunity Deleted

  Triggered with a pipeline opportunity is deleted

• Trigger
  Opportunity Updated

  Triggered with a pipeline opportunity is updated

• Trigger
  Payment Received

  Triggers when a payment is received either vial Stripe or manual entry.

• Trigger
  Project Completed

  Triggers when a project is set to "complete" in Moxie.

• Trigger
  Project Created

  Triggers when a new project is created in Moxie.

• Trigger
  Project Updated

  Triggers when the settings for a project are updated.

• Trigger
  Proposal Sent

  [DEPRECATED - Please use "Agreement Sent"] - Triggers when a proposal is sent either via link or email.

• Trigger
  Proposal Signed

  [DEPRECATED - Please use "Agreement Signed"] - Triggers when a proposal is accepted and signed with e-signature.

• Trigger
  Proposal Viewed

  [DEPRECATED - Please use "Agreement Viewed"] - Triggers when a user views the proposal.

• Trigger
  Task Approval

  Triggers when a new Deliverable is ready for client approval.

• Trigger
  Task Created

  Triggered when a Project Task is created

• Trigger
  Task Deleted

  Triggered when a Project Task is deleted

• Trigger
  Task Updated

  Triggered with a Project Task is updated.

• Trigger
  Ticket Closed

  Triggers and a support ticket is closed

• Trigger
  Ticket Comment

  Triggers when a comment is created on a ticket

• Trigger
  Ticket Created

  Triggers when a new support ticket is created

• Trigger
  Ticket Deleted

  Triggers when a support ticket is deleted

• Trigger
  Ticket Updated

  Triggers when a support ticket is updated

• Trigger
  Time Worked Created

  Triggers when a new time worked entry is created.

• Trigger
  Time Worked Deleted

  Triggers when a time worked record is deleted.

• Trigger
  Time Worked Updated

  Triggers when a time worked entry has been updated.

• Action
  Create Client

  Creates a new client record in Hectic

• Action
  Create Expense

  Records a new expense in your Moxie accounting records, optionally filed under a vendor and allocated to a client.

• Action
  Create Opportunity

  Create a new pipeline opportunity

• Action
  Create & Optionally Send Invoice

  Creates an invoice for a client from the line items you supply, and emails it straight away when you fill in who to send it to. Left blank, the invoice is saved as a draft.

• Action
  Create or Update Calendar Event

  Create or update a calendar event in Moxie

• Action
  Create Project

  Create a project and optionally use a template

• Action
  Create Task

  Create a task in the project management system

• Action
  Create Ticket

  Create a Ticket for a client and contact

• Action
  Create Ticket Comment

  Adds a comment (public or private) to an existing ticket.

• Action
  Create Time Worked

  Creates a time worked entry

• Action
  Delete Calendar Event

  Deletes a calendar event in Moxie by the external ID.

• Action
  Find a Client

  Finds a client by either name or contact email address.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.