Actions65
- Actions de Formation Actions
- Catalogue Public (Sessions) Actions
- Centres de Formation Actions
- Contacts Actions
- Entreprises Actions
- Factures Actions
- Formateurs Actions
- Modules/Produits Actions
- Participants Actions
- Sessions Permanentes Actions
- Salles de Formation Actions
Overview
This node interacts with the Dendreo API to manage training actions, specifically supporting the deletion of a training action. It is useful in scenarios where users need to automate the removal of training actions from their Dendreo system, such as cleaning up outdated or canceled training events. For example, a user can delete a specific training action by providing its ID, streamlining administrative workflows.
Use Case Examples
- Deleting a training action by selecting it from a list or specifying its ID to remove it from the system.
- Automating the cleanup of training actions that are no longer relevant or needed.
Properties
| Name | Meaning |
|---|---|
| Training Action | The training action to work with, identified either from a list or by ID. |
| Record ID | The ID of the record, required for operations like get, update, or delete, but hidden for this resource's delete operation. |
Output
JSON
json- The JSON response from the Dendreo API after deleting the training action, typically confirming the deletion or providing related information.
Dependencies
- Requires an API key credential for the Dendreo API, including the user's slug for API endpoint construction.
Troubleshooting
- Common errors include authentication failures (HTTP 401), which indicate invalid or missing API credentials. Users should verify their API key and permissions.
- A 404 error indicates the specified training action or endpoint was not found; users should check the training action ID and resource path.
- A 403 error means permission is denied; users should ensure their API key has the necessary permissions to delete training actions.