Immojump icon

Immojump

Interact with the ImmoJump API

Actions9

Overview

The node interacts with the ImmoJump API to retrieve data related to real estate and associated entities. Specifically, for the Company resource with the Get Many operation, it fetches multiple company records from the API. This operation is useful when you want to list or process a batch of companies managed within the ImmoJump system.

Common scenarios include:

  • Synchronizing company data from ImmoJump into another system.
  • Generating reports or analytics based on multiple companies.
  • Automating workflows that require bulk access to company information.

For example, you might use this node to pull up to 50 companies at once (or all companies if desired) to update your CRM or mailing lists.

Properties

Name Meaning
Return All Whether to return all results or only up to a given limit. Options: true (all results), false (limited results).
Limit Max number of results to return when not returning all. Integer between 1 and 100. Default is 50.

These properties control pagination of the results:

  • If Return All is set to true, the node will paginate through all available companies.
  • If false, it returns only up to the specified Limit number of companies.

Output

The node outputs an array of JSON objects representing company records retrieved from the ImmoJump API. Each item in the output corresponds to one company entity with its associated fields as provided by the API.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the ImmoJump API.
  • The node expects the following credentials configuration:
    • Base URL of the ImmoJump API.
    • Bearer token for authorization.
    • Optional organization ID header for scoped requests.

These must be configured in n8n prior to using the node.

Troubleshooting

  • Missing or invalid credentials: The node requires a valid API token and base URL. Ensure these are correctly set in the credentials.
  • Organization ID missing: Some API calls require an organization ID header. If missing, the request may fail or return incomplete data.
  • API rate limits or pagination issues: When fetching many companies, ensure the pagination parameters are correctly set. Use "Return All" carefully to avoid large data loads.
  • Unexpected API responses: If the API returns unexpected payloads or errors, check network connectivity and API status. The node logs debug information which can help diagnose issues.

Links and References

Discussion