Connect Leiga and Ventrata

Both apps 28Leiga 16Ventrata 12

• Trigger
  Updated Issue

  Triggers when an issue is updated in Leiga.

• Action
  Add comment

  Adds a comment to a Leiga issue or other record, optionally as a reply to an existing comment.

• Action
  Add epic

  Creates a new epic in a Leiga project.

• Action
  Add project

  Creates a new project in Leiga from a project template, with a name, leader and optional description.

• Action
  Add version

  Creates a new version (release) in Leiga with a name, owner, and optional description, start date and estimated release date.

• Action
  Create Issue

  Creates a new issue in a Leiga project with the issue type and field values you provide.

• Action
  Delete issue

  Deletes an issue from a Leiga project.

• Action
  Find issues by criteria

  Searches the issues in a Leiga project matching a summary keyword, status types, field values or date ranges, and returns the matching issues.

• Action
  Get issue

  Returns the full details of a Leiga issue, including its custom field values, by issue ID.

• Action
  Get project

  Returns the details of a Leiga project by its ID.

• Action
  Get version

  Returns the details of a Leiga version, including its name, status and release dates.

• Action
  List comments

  Returns the comments on a Leiga issue or other item, including replies and attachments.

• Action
  List Issue Types

  Returns the issue types (such as bug or task) available in a Leiga project.

• Action
  List projects

  Returns all projects in your Leiga organization with their id, name, key and archived status.

• Action
  Update issue

  Updates an existing Leiga issue's field values, such as its summary, description, status, priority, assignee or labels.

• Action
  Update project

  Updates a Leiga project's overview fields, such as its name or start time.

• Trigger
  Updated Booking

  Triggers when any booking is created, updated, cancelled, or redeemed, including changes to customer details, products, options, quantities, or status.

• Action
  Add booking

  Reserves availability by creating an ON_HOLD booking. Confirm it afterwards with Confirm booking.

• Action
  Confirm booking

  /bookings/{uuid}/confirm - confirm an on-hold booking with contact details (OCTO Core).

• Action
  Delete booking

  /bookings/{uuid} - cancel a booking with optional reason (OCTO Core).

• Action
  Find availability

  /availability - search availability for a product/option over a date range or specific dates (OCTO Core).

• Action
  Find availability calendar

  /availability/calendar - daily availability summary for a product/option over a date range (OCTO Core).

• Action
  Find Booking

  Find bookings by reference, date, contact details or other filters. At least one primary filter is required.

• Action
  Get booking

  /bookings/{uuid} - retrieve a booking by UUID (OCTO Core).

• Action
  Get product

  /products/{id} - retrieve one product with its options and units (OCTO Core).

• Action
  Get supplier

  Returns the supplier the connected API key belongs to (name, reference, website, contact details).

• Action
  List products

  /products - list all bookable products for the supplier (OCTO Core).

• Action
  Update booking

  /bookings/{uuid} - amend an existing booking (date/time, units, contact) (OCTO Core).

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