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 a CRM system to manage opportunities, specifically allowing users to create new opportunity records linked to leads. It is useful in sales automation workflows where you want to programmatically add potential deals or sales opportunities associated with specific leads, track their status, value, and other relevant details.
Practical examples include:
- Automatically creating an opportunity when a new lead is qualified.
- Adding detailed notes and expected values to opportunities for forecasting.
- Assigning opportunities to specific users or contacts within the CRM.
Properties
| Name | Meaning |
|---|---|
| Lead ID | The unique identifier of the lead this opportunity belongs to. |
| Status | The current status of the opportunity. Options are dynamically loaded from the CRM's opportunity statuses. |
| Note | A textual note providing additional information about the opportunity. |
| Value | The monetary value of the opportunity expressed in cents (e.g., 100000 represents $1,000). |
| Value Formatted | A human-readable string showing the value with currency symbol for display purposes only (e.g., "$1,000"). |
| Additional Fields | A collection of optional fields: |
| - Contact ID | The ID of the primary contact related to this opportunity. |
| - User | The user responsible for managing this opportunity, selectable from a list of users. |
| - Expected Value | The expected monetary value in cents (e.g., 50000 for $500). |
| - Confidence | Confidence percentage (0-100) indicating likelihood of closing the opportunity. |
| - Date Won | The expected close date/time of the opportunity. |
Output
The node outputs JSON data representing the created opportunity record as returned by the CRM API. This typically includes all the fields sent during creation plus any additional metadata assigned by the CRM (such as unique IDs, timestamps, etc.).
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the CRM service.
- The node dynamically loads options such as opportunity statuses and users via API calls to the CRM.
- Proper configuration of the API credentials and network access to the CRM endpoint is necessary.
Troubleshooting
Common issues:
- Missing or invalid Lead ID will cause the creation to fail.
- Providing an invalid status ID that does not exist in the CRM will result in errors.
- Network or authentication failures can prevent successful API calls.
Error messages:
"The resource "opportunity" is not known!"— indicates a misconfiguration or unsupported resource selection.- API errors returned from the CRM (e.g., unauthorized, bad request) will be surfaced as node execution errors.
Resolutions:
- Ensure all required fields (Lead ID, Status) are correctly set.
- Verify API credentials and permissions.
- Confirm that referenced IDs (status, user, contact) exist in the CRM.
- Use the "Continue On Fail" option to handle individual item errors gracefully in batch operations.
Links and References
- Close.com API Documentation (for understanding opportunity fields and statuses)
- n8n documentation on Creating Custom Nodes