Dendreo icon

Dendreo

Interact with Dendreo API - Optimized for performance
Join our community

Actions65

Overview

This node operation creates a new participant in the Dendreo system. It allows users to either associate the participant with an existing company or create a new company for the participant. The node collects participant details such as last name, first name, email, phone number, and date of birth, and sends this data to the Dendreo API to create the participant record. This operation is useful for managing participant data in training or educational contexts where participants are linked to companies.

Use Case Examples

  1. Creating a participant linked to an existing company by selecting the company from a list and providing participant details.
  2. Creating a participant with a new company by specifying the new company's name along with participant details.

Properties

Name Meaning
Company Selection Choose to select an existing company or create a new one for the participant.
Company The company to associate this participant with, selectable from a list or by ID, shown when selecting an existing company.
New Company Name Name of the new company to create, required when creating a new company for the participant.
Participant Last Name Participant's last name, required.
Participant First Name Participant's first name, required.
Participant Email Participant's email address, optional.
Participant Phone Participant's phone number, optional.
Date of Birth Participant's date of birth, optional.

Output

JSON

  • id_participant - Unique identifier of the created participant.
  • id_entreprise - Identifier of the associated company.
  • nom - Participant's last name.
  • prenom - Participant's first name.
  • email - Participant's email address.
  • telephone - Participant's phone number.
  • date_naissance - Participant's date of birth in ISO format.

Dependencies

  • Dendreo API with authentication credentials

Troubleshooting

  • Ensure the API key credential for Dendreo API is correctly configured to avoid authentication errors.
  • Verify that the company ID or new company name is provided correctly based on the company selection option to prevent errors in participant creation.
  • Check the JSON data format if using the raw JSON input to avoid invalid JSON 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