Actions32
- Contatos Actions
- Oportunidades Actions
- Tarefas Actions
- Produtos Actions
- Funis Actions
- Campos Personalizados Actions
- Notas Actions
- Anexos Actions
- Propostas Actions
- Webhooks Actions
Overview
The node integrates with the Linqer CRM API to update an existing sales opportunity ("Oportunidade"). It allows modifying various details of an opportunity such as its title, description, value, related contact, funnel stage, expected close date, associated products, and custom fields.
This node is useful in scenarios where you want to programmatically keep your CRM opportunities up-to-date based on external triggers or workflows. For example, after receiving new information about a deal from a sales team or another system, you can update the opportunity record automatically without manual entry.
Practical examples:
- Updating the expected close date and stage of an opportunity when a sales call outcome is logged.
- Adding or adjusting products linked to an opportunity as the deal evolves.
- Modifying custom fields to reflect additional metadata or internal scoring.
Properties
| Name | Meaning |
|---|---|
| Título | The title or name of the opportunity |
| Descrição | A textual description providing more details about the opportunity |
| Valor | The monetary value associated with the opportunity |
| Contact ID | The unique identifier of the contact related to this opportunity (required) |
| Funnel ID | The unique identifier of the sales funnel this opportunity belongs to (required) |
| Stage ID | The identifier of the current stage within the funnel |
| Data Esperada de Fechamento | Expected closing date/time for the opportunity |
| Channel ID | Identifier of the channel through which the opportunity was generated |
| Source ID | Identifier of the source from which the opportunity originated |
| Produtos | List of products associated with the opportunity; each product includes: |
| - ID do Produto: Unique product ID | |
| - Nome do Produto: Product name | |
| - Quantidade: Quantity of the product | |
| - Preço: Unit price of the product | |
| Campos Customizados | Custom fields for the opportunity; each includes: |
| - ID do Campo: Unique custom field ID | |
| - Valor: Value assigned to the custom field | |
| ID da Oportunidade | Unique identifier of the opportunity to update (required) |
Output
The node outputs the JSON response returned by the Linqer CRM API after updating the opportunity. This typically includes the updated opportunity object with all its properties reflecting the changes made.
The output JSON structure corresponds to the Linqer CRM's opportunity representation, including fields like title, description, value, contactId, funnelId, stageId, expectedCloseDate, channelId, sourceId, products (array), and customFields (object).
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests against the Linqer CRM API.
- The node makes HTTP requests to the Linqer CRM API endpoints under
/v1/opportunities/public. - Proper permissions and valid identifiers (e.g., opportunityId, contactId, funnelId) must be provided to successfully update an opportunity.
Troubleshooting
Common issues:
- Missing required parameters such as
opportunityId,contactId, orfunnelIdwill cause errors. - Providing invalid IDs that do not exist in the CRM will result in API errors.
- Network or authentication failures if the API key is incorrect or expired.
- Missing required parameters such as
Error messages:
"Operação "update" não suportada para oportunidades": Indicates an unsupported operation was requested; ensure the operation parameter is set to "update".- API error responses may include validation errors if required fields are missing or malformed.
Resolutions:
- Verify all required fields are filled correctly.
- Confirm that the API key credential is valid and has necessary access rights.
- Check that referenced IDs correspond to existing records in the CRM.
- Review network connectivity and endpoint URLs.
Links and References
- Linqer CRM API Documentation (general reference for endpoints and data models)
- n8n documentation on creating and using credentials
- n8n workflow examples for CRM integrations
