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 information about the authenticated user’s own profile. Specifically, the "Get Own Profile" operation under the "User" resource fetches details related to the user associated with a given account ID.
This node is useful in scenarios where you need to programmatically access user profile data from Unipile, such as integrating user information into workflows, verifying user identity, or synchronizing user data across systems.
Example use cases:
- Automatically fetching the current user's profile details to personalize workflow actions.
- Retrieving user metadata for audit or logging purposes.
- Integrating Unipile user data into CRM or other business tools.
Properties
| Name | Meaning |
|---|---|
| Account ID | The unique identifier of the account whose user profile is to be retrieved. This value is required and sent as a query parameter named account_id in the API request. |
Output
The node outputs JSON data representing the user profile information returned by the Unipile API. This typically includes fields such as user name, email, roles, and other profile-related attributes depending on the API response structure.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Unipile API.
- The base URL for API requests is configured dynamically from the provided credentials.
- Proper configuration of the API authentication token or key is necessary for successful requests.
Troubleshooting
- Missing or invalid Account ID: Since the Account ID is required, omitting it or providing an incorrect value will likely cause the API call to fail. Ensure the Account ID is correctly set.
- Authentication errors: If the API key or authentication token is missing, expired, or invalid, the node will not be able to retrieve user data. Verify that the API credentials are correctly configured.
- API endpoint issues: Network problems or incorrect base URL settings can cause request failures. Confirm that the base URL is correct and accessible.
- Unexpected API responses: If the API changes or returns unexpected data, the node might not handle it properly. Check the API documentation and update the node or workflow accordingly.
Links and References
- Unipile API Documentation (example placeholder link)
- n8n Documentation on Creating Custom Nodes