Connect Jitbit Helpdesk and Yay! Forms

Both apps 33Jitbit Helpdesk 20Yay! Forms 13

• Trigger
  New Ticket

  Triggers when a new ticket is created in Jitbit Helpdesk, optionally limited to a category, section, status, submitter, company, technician or tag.

• Action
  Add article

  Creates a new knowledge base article in a category.

• Action
  Add asset

  Creates a new asset in Jitbit Helpdesk with its model, manufacturer, type and supplier.

• Action
  Add company

  Creates a new company in Jitbit Helpdesk, or returns the existing company's id if the name is taken.

• Action
  Add tag to ticket

  Adds a tag to a ticket. The tag is created if it does not already exist.

• Action
  Add time spent

  Logs a time spent entry on a ticket under the connected user. Requires technician permissions.

• Action
  Create New Reply

  Posts a new reply (comment) to an existing helpdesk ticket.

• Action
  Create Ticket

  Creates a new helpdesk ticket in a category, with a subject, body and priority.

• Action
  Create User

  Creates a new helpdesk user. Requires administrator permissions.

• Action
  Find Ticket

  Searches tickets by text, optionally narrowed by submitter, category, status, assignee and creation date, and returns the matching tickets.

• Action
  Find User

  Finds a helpdesk user by their email address and returns their profile.

• Action
  Get Article

  Returns a knowledge base article with its full content, category, tags and attachments.

• Action
  Get ticket

  Returns a helpdesk ticket's details, including its status, category, submitter, assignee, tags, attachments and custom field values.

• Action
  List Companies

  Returns every company in your Jitbit helpdesk with its name, email domain and notes. Requires an administrator account.

• Action
  List Ticket Comments

  Returns all comments (replies) posted on a Jitbit Helpdesk ticket.

• Action
  List tickets

  Returns the helpdesk tickets the connected user can see, optionally filtered by mode, category, status, submitter, company, assignee, tag and dates.

• Action
  List Time Spent Entries

  Returns every time spent entry logged against a ticket, including who logged it, the seconds spent and when. Requires technician permissions.

• Action
  Update company

  Updates a company's name, notes and email domains in Jitbit Helpdesk.

• Action
  Update ticket

  Updates one or more properties of an existing helpdesk ticket, such as its status, priority, category, assignee, due date, tags, subject or body.

• Action
  Update user

  Updates an existing helpdesk user's profile, such as name, email, contact details, company, department, password and account status. Requires administrator permissions.

• Trigger
  New Response

  Triggers when a new response is submitted.

• Action
  Create Field

  Adds a new question field to a Yay! Forms form and returns the created field.

• Action
  Create Form

  Creates a new form in a Yay! Forms workspace and returns the created form, including its ID and public key.

• Action
  Delete Field

  Deletes one question field from a Yay! Forms form.

• Action
  Delete Form

  Deletes a Yay! Forms form along with its fields and responses.

• Action
  Get Form

  Returns one Yay! Forms form with its settings, theme, status and response counts.

• Action
  Get Form Stats

  Returns view, start and response counts for a Yay! Forms form, plus its completion rate and average time to complete.

• Action
  List Fields

  Returns every question field on a Yay! Forms form, in the order they appear.

• Action
  List Forms

  Returns the forms in a Yay! Forms workspace, one page at a time.

• Action
  List Responses

  Returns the responses submitted to a Yay! Forms form, one page at a time.

• Action
  List Workspaces

  Returns the Yay! Forms workspaces you have access to, with each workspace's id, name and plan.

• Action
  Update Field

  Updates one question field on a Yay! Forms form. Anything you leave blank keeps its current value.

• Action
  Update Form

  Updates a Yay! Forms form's details and settings. Anything you leave blank keeps its current value.

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