Inmobalia CRM icon

Inmobalia CRM

Interact with Inmobalia CRM API
Join our community

Actions47

Overview

The node interacts with the Inmobalia CRM API to perform various operations on different resources. Specifically, for the Contact resource with the Get operation, it retrieves detailed information about a single contact by its unique identifier. This is useful in scenarios where you need to fetch up-to-date contact details from your CRM system to use in workflows such as customer support automation, personalized marketing campaigns, or data synchronization tasks.

For example, you might use this node to:

  • Retrieve a contact's full profile before sending a personalized email.
  • Fetch contact details to update records in another system.
  • Access contact information to trigger conditional workflow branches based on contact attributes.

Properties

Name Meaning
Contact ID The unique numeric identifier of the contact to retrieve (e.g., 12345). This property is required for the Get operation on contacts.

Output

The output of the node is an array containing one item with a json field. This json field holds the detailed data of the requested contact as returned by the Inmobalia CRM API. The structure typically includes all available contact information such as name, email, phone numbers, address, tags, and any custom fields defined in the CRM.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the Inmobalia CRM API.
  • Requires an API authentication token configured via OAuth2 credentials within n8n.
  • The node depends on the internal client library (createClient) to communicate with the API.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Contact ID will likely result in an error or empty response.
    • Missing or expired API authentication token will cause authentication failures.
    • Network connectivity issues can prevent successful API calls.

  • Error messages:

    • Unsupported operation: get — indicates that the operation parameter was not correctly set to "get" for the Contact resource.
    • Unsupported resource: contacts — indicates that the resource parameter was not set to "contacts".
    • API errors wrapped as NodeApiError may include HTTP status codes and messages from the Inmobalia CRM API, such as 404 Not Found if the contact does not exist.

  • Resolutions:

    • Ensure the Contact ID is correct and exists in the CRM.
    • Verify that the OAuth2 credentials are properly configured and valid.
    • Check network connectivity and API endpoint availability.

Links and References

Discussion