Connect Jitbit Helpdesk to Pylon

Both apps 45Jitbit Helpdesk 20Pylon 25

• 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 internal note to issue

  Adds an internal note to a Pylon issue. Internal notes are not visible to the requester.

• Action
  Add tag

  Creates a new tag in Pylon that can be applied to accounts, articles or issues.

• Action
  Add task

  Creates a task in Pylon with a title and optional details such as assignee, due date, account, project and status. Returns the new task.

• Action
  Create Account

  Creates a new customer account in Pylon with its name, domains, owner, tags and other details.

• Action
  Create Account Activity

  Creates a custom activity on a Pylon account's timeline.

• Action
  Create Call Recording

  Creates a call recording in Pylon from your own call recorder, including its transcript, and returns the new recording. Requires the Custom Call Recorder integration to be enabled in Pylon.

• Action
  Delete account

  Permanently deletes a Pylon account by its ID or external ID.

• Action
  Delete issue

  Permanently deletes an issue in Pylon.

• Action
  Find Account by Name

  Finds Pylon accounts by name, by exact or partial match, returning the matching accounts.

• Action
  Find contacts by criteria

  Returns the contacts that match the specified search text and/or filter.

• Action
  Find issues by criteria

  Returns Pylon issues matching a text search and/or a filter on fields such as state, assignee, account, tags or dates.

• Action
  Get account

  Returns a single Pylon account by its ID or external ID, including its domains, owner, tags, channels and custom fields.

• Action
  Get contact

  Returns a single contact, including its emails, phone numbers, account and custom field values, by its ID or external ID.

• Action
  Get issue

  Returns a single Pylon issue by its ID or issue number, including its custom field values. An error occurs if the issue is not found.

• Action
  Get user

  Returns a single Pylon team member by ID, including their name, email addresses, status, and assigned roles.

• Action
  Get Users

  Returns the users in your Pylon organization, optionally including deactivated users.

• Action
  List accounts

  Returns all accounts in your Pylon organization, including their domains, owner, tags and custom field values.

• Action
  List contacts

  Returns all contacts in the Pylon organization, including their emails, phone numbers, account and custom field values.

• Action
  List tags

  Returns all tags in the Pylon organization, with each tag's name, color and the type of object it applies to.

• Action
  List teams

  Returns all teams in the Pylon organization, with their members, how each team assigns issues, and any recurring assignment schedule.

• Action
  Reply to issue

  Sends a customer-facing reply on a Pylon issue, continuing an existing conversation or thread. Returns the ID of the new message and its issue.

• Action
  Update Account

  Updates an existing Pylon account. Only the fields you fill in are changed.

• Action
  Update contact

  Updates an existing Pylon contact by its ID or external ID. Only the fields you fill in are changed.

• Action
  Update issue

  Updates an existing Pylon issue — its title, state, assignee, team, account, requester, tags, type, portal visibility and custom fields. Only the fields you fill in are changed.

• Action
  Update Issue Followers

  Adds or removes users and contacts as followers of a Pylon issue, and returns the issue's resulting followers.

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