Lola CIPInstall

Overview

The "Lola CIP" node is designed to interact with a user profile system, specifically for managing and retrieving CIP (Customer Information Profile) tokens. It supports two main operations: claiming (creating or updating) a profile token and retrieving an existing profile token. This node is useful in workflows where you need to manage user identities or synchronize user data across platforms such as Telegram, WhatsApp, etc.

Practical examples:

• Automatically create or update a user's profile when they sign up or interact with your service.
• Retrieve a user's profile information for personalization or verification purposes during workflow execution.

Properties

Name	Meaning
Profile ID	User Profile ID, must be unique and should be taken from Lola Profile V2. Required for all operations.
Token Operation	The action to perform: - Get: Get a profile - Claim: Set a profile (create if not exists, update if exists)
CIP Token ID	Current CIP Token ID. Only required when the operation is "Claim".
Platform ID	Current platform identifier (e.g., telegram, whatsapp, etc). Only required when the operation is "Claim".

Output

• The output will always include a field lola_cip inside the json property of the item.
• The structure of lola_cip depends on the response from the underlying claim or get operation, but it will typically contain at least a status field (such as "success").
• If the operation is successful (status == "success"), the item is sent to the first output ("success"). Otherwise, it is sent to the second output ("error").

Example output:

{
  "json": {
    "lola_cip": {
      "status": "success",
      // ...other fields depending on the API response
    }
  }
}

Dependencies

• May require credentials named lolaKeyApi (not strictly required according to the node definition, but may be needed depending on the environment).
• Relies on external functions claimCIPToken and getCIPToken (from bundled dependencies), which likely interact with an external Lola Profile API.

Troubleshooting

• Missing or invalid Profile ID: Since "Profile ID" is required, omitting it will result in an error.
• API errors: If the underlying Lola Profile API returns an error (e.g., network issues, invalid token/platform ID), the node will throw an error and route the item to the "error" output.
• Credential issues: If the API requires authentication and credentials are missing or incorrect, you may encounter authentication errors.

Common error messages:

• Errors thrown by the node will be wrapped as n8n NodeOperationError, often containing the original error message from the API or function call.

Links and References

• n8n Documentation: Custom Nodes
• (If available) Documentation for Lola Profile V2 and its API endpoints.