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 interacts with the Autotask REST API to perform operations on various resources. Specifically, for the 'Project Charge' resource with the 'Count' operation, it counts the number of project charge records that match specified criteria. This is useful for scenarios where you need to quickly determine the number of charges associated with projects, such as generating reports, monitoring billing, or validating data before further processing.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields to map or filter on when performing the count operation on project charges. This allows users to specify criteria or select fields relevant to the count query. |
Output
JSON
count- The total number of project charge records matching the specified criteria.
Dependencies
- Requires an API key credential for authenticating with the Autotask REST API.
Troubleshooting
- If the node throws an error indicating the resource is not supported, verify that the 'resource' parameter is set to 'projectCharge'.
- Errors related to authentication usually mean the API key credential is missing or invalid; ensure correct credentials are configured.
- If the count result is zero unexpectedly, check the 'Fields' mapping to ensure the filter criteria are correctly defined.
- Network or API rate limit errors may occur; verify network connectivity and API usage limits.