Actions79
- Lead Status Actions
- Pipeline Actions
- Template Actions
- Lead Actions
- Contact Actions
- Activity Actions
- Meeting Search Actions
- Opportunity Actions
- Opportunity Status Actions
- Integration Link Actions
- Smart View Actions
- Comment Actions
- Email Template Actions
- Task Actions
- User Actions
- Custom Field Actions
Overview
This node integrates with the Close.com CRM platform, specifically enabling operations on various CRM resources. For the Opportunity resource with the Get Many operation, it retrieves multiple opportunity records from Close.com based on user-defined filters and limits.
Typical use cases include:
- Fetching a list of sales opportunities to analyze pipeline status.
- Retrieving opportunities created within a specific date range for reporting.
- Filtering opportunities by lead, status, or assigned user to focus on relevant deals.
- Exporting opportunity data for further processing or integration with other systems.
For example, a sales manager might use this node to get all open opportunities worth more than $1000 created in the last month, helping prioritize follow-ups.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching opportunities or limit the number of results. |
| Limit | Maximum number of opportunity records to return (used if "Return All" is false). |
| Filter Options | Collection of optional filters to narrow down the opportunities returned: |
| - Lead ID | Filter opportunities associated with a specific lead ID. |
| - Status ID | Filter opportunities by their status ID (e.g., open, won, lost). |
| - User ID | Filter opportunities assigned to a particular user ID. |
| - Query | JSON-formatted search query for advanced filtering (e.g., {"status": "open", "value__gte": 1000}). |
| - Date From | Only include opportunities created after this date/time. |
| - Date To | Only include opportunities created before this date/time. |
| - Fields | Comma-separated list of specific fields to include in the response, limiting returned data to essentials. |
Output
The node outputs an array of JSON objects representing the retrieved opportunities. Each object contains opportunity details as provided by Close.com, potentially filtered by the requested fields.
If binary data were involved (not applicable here), it would be summarized accordingly, but this operation returns only JSON data.
Dependencies
- Requires an API key credential for authenticating with Close.com.
- The node uses Close.com's REST API endpoints to fetch opportunity data.
- No additional external dependencies beyond standard HTTP requests to Close.com.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Invalid filter parameters (e.g., malformed JSON in the Query field) may result in API errors.
- Requesting too many records without enabling "Return All" can lead to truncated results.
- Date filters must be valid ISO date strings; invalid dates may cause errors.
Error Messages:
"The resource "opportunity" is not known!"— indicates a misconfiguration of the resource parameter.- API errors from Close.com (e.g., 400 Bad Request) usually relate to invalid filters or parameters.
Resolutions:
- Verify API credentials are correctly set up in n8n.
- Validate JSON syntax in the Query filter.
- Use "Return All" cautiously to avoid large data loads.
- Ensure date inputs are properly formatted.