Connect Feathery and Jitbit Helpdesk

Both apps 33Feathery 13Jitbit Helpdesk 20

• Trigger
  Data Received

  Triggers when an end user submits or updates data on a Feathery form.

• Trigger
  Form Completion

  Triggers when an end user completes a Feathery form.

• Action
  Create Hidden Field

  Creates a hidden field in your Feathery account.

• Action
  Create or Fetch User

  Creates a Feathery end user with the given ID, or returns the existing user, including its SDK key.

• Action
  Create or Update Submission

  Sets field values for a Feathery user and initializes submissions on the given forms.

• Action
  Delete User

  Deletes a Feathery end user and their submissions.

• Action
  Get User Field Data

  Returns every field value a Feathery user submitted across forms.

• Action
  Get User Form Session

  Returns a Feathery user's form session: every form they are working on and their progress.

• Action
  List Document Templates

  Returns document templates uploaded by your Feathery team, optionally filtered by name or tags.

• Action
  List Forms

  Returns your Feathery forms, optionally filtered by tags or active status.

• Action
  List Form Submissions

  Returns submissions for a Feathery form, optionally filtered by user, completion and update time.

• Action
  List Hidden Fields

  Returns all hidden fields in your Feathery account.

• Action
  List Users

  Returns your Feathery end users, optionally filtered by creation time or a field value.

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