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 manage "Oportunidades" (Opportunities). Specifically, the "Buscar Todas" (Get All) operation retrieves all opportunities associated with the authenticated account. This is useful for scenarios where you want to list or process all sales opportunities in your CRM system, such as generating reports, syncing data with other tools, or triggering workflows based on opportunity data.
For example, a sales manager could use this node to fetch all current opportunities to analyze pipeline health or to automate follow-up tasks based on opportunity stages.
Properties
| Name | Meaning |
|---|---|
| Account ID | The identifier of the account whose opportunities are to be retrieved. This is a required string input. |
Output
The output is a JSON array where each item represents an opportunity object fetched from the Linqer CRM API. Each opportunity object typically includes fields such as title, description, value, contactId, funnelId, stageId, expectedCloseDate, channelId, sourceId, products, and customFields, among others.
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 endpoints, so network connectivity to the API URL configured in the credentials is necessary.
- No additional environment variables or external services are explicitly required beyond the API authentication.
Troubleshooting
Common Issues:
- Missing or invalid Account ID parameter will cause the request to fail.
- Invalid or expired API credentials will result in authentication errors.
- Network issues or incorrect API URL configuration can cause request failures.
Error Messages:
"Operation "getAll" not supported for opportunities": This would indicate an internal mismatch or misconfiguration; ensure the operation name is correctly set to "getAll".- Authentication errors usually manifest as HTTP 401 or 403 responses; verify that the API key credential is valid and has appropriate permissions.
- If the API returns unexpected data or empty arrays, confirm that the account ID is correct and that there are existing opportunities in the CRM.
Links and References
- Linqer CRM API Documentation (general reference): https://docs.linqercrm.com/api (Note: link is illustrative, replace with actual if available)