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 delete a specific procedure by its unique identifier. It is useful in scenarios where procedures need to be programmatically removed from a system, such as cleaning up outdated or incorrect entries, automating maintenance tasks, or managing workflows that involve dynamic procedure management.
For example, if you have a list of medical or operational procedures stored in an external system, this node can be used to delete a procedure when it is no longer relevant or was created by mistake.
Properties
| Name | Meaning |
|---|---|
| Id | The ID of the procedure to delete. This is a required numeric value that uniquely identifies the procedure to be removed. |
Output
The node outputs JSON data representing the result of the deletion operation. Typically, this will include confirmation of successful deletion or details about any error encountered. The exact structure depends on the external API's response but generally confirms whether the procedure with the specified ID was deleted.
No binary data output is involved.
Dependencies
- Requires an API key credential for authentication with the external service.
- Needs configuration of the base URL for the API endpoint.
- Depends on an external API (likely RESTful) that supports deleting procedures by ID.
Troubleshooting
Common issues:
- Providing an invalid or non-existent procedure ID will likely result in an error response from the API.
- Missing or incorrect API credentials will cause authentication failures.
- Network connectivity problems may prevent the node from reaching the API.
Error messages and resolutions:
- "Procedure not found" — Verify that the provided ID exists in the system.
- "Authentication failed" — Check that the API key or authentication token is correctly configured.
- Timeout or network errors — Ensure stable internet connection and correct API base URL.
Links and References
- Refer to the external API documentation for detailed information on the procedure deletion endpoint.
- Consult n8n documentation on how to configure API credentials and HTTP request nodes for similar integrations.