Groner icon

Groner

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

Actions11

Deal → Create

AI-generated

Overview

This node operation creates a new deal (lead) in the Groner CRM system. It is useful for automating the process of adding new sales leads or deals into the CRM from external workflows or applications. For example, when a new lead is captured from a web form or marketing campaign, this node can automatically create the corresponding deal record in Groner CRM with detailed information.

Use Case Examples

  1. Automatically create a new deal in Groner CRM when a lead form is submitted on a website.
  2. Add new sales leads from an email marketing campaign into Groner CRM for follow-up by the sales team.

Properties

Name Meaning
Name Lead/deal name, used to identify the deal.
Email Address Lead email address, used for contact purposes.
Phone Lead phone number, used for contact purposes.
Origin Name or ID Lead origin, specifying where the lead came from. Can be selected from a list or specified by ID.
Additional Fields Optional additional details about the deal such as estimated value, campaign info, location, responsible person, notes, business segment, and more.

Output

JSON

  • nome - Name of the created deal.
  • email - Email address of the lead.
  • telefone - Phone number of the lead.
  • cidade - City of the lead.
  • documento - CPF or CNPJ number.
  • tipoPessoa - Type of person (individual or company).
  • uf - State (UF).
  • valorConta - Estimated deal value.
  • responsavelId - ID of the responsible person.
  • emailResponsavel - Email of the responsible person.
  • nota - Additional notes or observations.
  • url - Website URL.
  • campanha - Campaign name.
  • anuncio - Advertisement origin.
  • conjuntoAnuncios - Ad set for the campaign.
  • codigoLeadTracking - Tracking code for the lead.
  • nomeFantasia - Trade name of the company.
  • segmento - Business segment.
  • tipoProjetoId - Deal type ID.

Dependencies

  • An API key credential for Groner CRM (referred to as 'gronerApi')

Troubleshooting

  • Ensure the 'gronerApi' credential is correctly configured with the tenant information and API key to authenticate requests.
  • Verify that all required fields (Name, Email Address, Phone, Origin Name or ID) are provided and correctly formatted.
  • If the node fails, check the HTTP response for error messages related to invalid parameters or authentication issues.
  • Use the 'continueOnFail' option to handle errors gracefully in workflows and inspect error messages for troubleshooting.

Links

Discussion