Close CRM icon

Close CRM

Integration with Close CRM
Join our community

Actions2

Overview

This node integrates with the Close CRM API, specifically allowing users to perform HTTP GET requests with query parameters. It is designed to fetch data from Close CRM by sending custom query parameters in the request URL. This can be useful for retrieving filtered lists of records, searching for specific entities, or querying data based on dynamic criteria.

For example, a user might want to retrieve all leads that match certain conditions by specifying those conditions as query parameters. The node then constructs the GET request accordingly and returns the results.

Properties

Name Meaning
Type of Data Selects the type of data to send; currently only "Query" (query parameters) is supported.
Query Parameters Key-value pairs representing the query parameters to include in the GET request URL. Each pair consists of a key (parameter name) and its corresponding value.

Output

The node outputs JSON data containing the response from the Close CRM API for the GET request made with the specified query parameters. The structure of the JSON output depends on the API endpoint queried and typically includes the requested records or data objects.

No binary data output is indicated or expected from this node.

Dependencies

  • Requires an active internet connection to communicate with the Close CRM API at https://api.close.com.
  • An API authentication token or API key credential for Close CRM may be required to authorize requests (configured separately in n8n).
  • The node uses standard HTTP headers for JSON content negotiation (Accept: application/json and Content-Type: application/json).

Troubleshooting

  • Common issues:

    • Missing or invalid API credentials will cause authentication failures.
    • Incorrectly formatted query parameters may result in API errors or empty responses.
    • Network connectivity problems can prevent successful API calls.

  • Error messages:

    • Authentication errors typically indicate missing or invalid API keys; ensure credentials are correctly configured.
    • HTTP 400 or 422 errors suggest malformed query parameters; verify keys and values conform to API expectations.
    • Timeout or network errors require checking internet connectivity and API availability.

Links and References

Discussion