Connect Jitbit Helpdesk to Stedi

Both apps 29Jitbit Helpdesk 20Stedi 9

• 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 event destination

  Create a new event destination for receiving Stedi webhook events.

• Action
  Check eligibility

  Runs a real-time eligibility and benefits check (X12 270/271) against a payer for a patient and returns the payer's coverage and benefits response.

• Action
  Delete event destination

  Permanently deletes a Stedi event destination so it stops receiving events. This cannot be undone; to pause delivery instead, update the destination's status to DISABLED.

• Action
  Find payers by criteria

  Searches the Stedi Payer Network for payers matching a name, payer ID or alias, optionally filtered by supported transaction types, coverage types, operating states and insurance programs. Returns matching payers ranked by relevance.

• Action
  Get event destination

  Retrieve an event destination by id.

• Action
  Get payer

  Retrieve a single payer record by id.

• Action
  List event destinations

  Lists the event destinations configured in your Stedi account, optionally filtered by status or event type.

• Action
  List payers

  Lists every payer Stedi supports, with payer IDs, aliases, supported transactions and enrollment requirements.

• Action
  Update event destination

  Updates an existing Stedi event destination's name, URL, subscribed event types, description, status or concurrency limit. Fields left blank are not changed.

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