Connect FormHug and Jitbit Helpdesk

Both apps 32FormHug 12Jitbit Helpdesk 20

• Trigger
  New Or Updated Submission

  Triggers when a submission is created or edited on the chosen form.

• Action
  Add entry

  Creates a new entry (submission) on one of your FormHug forms.

• Action
  Add folder

  Creates a new folder for organizing forms, at the root or inside an existing folder.

• Action
  Add form

  Creates a new FormHug form, optionally with initial questions, locale, timezone, folder and header theme.

• Action
  Get current user

  Returns the FormHug user associated with the connected account, including their billing account and current subscription plan.

• Action
  Get entry

  Returns one submitted entry of a form, including every answer keyed by the form field's API code.

• Action
  Get form

  Returns a form's details, including its name, settings, folder and the full list of its fields.

• Action
  List entries

  Returns the entries (submissions) of one of your forms, optionally filtered and sorted.

• Action
  List folders

  Returns all folders owned by the connected FormHug user, newest first.

• Action
  List forms

  Returns the forms you created or that were shared with you, optionally filtered by name or folder.

• Action
  Update entry

  Updates an existing entry on a form. Only the fields you supply change; all other answers stay as they are.

• Action
  Update form

  Updates a form's name, description, locale, timezone, layout or question list. Only the values you provide are changed.

• 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.

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