Actions6
Overview
This node integrates with the CV CRM API to manage leads within a commercial real estate context. Specifically, the Lead - Create operation allows users to create new lead records by providing essential contact information and additional metadata.
Typical use cases include:
- Automatically adding new potential customer contacts collected from web forms or marketing campaigns into the CRM.
- Enriching lead data with details such as broker assignment, project interest, and origin for better sales tracking.
- Streamlining lead management workflows by programmatically creating leads in bulk or triggered by external events.
For example, a real estate agency could use this node to capture leads from their website, including email, phone, and project preferences, and immediately add them to their CRM system for follow-up.
Properties
| Name | Meaning |
|---|---|
| Email address of the lead (e.g., "nome@email.com"). | |
| Phone | Phone number of the lead (e.g., "11999999999"). |
| Additional Fields | A collection of optional fields to provide extra lead details: |
| - Additional Data | Extra data for the lead in JSON format. |
| - Allow Edit | Boolean indicating if the lead can be edited after creation (default: true). |
| - Broker ID | Identifier of the broker responsible for the lead. |
| - Manager ID | Identifier of the manager responsible for the lead. |
| - Name | Full name of the lead. |
| - Origin | Source or origin of the lead (e.g., campaign name). |
| - Project ID | Identifier of the real estate project the lead is interested in. |
| - Real Estate ID | Identifier of the real estate company managing the lead. |
| - Sales Point ID | Identifier of the sales point associated with the lead. |
| - Unit ID | Identifier of the specific unit of interest to the lead. |
Output
The node outputs an array of JSON objects representing the response from the CV CRM API after creating the lead. This typically includes:
- The newly created lead's unique identifier.
- Confirmation of the stored fields such as email, phone, and any additional data provided.
- Status or error messages if the creation failed.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the CV CRM API.
- The node expects the CV CRM API domain to be configured in the credentials.
- Network access to the CV CRM API endpoint is necessary.
Troubleshooting
- Invalid or missing API token: The node will fail if the API authentication token is incorrect or not provided. Ensure the API key credential is correctly set up.
- Malformed additional data JSON: If the "Additional Data" field contains invalid JSON, the API may reject the request. Validate JSON syntax before input.
- Required fields missing: The API may require at least an email or phone number; omitting these might cause errors.
- Network issues: Connectivity problems to the CV CRM API domain will result in request failures.
- API rate limits: Excessive requests may be throttled by the API, causing errors or delays.
Links and References
- CV CRM API Documentation (Replace with actual URL if available)