eKyte icon

eKyte

Create and retrieve data from eKyte (tasks, projects, tickets, boards, workspaces, notes, notifications)

Actions25

Ticket → Create

AI-generated

Overview

This node operation creates a new ticket in the eKyte system. It is useful for tracking issues, requests, or inquiries within a workspace, allowing users to specify details such as subject, ticket type, priority, requester, and responsible analyst. For example, a support team can use this node to log customer service requests or bug reports with relevant metadata for efficient handling.

Use Case Examples

  1. Creating a new support ticket with a subject, priority, and detailed description.
  2. Logging a bug fix request with an assigned analyst and expected due date.

Properties

Name Meaning
Base URL The base URL for the eKyte API, used to construct the API endpoint for the request.
Email The email address of the eKyte user performing the ticket creation operation.
Workspace ID The unique identifier of the workspace where the ticket will be created.
Priority Priority level of the ticket as a number from 0 to 100, indicating urgency.
Subject The subject line of the ticket, summarizing the issue or request.
Ticket Type The category of the ticket being created, such as Request, Question, Bug Fix, Quote, or Improvement.
Expected Due Date The expected resolution date for the ticket in ISO 8601 format.
Requester Email The email of the person who created the request, can be any user including guests.
CC Users Comma-separated list of user emails to be CC'd on the ticket.
Analyst Email The main responsible analyst for handling the ticket; if not provided, a default is assigned.
Description Detailed description of the ticket including relevant information and context.
Artifact IDs List of numeric artifact IDs to attach to the ticket.

Output

JSON

  • json - The JSON response from the eKyte API representing the created ticket details.

Dependencies

  • eKyte API
  • API key credential for authentication

Troubleshooting

  • Common issues include invalid or missing required parameters such as user email, workspace ID, or subject.
  • API errors may occur if the user email is not authorized or if the workspace ID does not exist.
  • Error messages from the API are parsed and presented to help identify issues, such as invalid ticket type or malformed request body.

Links

Discussion