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 enables users to create new Contract Role Costs records in the Autotask system via its REST API. It is useful for automating the addition of cost-related data associated with contract roles, which can help in managing contract financials and resource allocation. For example, a user can map fields from incoming data to create a new contract role cost entry, facilitating integration with other systems or workflows that manage contracts and billing.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines the mapping of input data fields to the Contract Role Costs resource fields for creating or updating records. This property supports defining the fields manually or using auto-mapping features to streamline data input. |
Output
JSON
id- The unique identifier of the created Contract Role Cost record.fields- The data fields of the created Contract Role Cost record as returned by the Autotask API.
Dependencies
- Requires an Autotask API credential (API key or token) to authenticate requests to the Autotask REST API.
Troubleshooting
- Ensure that the API credentials are correctly configured and have sufficient permissions to create Contract Role Costs.
- Verify that all required fields are mapped and provided in the 'Fields' property; missing mandatory fields may cause API errors.
- Check for network connectivity issues or API rate limits that might prevent successful requests.
- Error messages from the API typically indicate missing or invalid fields; review the error details to adjust the field mappings accordingly.