Actions85
- Account Actions
- Calendar Actions
- Email Actions
- LinkedIn Actions
- Close Job Posting
- Create Job Posting
- Download Applicant Resume
- Edit Job Posting
- Endorse Skill
- Get Company Profile
- Get Hiring Project by ID
- Get Hiring Projects
- Get Inmail Balance
- Get Job Applicant
- Get Job Applicants
- Get Job Offer
- Get Job Postings
- Get Raw Data
- Perform Action on Member
- Publish Job Posting
- Search
- Search Parameters
- Solve Job Publishing Checkpoint
- Messaging Actions
- Post Actions
- User Actions
- Webhook Actions
Overview
The node interacts with the Unipile API to retrieve user profile information based on a unique identifier. Specifically, the "Get Profile by Identifier" operation under the "User" resource fetches detailed profile data for a given user within a specified account context. This is useful in scenarios where you need to programmatically access user profiles for CRM enrichment, user management, or integration with other systems that require user details.
Practical examples include:
- Fetching a user's profile to display personalized content.
- Synchronizing user data between Unipile and another platform.
- Triggering workflows based on user profile attributes.
Properties
| Name | Meaning |
|---|---|
| Identifier | The unique identifier of the user whose profile is to be retrieved. |
| Account ID | The identifier of the account under which the user exists; used to scope the profile retrieval request. |
| Additional Fields | Optional parameters to customize the API call: |
| - Linkedin API | Specifies an alternative LinkedIn API endpoint to use instead of the default one when fetching the profile. |
| - Linkedin Sections | Defines specific sections of the LinkedIn profile to synchronize during the API call. |
| - Notify | Boolean flag indicating whether the profile visit should trigger a notification to the profile owner. |
Output
The node outputs JSON data representing the user's profile as returned by the Unipile API. This typically includes user details such as name, contact information, social profiles, and any additional fields requested via the optional parameters.
If the node supports binary data output (not indicated here), it would represent attachments or media related to the user profile, but this operation focuses on JSON profile data only.
Dependencies
- Requires an active connection to the Unipile API, authenticated via an API key credential.
- The base URL for API requests is configured through the node's credentials.
- Proper permissions on the Unipile account to access user profile data are necessary.
Troubleshooting
- Missing or invalid Identifier/Account ID: Ensure both required fields are provided and correctly formatted; otherwise, the API will reject the request.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- API rate limits or connectivity issues: Network problems or exceeding API quotas can cause failures; check network status and API usage.
- Invalid additional fields: Providing unsupported values for LinkedIn API or sections may result in partial or failed responses.
Links and References
- Unipile API Documentation (hypothetical link)
- n8n documentation on Creating Custom Nodes