Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation updates a custom ticketing template in a ticket management system. It allows users to modify the details of an existing ticket template by specifying its ID and providing new data for the template's configuration. This is useful in scenarios where organizations need to customize how tickets are structured, displayed, or integrated with other systems.

Practical examples include:

  • Updating the list of companies associated with a ticket template.
  • Modifying integration settings related to the ticket template.
  • Changing detailed template information such as fields, layout, or metadata.

Properties

Name Meaning
X USER ID The user identifier required for authentication or tracking purposes in the API request.
Data JSON object containing the updated template details. It includes keys like companies_list, integrations, and template_details. Each key expects an array (as stringified JSON) representing respective configurations.
Id Numeric identifier of the ticket template to update.

Output

The node outputs JSON data representing the response from the API after attempting to update the ticket template. This typically includes confirmation of the update, the updated template data, or error messages if the update failed.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating requests to the Connect Secure API.
  • Depends on the Connect Secure API endpoint that manages ticket templates.
  • The node uses the OpenAPI specification defined in openapi.json to build its properties and operations.

Troubleshooting

  • Missing or invalid X USER ID: The API may reject requests without a valid user ID header. Ensure this property is correctly set.
  • Invalid JSON in Data property: The data field must be valid JSON. Malformed JSON will cause errors.
  • Incorrect template Id: Providing an invalid or non-existent template ID will result in failure to update.
  • API authentication errors: Ensure the API key credential is configured properly in n8n.
  • Network or connectivity issues: Verify network access to the Connect Secure API endpoint.

Links and References

Discussion