Actions47
- Booking Actions
- Contact Actions
- Enquiry Actions
- Event Actions
- Location Actions
- Property Actions
- Sale Actions
- User Actions
- Web Lead Actions
Overview
This node integrates with the Inmobalia CRM API to retrieve detailed information about a specific event by its unique identifier. It is useful in scenarios where you need to fetch and process data related to events stored in the CRM, such as event details for reporting, automation workflows, or syncing event data with other systems.
For example, you might use this node to:
- Retrieve an event's full details when triggered by another workflow step.
- Automate notifications or follow-ups based on event information.
- Aggregate event data for analytics or dashboard displays.
Properties
| Name | Meaning |
|---|---|
| Event ID | The unique numeric identifier of the event to retrieve (e.g., 12345). This property is required to specify which event's details to fetch. |
Output
The node outputs a JSON object containing the full details of the requested event as returned by the Inmobalia CRM API. The structure typically includes all relevant event fields such as event name, date, location, participants, and any custom metadata associated with the event.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Inmobalia CRM API using an OAuth2-based API key credential configured within n8n.
- The node depends on the Inmobalia CRM service being accessible and the provided event ID existing in the system.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Event ID will likely result in an error or empty response.
- Network connectivity problems or expired API credentials can cause authentication failures.
- Using unsupported operations or resources will throw errors indicating unsupported operation/resource.
Error messages:
Unsupported operation: getorUnsupported resource: events: Indicates that the selected operation or resource is not implemented or incorrectly specified.- API errors wrapped as
NodeApiErrormay include HTTP status codes and messages from the Inmobalia CRM API, such as "Not Found" if the event ID does not exist.
Resolution tips:
- Verify the Event ID is correct and exists in the CRM.
- Ensure the API credentials are valid and have sufficient permissions.
- Check network connectivity and API endpoint availability.
- Confirm that the node parameters for resource and operation are correctly set to "Event" and "Get" respectively.
Links and References
- Inmobalia CRM API Documentation (example link; replace with actual)
- n8n OAuth2 Credential Setup Guide: https://docs.n8n.io/credentials/oauth2/
- n8n Node Development Documentation: https://docs.n8n.io/integrations/creating-nodes/