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 creating a Company Note in the Autotask system via its REST API. It is useful for users who want to programmatically add notes to company records within Autotask, such as logging communications, updates, or important information related to a company. For example, a support team could automate adding notes about customer interactions or status updates directly into the company profile.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines the specific fields and their values to map when creating the Company Note. This allows users to specify which data attributes of the note to set, such as the note content, associated company ID, or other relevant fields. |
Output
JSON
id- The unique identifier of the created Company Note in Autotask.content- The textual content or body of the created Company Note.companyID- The identifier of the company to which the note is attached.createdDate- Timestamp indicating when the Company Note was created.
Dependencies
- Requires an Autotask API credential for authentication to access the Autotask REST API.
Troubleshooting
- Ensure the Autotask API credentials are correctly configured and have sufficient permissions to create company notes.
- Verify that all required fields in the 'Fields' mapping are provided; missing mandatory fields may cause API errors.
- Check for network connectivity issues that might prevent communication with the Autotask API endpoint.
- If the API returns errors about invalid data, review the field mappings to ensure data types and values conform to Autotask's API requirements.
Links
- Autotask Company Notes API Documentation - Official Autotask documentation describing the Company Notes resource and its API usage.