Dendreo icon

Dendreo

Interact with Dendreo API - Optimized for performance
Join our community

Actions65

Overview

This node interacts with the Dendreo API to create a new permanent session (Sessions Permanentes). It allows users to specify details such as the associated module, training room, session name, start date, and end date. This operation is useful for managing and scheduling ongoing training sessions within the Dendreo platform, enabling automation of session creation in workflows.

Use Case Examples

  1. Creating a new permanent training session by specifying the module, training room, session name, and session dates.
  2. Automating the scheduling of recurring training sessions in a training management system integrated with Dendreo.

Properties

Name Meaning
Data (JSON) JSON data for the record, used to provide custom or additional session details in JSON format.
Module The module associated with the permanent session, selected from a list of available modules.
Training Room The training room where the session will take place, selected from a list of available training rooms.
Session Name The name of the permanent session.
Start Date The start date and time of the session.
End Date The end date and time of the session.

Output

JSON

  • json
    • id_module - ID of the module associated with the session
    • id_salle_de_formation - ID of the training room for the session
    • nom - Name of the permanent session
    • date_debut - Start date of the session in ISO format
    • date_fin - End date of the session in ISO format

Dependencies

  • Dendreo API with authentication via an API key credential

Troubleshooting

  • Ensure the API key credential is correctly configured and has the necessary permissions to create permanent sessions.
  • Verify that the module and training room IDs provided are valid and exist in the Dendreo system.
  • Check the JSON data format if using the 'Data (JSON)' property to avoid parsing errors.
  • Common error messages include authentication failures (401), resource not found (404), and permission denied (403). These should be resolved by verifying credentials, resource IDs, and user permissions respectively.

Discussion