Overview
This node integrates with the GoHighLevel platform via an MCP server to perform various CRM-related operations. Specifically, for the "Criar Oportunidade" (Create Opportunity) operation, it allows users to create a new sales opportunity linked to a contact within a specified sales pipeline and stage. This is useful in automating lead management workflows, tracking potential deals, and organizing sales processes.
Practical examples include:
- Automatically creating an opportunity when a new lead fills out a form.
- Adding opportunities to specific pipelines and stages based on marketing campaign responses.
- Setting estimated deal values to forecast revenue.
Properties
| Name | Meaning |
|---|---|
| Nome do Contato | The name of the contact associated with the opportunity. |
| Telefone | The phone number of the contact related to the opportunity. |
| Pipeline | The name of the sales pipeline where the opportunity will be created. |
| Estagio | The stage within the pipeline that the opportunity should be assigned to. |
| Valor | The monetary value of the opportunity (deal size or expected revenue). |
Output
The node outputs a JSON array containing the response data from the MCP server after attempting to create the opportunity. Each element corresponds to one input item processed and includes the details returned by the API about the newly created opportunity.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to a GoHighLevel MCP server, configured via an API key credential.
- The node expects the MCP server URL to be provided through credentials.
- Network access to the MCP server endpoint is necessary.
Troubleshooting
Common issues:
- Incorrect or missing pipeline or stage names may cause the API to reject the creation request.
- Invalid or incomplete contact information (name or phone) might result in errors or incomplete opportunity records.
- Network connectivity problems or incorrect MCP server URL can prevent successful requests.
Error messages:
- Errors returned from the MCP server typically indicate invalid parameters or authentication failures.
- If the node returns empty or undefined data, verify that all required fields are correctly filled and that the MCP server is reachable.
Resolutions:
- Double-check the spelling and existence of pipeline and stage names in your GoHighLevel account.
- Ensure the API key credential is valid and has sufficient permissions.
- Test network connectivity to the MCP server URL outside n8n to confirm accessibility.
Links and References
- GoHighLevel Official Website
- GoHighLevel API Documentation (if publicly available)
- n8n Documentation on Creating Custom Nodes