Actions79
- Lead Actions
- Lead Status Actions
- Contact Actions
- Activity Actions
- Meeting Search Actions
- Opportunity Actions
- Opportunity Status Actions
- Integration Link Actions
- Smart View Actions
- Comment Actions
- Pipeline Actions
- Email Template Actions
- Task Actions
- User Actions
- Template Actions
- Custom Field Actions
Opportunity → Get
AI-generatedOverview
This node integrates with the Close.com CRM platform, specifically allowing operations on various CRM resources. For the Opportunity resource with the Get operation, it retrieves detailed information about a specific sales opportunity by its ID. This is useful for workflows that need to fetch up-to-date data on an opportunity to make decisions, update records, or trigger other actions based on opportunity details.
Practical examples:
- Fetching opportunity details to display in a dashboard.
- Retrieving opportunity data before updating related records.
- Using opportunity fields to trigger conditional logic in automation.
Properties
| Name | Meaning |
|---|---|
| Opportunity ID | The unique identifier of the opportunity to retrieve. Required for the Get operation. |
| Additional Fields | Optional collection to specify extra parameters: |
| - Fields | Comma-separated list of specific fields to include in the response (e.g., "name,status"). |
Output
The node outputs JSON data representing the requested opportunity's details as returned by the Close.com API. The structure includes all standard and optionally requested fields of the opportunity record.
- The output JSON contains key-value pairs corresponding to the opportunity's properties such as ID, name, status, value, close date, and any custom fields if requested.
- No binary data output is produced by this operation.
Dependencies
- Requires an active connection to Close.com CRM via an API key credential configured in n8n.
- The node uses Close.com's REST API endpoints to perform operations.
- Proper API permissions are needed to read opportunity data.
Troubleshooting
Common issues:
- Invalid or missing Opportunity ID will cause errors.
- Insufficient API permissions may result in authorization errors.
- Network connectivity problems can cause request failures.
Error messages:
"The resource "opportunity" is not known!"— indicates a misconfiguration or unsupported resource selection.- API errors from Close.com (e.g., 404 Not Found) typically mean the opportunity ID does not exist.
Resolutions:
- Verify the Opportunity ID is correct and exists in Close.com.
- Ensure the API key credential has read access to opportunities.
- Check network connectivity and API endpoint availability.
Links and References
- Close.com API Documentation
- n8n Documentation on HTTP Request Nodes (for understanding API calls)
- Close.com CRM Official Site