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 retrieve detailed information about a specific contact by its ID. It is useful in scenarios where you need to fetch contact details for further processing, such as updating records, sending personalized communications, or integrating contact data into other workflows. For example, you can use this node to get a contact's full profile before updating their information or to pull contact details for reporting purposes.
Use Case Examples
- Retrieve a contact's full details by selecting the contact from a list or by providing the contact ID.
- Use the contact information to update related records in a CRM system.
- Fetch contact data to personalize email campaigns or notifications.
Properties
| Name | Meaning |
|---|---|
| Contact | The contact to work with, selected either from a list or by specifying the contact ID. This is a required property for the 'Get a Contact' operation. |
Output
JSON
id_contact- Unique identifier of the contact.nom- Last name of the contact.prenom- First name of the contact.email- Email address of the contact.civilite- Title or civility of the contact (e.g., Mr., Mrs., Ms.).telephone_direct- Direct phone number of the contact.additionalProperties- Any additional properties returned by the API for the contact.
Dependencies
- Dendreo API with an API key credential
Troubleshooting
- Ensure the contact ID is a valid number when using the 'By ID' mode; otherwise, the node will throw a validation error.
- Authentication errors (HTTP 401) indicate issues with the API key or permissions; verify the API credentials configured in the node.
- A 404 error means the contact was not found or the endpoint does not exist; check the contact ID and resource name.
- Permission denied errors (HTTP 403) suggest insufficient permissions for the API key; review the API key's access rights.
Links
- Dendreo API Documentation - Official API documentation for Dendreo, providing details on endpoints and data structures.