avanta

Consume avanta API

Actions57

Company Actions
- Create or Update
- Deactivate
- Delete
- Get Many
Company - Address Actions
- Create or Update
- Delete
- Get Many
Company - User Actions
- Create or Update
Company - Contact Actions
- Create or Update
- Delete
- Get Many
- Link to Company
- Link to Sales Org
Company - Group Actions
- Create or Update
- Delete
- Get Many
Company - Role Actions
- Create or Update
- Delete
- Get Many
Company - Rule Actions
- Create or Update
- Get Many
Company - Sku Actions
- Create or Update
- Delete
Company - Restrict Actions
- Create or Update
- Delete
Sales Organization Actions
- Create or Update
- Delete
- Get Many
Product Actions
- Create or Update
- Delete
- Get Many
Category Actions
- Create or Update
Servicecenter - Order Actions
- Create or Update
- Get Many
Servicecenter - Invoice Actions
- Create or Update
- Get Many
Servicecenter - Credit Memo Actions
- Create or Update
- Get Many
Servicecenter - Shipment Actions
- Create or Update
- Get Many
Servicecenter - Tracking Actions
- Create or Update
- Get Many
Servicecenter - Reshipment Actions
- Create or Update
- Get Many
Servicecenter - Backorder Actions
- Create or Update
- Get Many
Requests - Inquiry Actions
- Create or Update
- Get Many
Requests - Ticket Actions
- Create or Update
- Get Many
Requests - Return Registration Actions
- Create or Update
- Get Many
Download Actions
- Create Category
- Remove Category
- Create Item
- Remove Item
Bill of Material Actions
- Create or Update

Requests - Ticket → Create or Update

AI-generated

Overview

This node handles the creation or updating of tickets within the Requests - Ticket resource. It is useful for automating ticket management workflows, such as creating new support tickets with detailed comments, associating tickets with customers and companies, and updating ticket statuses. Practical examples include creating a new support ticket with multiple comments, setting watchers for ticket notifications, or updating ticket details based on external triggers.

Use Case Examples

Create a new support ticket with subject, ticket number, and comments.
Update an existing ticket's status and add watchers for notifications.
Use bulk API to create multiple tickets efficiently.

Properties

Name	Meaning
Request Options	Options to control API request behavior such as debug mode, SSL validation, and timeout settings.
Return to Webhook	Whether to return the response to a webhook, requiring a 'Respond to Webhook' node after this node.
Use Bulk API	Whether to use the bulk API for processing multiple items.
Dataflow ID	Optional override for the dataflow ID, automatically read from webhook input if not set.
Company Customer ID	Customer ID of the company.
Ticket Number	Unique identifier for the ticket, required for creation.
Subject	Subject or title of the ticket, required for creation.
Website ID	Identifier for the website associated with the ticket, required for creation.
Store ID	Identifier for the store associated with the ticket, required for creation.
Comment Type	Method to add comments, either using mapped fields or raw JSON.
Comments	Collection of comments with user name, content, and creation date, used when Comment Type is 'Fields Below'.
Comments JSON	Raw JSON input for comments, used when Comment Type is 'JSON'.
Additional Fields	Additional optional fields such as watchers, status, company ID, ticket ID, external ID, extension attributes, user ID, customer name, and customer email.

Output

JSON

ticket_id - Internal ticket identifier assigned or updated.
ticket_number - Unique ticket number.
subject - Subject or title of the ticket.
website_id - Website identifier associated with the ticket.
store_id - Store identifier associated with the ticket.
comments - Array of comments added to the ticket.
status - Current status of the ticket.
watchers - List of email addresses watching the ticket.
company_id - Internal company identifier linked to the ticket.
external_id - External system identifier for the ticket.
extension_attributes - Custom extension attributes associated with the ticket.
user_id - Internal user ID of the ticket author.
customer - Name of the ticket author.
customer_email - Email of the ticket author.

Dependencies

An API key credential for avanta API authentication

Troubleshooting

Ensure required fields like Ticket Number, Subject, Website ID, and Store ID are provided to avoid validation errors.
If using bulk API, verify that the dataflow ID is correctly set or available in the webhook input to prevent processing errors.
Enable Debug Mode to get detailed API request information for troubleshooting connectivity or data issues.
If SSL certificate validation fails, consider enabling 'Ignore SSL Issues' option, but be aware of security risks.
When returning response to webhook, ensure a 'Respond to Webhook' node follows this node to handle the response properly.

avantaInstall