Actions100
- Activity Logs Actions
- Articles Actions
- Asset Layouts Actions
- Asset Passwords Actions
- Assets Actions
- Get Assets
- Get Companies Company Id Assets
- Post Companies Company Id Assets
- Get Companies Company Id Assets Id
- Put Companies Company Id Assets Id
- Delete Companies Company Id Assets Id
- Put Companies Company Id Assets Id Archive
- Put Companies Company Id Assets Id Unarchive
- Put Companies Company Id Assets Id Move Layout
- Cards Actions
- Companies Actions
- Expirations Actions
- Exports Actions
- Folders Actions
- IP Addresses Actions
- Lists Actions
- Magic Dash Actions
- Matchers Actions
- Networks Actions
- Password Folders Actions
- Procedure Tasks Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
Overview
This node allows users to create a new procedure in the target system. It is useful for automating the addition of procedural templates or workflows, especially when managing multiple procedures programmatically. For example, a user can automate the creation of standardized procedures with specific names and optional metadata such as descriptions or company associations.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the procedure to be created. This is a required string input. |
| Additional Body Fields | Optional additional fields to include in the procedure creation request: |
| - Description | A textual description of the procedure. |
| - Company Id | Numeric ID of the company to which this procedure should be transferred. Set to null to make it global. |
| - Company Template | Boolean flag; when true, sets both template and remove_completion_ability to true, otherwise false. |
Output
The node outputs JSON data representing the newly created procedure object as returned by the API. This typically includes the procedure's unique identifier, name, description, company association, and other metadata fields. There is no binary output.
Dependencies
- Requires an API key credential for authentication with the target service.
- The base URL for the API must be configured in the node credentials.
- The node uses JSON content type and expects the API to accept POST requests to create procedures.
Troubleshooting
- Missing Required Fields: If the "Name" property is not provided, the node will likely throw an error indicating a missing required field.
- Authentication Errors: Ensure that the API key credential is valid and has permissions to create procedures.
- Invalid Company Id: Providing an invalid or non-existent company ID may cause the API to reject the request.
- Boolean Field Misuse: The "Company Template" boolean affects two internal flags; setting it incorrectly might lead to unexpected behavior in the created procedure.
- API Endpoint Issues: Verify that the base URL and endpoint paths are correctly configured in the credentials.
Links and References
- No direct external links were found in the source code. Users should refer to their target system's API documentation for detailed information on procedure creation endpoints and field specifications.