Actions100
- Activity Log Actions
- Article Actions
- Asset Actions
- Asset Layout Actions
- Asset Layout Field Actions
- Asset Password Actions
- Card Actions
- Company Actions
- Expiration Actions
- Folder Actions
- IP Address Actions
- List Actions
- Magic Dash Actions
- Matcher Actions
- Network Actions
- Password Folder Actions
- Procedure Actions
- Procedure Task Actions
- Public Photo Actions
- Rack Storage Actions
- Rack Storage Item Actions
Overview
This node interacts with a system managing procedures and allows creating a new procedure by duplicating an existing template procedure. The "Create From Template" operation is useful when you want to quickly generate a new procedure based on a predefined template, optionally customizing it with additional details such as company association, name, or description.
Practical examples include:
- Automating the creation of standardized procedures for different companies or departments.
- Quickly setting up new workflows that follow a common structure but require specific naming or descriptions.
- Duplicating complex procedures without manually recreating all steps.
Properties
| Name | Meaning |
|---|---|
| Template ID | The ID of the template procedure to duplicate. |
| Additional Fields | Optional fields to customize the new procedure: |
| - Company Name or ID: Select or specify the company this procedure belongs to. | |
| - Name: The new name for the duplicated procedure. | |
| - Description: The new description for the duplicated procedure. | |
| Company Name or ID | (Required) The company this procedure belongs to. Choose from the list or specify an ID using expressions. |
Output
The node outputs JSON data representing the newly created procedure object(s). Each output item corresponds to one input item processed and includes the details of the created procedure, such as its ID, name, description, associated company, and other relevant metadata returned by the API.
No binary data output is indicated in the source code.
Dependencies
- Requires an API key credential for authenticating with the external service's REST API.
- The base URL for the API must be configured in the node credentials.
- The node depends on the external service's API endpoints for procedures and companies.
- Option loaders are used to dynamically fetch lists of companies for selection in properties.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent Template ID will likely cause the API call to fail.
- Omitting the required company field or providing an invalid company ID may result in errors.
- Network or authentication issues with the API key can prevent successful execution.
Error Messages:
- Errors related to unknown resources or operations indicate misconfiguration of resource or operation parameters.
- API errors typically return messages describing missing or invalid parameters; ensure all required fields are correctly set.
- If the node fails but "Continue On Fail" is enabled, error details will be included in the output JSON for each failed item.
Resolution Tips:
- Verify that the Template ID exists and is accessible with the provided API key.
- Confirm the company ID or name is valid and available via the dynamic options.
- Check API key validity and network connectivity.
- Use debug logging (if enabled) to inspect input and output data for troubleshooting.
Links and References
- n8n Expressions Documentation — For using expressions in property values.
- External API documentation for the procedures and templates (not provided here, consult your service provider).