Actions389
- Contract Actions
- Ticket History Actions
- Ticket Note Webhook Actions
- Ticket Note Actions
- Ticket Webhook Actions
- Time Entry Actions
- Resource Actions
- Role Actions
- Resource Role Actions
- Search Filter Actions
- Service Actions
- Skill Actions
- Service Call Actions
- Survey Results Actions
- Survey Actions
- Ticket Actions
- Opportunity Actions
- Notification History Actions
- Invoice Actions
- Product Actions
- Product Vendor Actions
- Project Actions
- Project Charge Actions
- Project Phase Actions
- Project Task Actions
- Project Note Actions
- Contract Retainer Actions
- Contract Service Actions
- Contract Service Adjustment Actions
- Contract Service Bundle Actions
- Contract Service Bundle Unit Actions
- Contract Service Bundle Adjustment Actions
- Contract Ticket Purchase Actions
- Contract Service Unit Actions
- Domain Registrar Actions
- Holiday Actions
- Holiday Set Actions
- Contract Exclusion Billing Code Actions
- Contract Rate Actions
- Contract Exclusion Role Actions
- Contract Exclusion Sets Actions
- Contract Exclusion Set Excluded Role Actions
- Contract Exclusion Set Excluded Work Type Actions
- Contract Milestone Actions
- Contract Note Actions
- Contract Role Costs Actions
- Contact Groups Actions
- Contact Actions
- Contact Webhook Actions
- Contact Group Contacts Actions
- Contract Block Hour Factor Actions
- Contract Block Actions
- Contract Billing Rule Actions
- Contract Charge Actions
- Configuration Item Category Actions
- Configuration Item Category UDF Association Actions
- Configuration Item DNS Record Actions
- Configuration Item Note Actions
- Configuration Item Related Item Actions
- Configuration Item SSL Subject Alternative Name Actions
- Configuration Item Type Actions
- Configuration Item Webhook Actions
- Company Alert Actions
- Company Actions
- Billing Code Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Configuration Item Actions
- Configuration Item Billing Product Association Actions
Overview
This node updates an existing Opportunity record in the Autotask system using the Autotask REST API. It is useful for automating updates to opportunity data such as status, value, or custom fields within business workflows. For example, it can be used to update the stage of a sales opportunity after a call or to modify opportunity details based on external triggers.
Properties
| Name | Meaning |
|---|---|
| Opportunity ID | The unique identifier of the opportunity record to update. This is required to specify which opportunity to modify. |
| Fields | A resource mapper input that defines which fields of the opportunity to update and their new values. It supports defining fields manually or using auto-mapping features to map input data to opportunity fields. |
Output
JSON
id- The ID of the updated opportunity.fields- The updated fields and their new values as returned by the Autotask API.success- Boolean indicating whether the update operation was successful.error- Error message if the update operation failed.
Dependencies
- Requires an Autotask API credential (API key or token) to authenticate requests to the Autotask REST API.
Troubleshooting
- If the Opportunity ID is invalid or does not exist, the node will fail with an error indicating the record was not found. Verify the ID is correct.
- If required fields are missing or invalid in the fields mapping, the API may reject the update. Ensure all mandatory fields are provided and valid.
- Authentication errors may occur if the API credentials are incorrect or expired. Check and update the Autotask API credentials in the node settings.
- Network or API downtime can cause request failures. Retry after some time or check Autotask service status.