Actions28
- Profiles Actions
- Companies Actions
- Jobs Actions
- Messages Actions
Profiles → Get Profile by IDs
AI-generatedOverview
This node integrates with the Xing API to perform various operations related to user profiles, companies, jobs, and messages on the Xing platform. Specifically, for the "Profiles" resource and the "Get Profile by IDs" operation, it retrieves detailed profile information for one or more users based on their user IDs.
This functionality is useful when you need to fetch multiple user profiles in bulk by specifying their IDs, such as for data enrichment, analytics, or synchronization tasks involving Xing user data.
Example use case:
You have a list of Xing user IDs from an external source and want to retrieve their profile details to update your CRM or generate reports.
Properties
| Name | Meaning |
|---|---|
| User ID | One or more Xing user IDs separated by commas (e.g., 12345,67890). The node will fetch profiles for all specified IDs. |
Output
The node outputs JSON data containing the profile information for the requested user IDs. The structure corresponds to the Xing API's response for multiple profiles, typically including fields such as user names, job titles, locations, and other profile details.
If multiple IDs are provided, the output will include an array or collection of profile objects matching those IDs.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential and OAuth2 authentication configured for accessing the Xing API.
- The node depends on the external Xing API service at
https://api.xing.com. - Proper permissions/scopes must be granted to the API credentials to access profile data.
Troubleshooting
Common issues:
- Invalid or missing user IDs can cause errors or empty results.
- Insufficient API permissions may result in authorization errors.
- Network or API rate limiting issues could cause request failures.
Error messages:
"Unknown operation: getProfileByIds"— indicates a misconfiguration of the operation parameter; ensure the correct operation name is selected.- API errors returned from Xing (e.g., 401 Unauthorized, 404 Not Found) should be checked against the API credentials and user ID validity.
Resolution tips:
- Verify that the user IDs are correctly formatted and exist on Xing.
- Confirm that the API credentials have the necessary scopes.
- Enable "Continue On Fail" in the node settings to handle individual item errors gracefully.
Links and References
- Xing API Documentation (general reference for available endpoints and data structures)
- n8n documentation on creating custom nodes for further customization guidance