Connect Jitbit Helpdesk to MoEngage

Both apps 28Jitbit Helpdesk 20MoEngage 8

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

• Action
  Add or Remove User From Cohort (Audience)

  Adds users to, or removes users from, a partner-synced custom segment (cohort) in MoEngage. Only users who already exist in MoEngage are matched; no new users are created.

• Action
  Create or update device

  Creates a new device for an existing MoEngage user, or updates the properties of one of that user's devices. MoEngage accepts the request and processes it shortly afterwards.

• Action
  Create or Update User

  Creates a new MoEngage user or updates the attributes of an existing user.

• Action
  Delete users

  Requests permanent deletion of one MoEngage user, identified by customer ID or MoEngage ID. The user stays active for a 24-hour buffer period and cannot be retrieved once deleted.

• Action
  Fetch Campaign Report

  Downloads a generated MoEngage campaign report file by its file name. Reports can be downloaded for 7 days after they are generated.

• Action
  Find users

  Returns the MoEngage user profiles that match the Customer IDs or MoEngage IDs you specify, and lists any IDs that were not found.

• Action
  Import User Event

  Records one or more events a user performed, with their attributes and times, on the user's MoEngage profile. Creates the user if needed.

• Action
  Merge users

  Merges duplicate MoEngage user profiles by moving each merged user's data into the retained user. MoEngage cannot undo a merge, so check the user IDs before running it.

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