Actions47
- Booking Actions
- Contact Actions
- Enquiry Actions
- Event Actions
- Location Actions
- Property Actions
- Sale Actions
- User Actions
- Web Lead Actions
Overview
The node interacts with the Inmobalia CRM API to retrieve data related to web leads. Specifically, the "Get" operation for the "Web Lead" resource fetches detailed information about a single web lead by its unique identifier. This is useful in scenarios where you want to obtain specific details about a potential customer or inquiry captured through web forms or other lead generation channels integrated into the CRM.
Practical examples include:
- Fetching a web lead's contact and inquiry details to trigger personalized follow-up workflows.
- Integrating lead data into marketing automation or sales pipelines.
- Validating or enriching lead information before further processing.
Properties
| Name | Meaning |
|---|---|
| Web Lead ID | The unique numeric identifier of the web lead to retrieve (e.g., 12345). This property is required for the "Get" operation on the "Web Lead" resource. |
Output
The output is a JSON object representing the detailed data of the requested web lead. This typically includes all available fields and metadata associated with that web lead in the Inmobalia CRM system, such as contact information, lead source, status, timestamps, and any custom fields defined in the CRM.
The node does not output binary data for this operation.
Example output structure (simplified):
{
"id": 12345,
"name": "John Doe",
"email": "john.doe@example.com",
"phone": "+1234567890",
"source": "Website Form",
"status": "New",
"createdAt": "2024-01-01T12:00:00Z",
"customFields": {
"interestedProperty": "Apartment Downtown",
"budget": 250000
}
}
(Note: Actual fields depend on the CRM configuration and API response.)
Dependencies
- Requires an active connection to the Inmobalia CRM API.
- Requires an API authentication token configured via OAuth2 credentials in n8n.
- No additional external dependencies are needed beyond the configured credential.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Web Lead ID will likely result in an error or empty response.
- Missing or expired API authentication token can cause authorization errors.
- Network connectivity issues may prevent successful API calls.
Error messages:
Unsupported operation: get— indicates the operation name might be misspelled or unsupported for the selected resource.Unsupported resource: webLeads— indicates the resource name might be incorrect or not supported.- API errors returned from the CRM (e.g., 404 Not Found if the Web Lead ID does not exist).
Resolutions:
- Verify the Web Lead ID is correct and exists in the CRM.
- Ensure the API credentials are valid and have necessary permissions.
- Check network connectivity and retry.
- Confirm the resource and operation names match exactly as expected.
Links and References
- Inmobalia CRM API Documentation (example placeholder link)
- n8n OAuth2 Credential Setup Guide
- n8n Node Development Documentation