Groner icon

Groner

Integrate with Groner CRM to manage deals, contacts, tasks, and more

Actions11

Deal → Search

AI-generated

Overview

This node operation allows users to search for deals within the Groner CRM system using a variety of filters and criteria. It is useful for retrieving specific deals based on detailed parameters such as deal type, responsible personnel, stage, status, location, financial metrics, dates, and additional custom fields. Practical examples include finding deals in a particular city with a minimum value, or deals assigned to a specific seller within a date range.

Use Case Examples

  1. Search deals filtered by deal type and status to generate sales reports.
  2. Retrieve deals in a specific city with a minimum consumption and power for energy management.
  3. Find deals created within a date range and sorted by value for performance analysis.

Properties

Name Meaning
Filters Collection of filters to narrow down the search by deal type, pre-seller, responsible seller, responsible technician, stage, and status.
Location Filters to narrow down deals by city and state.
Financial Filters related to financial and consumption metrics of deals, including minimum and maximum values for consumption, power, and deal value.
Dates Filters to specify date ranges for deal creation, closing forecast, sale dates, and other relevant dates.
Additional Fields Additional filters for more specific search criteria such as ad set, advertisement, campaign, contact owner ID, qualification scores, lead ID, origin IDs, page size, return only list flag, search criteria, search query, sort by field, status history IDs, store IDs, and tag IDs.

Output

JSON

  • Content
    • list - List of deals matching the search criteria
  • pageSize - Number of deals returned per page
  • query - Search query used
  • criterio - Additional search criteria used
  • tipoProjetoId - Deal type filter applied
  • etapaId - Deal stage filter applied
  • statusId - Deal status filter applied
  • vendedorResponsavelId - Responsible seller filter applied
  • tecnicoResponsavelId - Responsible technician filter applied
  • preVendedorId - Pre-seller filter applied
  • leadId - Lead ID filter applied
  • lojasIds - Store IDs filter applied
  • cidade - City filter applied
  • uf - State filter applied
  • potenciaInicial - Minimum power filter applied
  • potenciaFinal - Maximum power filter applied
  • valorInicial - Minimum deal value filter applied
  • valorFinal - Maximum deal value filter applied
  • consumoInicial - Minimum consumption filter applied
  • consumoFinal - Maximum consumption filter applied
  • etiquetasIds - Tag IDs filter applied
  • origensIds - Origin IDs filter applied
  • statusHistoricoIds - Status history IDs filter applied
  • nStatusHistoricoIds - Negative status history IDs filter applied
  • dataInicial - Start date filter applied
  • dataFinal - End date filter applied
  • dataPrevisaoFechamentoInicial - Initial closing forecast date filter applied
  • dataPrevisaoFechamentoFinal - Final closing forecast date filter applied
  • dataPropostaAceitaInicial - Initial proposal acceptance date filter applied
  • dataPropostaAceitaFinal - Final proposal acceptance date filter applied
  • dataVendaInicial - Initial sale date filter applied
  • dataVendaFinal - Final sale date filter applied
  • dataPerdaInicial - Initial loss date filter applied
  • dataPerdaFinal - Final loss date filter applied
  • ordenarPor - Sort by field applied
  • qualificacaoInicial - Minimum qualification score filter applied
  • qualificacaoFinal - Maximum qualification score filter applied
  • indicador - Performance indicator filter applied
  • donoContatoId - Contact owner ID filter applied
  • campanha - Campaign filter applied
  • anuncio - Advertisement filter applied
  • conjuntoAnuncios - Ad set filter applied

Dependencies

  • Groner API authentication

Troubleshooting

  • Ensure all filter values are correctly formatted and valid according to the Groner API specifications.
  • If the API returns an error, check the authentication credentials and permissions.
  • Large result sets may require pagination using the pageSize parameter to avoid timeouts or incomplete data.
  • If no deals are returned, verify that the search criteria are not too restrictive or conflicting.

Links

Discussion