PopoOpenPlatform Api

Overview

This n8n node allows you to retrieve the Popo (POPO OpenPlatform) avatar for a specific user by their email address. It is designed for scenarios where you need to programmatically access or display a user's Popo profile picture, such as in automated workflows that sync user data, generate reports, or personalize communications.

Practical examples:

• Displaying employee avatars in dashboards or internal tools.
• Syncing user profile pictures between Popo and other platforms.
• Automating onboarding processes by fetching and storing user avatars.

Properties

Name	Type	Meaning
User Email	String	The email address of the user whose Popo avatar you want to retrieve.

Output

The node returns a JSON object containing the result of the API call to fetch the user's Popo avatar. While the exact structure depends on the Popo OpenPlatform API response, it typically includes fields such as:

{
  "code": 0,
  "msg": "success",
  "data": {
    "email": "user@example.com",
    "headPicUrl": "https://popo.example.com/avatar/abc123.jpg"
  }
}

• code: Status code of the API response.
• msg: Message describing the result.
• data.email: The email address queried.
• data.headPicUrl: URL to the user's Popo avatar image.

No binary output is produced; only JSON data is returned.

Dependencies

• External Service: Requires access to the Popo OpenPlatform API.
• API Credentials: You must configure valid Popo OpenPlatform API credentials in n8n under the name popoOpenPlatformApi.

Troubleshooting

Common issues:

• Invalid or missing email: If the provided email does not exist or is incorrectly formatted, the API may return an error or empty result.
• Authentication errors: If API credentials are missing or invalid, the node will fail with an authentication error.
• Network/API downtime: If the Popo OpenPlatform service is unavailable, requests will fail.

Error messages and resolutions:

• "code": 401 or similar: Check your API credentials configuration in n8n.
• "msg": "user not found": Verify the email address is correct and exists in Popo.
• Network errors: Ensure n8n can reach the Popo OpenPlatform endpoint (check firewall/proxy settings).

Links and References

• Popo OpenPlatform Documentation (if available)
• n8n Documentation: Custom Nodes
• n8n Credentials Setup

---

Note: This summary is based on static analysis of the provided source code and property definitions. For detailed API response formats, refer to the official Popo OpenPlatform documentation.