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 integrates with the Autotask REST API to perform operations on Contract Blocks, specifically allowing the creation of new contract blocks within Autotask. It is useful for automating contract management workflows, such as adding new contract blocks based on dynamic data inputs. For example, a user can create a contract block with specific fields mapped from previous workflow steps, enabling seamless contract updates without manual entry.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines the fields and their values to be set when creating or updating a contract block. This property uses a resource mapper to allow users to specify which contract block fields to populate and how to map data into them. |
Output
JSON
id- The unique identifier of the created contract block.fields- An object containing the values of the fields that were set on the created contract block.status- The status or result of the create operation, indicating success or failure.
Dependencies
- Requires an Autotask API credential (API key or token) to authenticate requests to the Autotask REST API.
Troubleshooting
- If the node throws an error about unsupported resource or operation, verify that the resource is set to 'contractBlock' and the operation to 'create'.
- Errors related to field mapping usually indicate missing or invalid field values; ensure that the 'Fields' property is correctly configured with valid contract block fields.
- Authentication errors suggest invalid or missing Autotask API credentials; verify the credentials are correctly set up in n8n.
- Network or API errors may occur if the Autotask API endpoint is unreachable or rate-limited; check network connectivity and API usage limits.