AvantGuard - WebhookSite icon

AvantGuard - WebhookSite

AvantGuard - WebhookSite

Actions100

Overview

This node operation allows users to create a new procedure by duplicating an existing template procedure. It is useful in scenarios where you want to quickly generate a procedure based on a predefined template, optionally customizing it with specific details such as company association, name, and description. For example, a user can duplicate a standard onboarding procedure template and assign it to a particular company with a custom name and description.

Properties

Name Meaning
Id The ID of the template procedure to duplicate. This is required to specify which template to use.
Additional Query Parameters Optional parameters to customize the new procedure:
- Company Id The ID of the company for which the new procedure is created. If omitted, the procedure will be global.
- Name A new name for the duplicated procedure.
- Description A new description for the duplicated procedure.

Output

The node outputs JSON data representing the newly created procedure. This typically includes details such as the procedure's unique identifier, name, description, associated company (if any), and other metadata returned from the API after creation. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authentication to the external service managing procedures.
  • The node uses a base URL configured in credentials to send requests.
  • The operation sends HTTP requests with query parameters to create the procedure from the template.

Troubleshooting

  • Missing or invalid template ID: If the provided template ID does not exist or is invalid, the API may return an error indicating the template was not found. Ensure the ID is correct.
  • Insufficient permissions: If the API key lacks permission to create procedures or access the specified company, errors related to authorization may occur.
  • Invalid additional parameters: Providing incorrect types or invalid values for optional parameters like company ID, name, or description might cause request failures.
  • Network or configuration issues: Ensure the base URL and credentials are correctly set up in n8n to avoid connection errors.

Links and References

  • Refer to the external API documentation for procedures management to understand all available fields and constraints when creating procedures from templates.
  • Consult n8n documentation on how to configure API credentials and handle HTTP request nodes for similar integrations.

Discussion