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 to update an existing Opportunity record. It allows users to modify various fields of an opportunity such as its note, monetary value, status, expected value, confidence percentage, and expected close date.
Typical use cases include:
- Automating updates to sales opportunities based on external triggers or workflows.
- Synchronizing opportunity data from other systems into Close.com.
- Adjusting opportunity details dynamically during a sales process.
For example, you could use this node to update the status of an opportunity when a deal progresses, or to add notes and adjust the expected value after a sales call.
Properties
| Name | Meaning |
|---|---|
| Opportunity ID | The unique identifier of the opportunity to update. |
| Update Fields | A collection of fields to update on the opportunity: |
| - Note | A textual note about the opportunity. |
| - Value | The monetary value of the opportunity in cents (e.g., 100000 for $1,000). |
| - Value Formatted | Human-readable formatted display value with currency symbol (e.g., "$1,000", "€500", "£250"). For display only. |
| - Status | The status of the opportunity. Options are dynamically loaded from available opportunity statuses. |
| - Expected Value | The expected value of the opportunity in cents (e.g., 50000 for $500). |
| - Confidence | Confidence percentage (0-100) indicating likelihood of closing the opportunity. |
| - Date Won | The expected close date of the opportunity. |
Output
The node outputs JSON data representing the updated opportunity object returned by the Close.com API. This typically includes all current fields of the opportunity after the update.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Close.com API.
- The node uses HTTP requests to communicate with Close.com's REST API endpoints.
- Dynamic option loading for fields like "Status" depends on successful API calls to fetch current opportunity statuses.
Troubleshooting
- Invalid Opportunity ID: If the provided Opportunity ID does not exist or is malformed, the API will return an error. Verify the ID is correct and exists in your Close.com account.
- Authentication Errors: Ensure that the API key credential is valid and has sufficient permissions to update opportunities.
- Invalid Field Values: Numeric fields like "Value", "Expected Value", and "Confidence" must be within valid ranges (e.g., confidence between 0 and 100). Incorrect values may cause API errors.
- Network Issues: Connectivity problems can cause request failures. Check network access and API endpoint availability.
- Empty Update Fields: If no fields are specified to update, the node might perform no action or return an error. Always specify at least one field to update.