Actions32
- Contatos Actions
- Oportunidades Actions
- Tarefas Actions
- Produtos Actions
- Funis Actions
- Campos Personalizados Actions
- Notas Actions
- Anexos Actions
- Propostas Actions
- Webhooks Actions
Overview
This node integrates with the Linqer CRM API to manage products within the CRM system. Specifically, the "Buscar por ID" (Get by ID) operation under the "Produtos" (Products) resource retrieves detailed information about a single product using its unique identifier.
Common scenarios for this node include:
- Fetching product details to display or use in workflows.
- Synchronizing product data between Linqer CRM and other systems.
- Automating inventory checks or updates based on product information.
For example, you might use this node to get the price, stock level, and description of a product by providing its ID, then use that data to update an e-commerce platform or trigger alerts if stock is low.
Properties
| Name | Meaning |
|---|---|
| ID do Produto | The unique identifier of the product to retrieve. This is a required string input. |
Output
The node outputs JSON data representing the product details retrieved from Linqer CRM. The structure typically includes fields such as:
name: Product name.description: Description of the product.price: Price of the product.sku: Stock keeping unit identifier.category: Product category.stock: Available stock quantity.active: Whether the product is active.lastModifiedBy: Identifier of the user who last modified the product.
The output is a JSON object containing these fields and possibly others as returned by the Linqer CRM API.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Linqer CRM API.
- The node uses HTTP requests to the Linqer CRM REST endpoints.
- Proper configuration of the API URL and authentication credentials in n8n is necessary.
Troubleshooting
- Invalid or missing product ID: Ensure the "ID do Produto" property is correctly set and corresponds to an existing product in Linqer CRM.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network or API errors: Check connectivity to the Linqer CRM API endpoint and confirm the service is operational.
- Unsupported operation error: If the operation or resource is incorrectly specified, the node will throw an error indicating unsupported operations.
Links and References
- Linqer CRM API documentation (refer to the official API docs for detailed endpoint info).
- n8n documentation on creating and configuring API credentials.
- General REST API usage guides for understanding request/response patterns.