Connect Cisco WebEx and Jitbit Helpdesk

Both apps 32Cisco WebEx 12Jitbit Helpdesk 20

• Trigger
  New meeting

  Fires when a meeting is created. Webhook resource=meetings event=created

• Trigger
  New message

  Fires when a message is created in a space.

• Action
  Add meeting

  Schedules a new Webex meeting (or webinar / personal room meeting) and returns the created meeting.

• Action
  Add message

  Posts a plain-text or Markdown message, optionally with one file or one card, to a Webex space or directly to a person.

• Action
  Add room

  Creates a Webex space (room). The connected user is automatically added as a member.

• Action
  Delete meeting

  Deletes a scheduled meeting or an entire meeting series. A deleted meeting cannot be recovered.

• Action
  Find people by criteria

  Returns up to 100 people in the Webex organization that match the specified email, name, IDs, roles or location.

• Action
  Get meeting

  Retrieves the details of a Webex meeting series, scheduled meeting or meeting instance by its id.

• Action
  Get membership

  Returns one space membership: who the member is, which space, and whether they moderate it.

• Action
  List messages

  Lists the messages in a Webex space, newest first. Optionally narrow to replies in one thread, messages mentioning you, or messages sent before a date or message.

• Action
  List rooms

  List the Webex spaces (rooms) the connected user belongs to, optionally filtered by team or type.

• Action
  Update meeting

  Updates a meeting series or a single scheduled meeting in Webex. Only the fields you fill in 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.