Actions524
- AI Helper Actions
- Tool Actions
- API Threshold Actions
- Appointment Actions
- Billing Code Actions
- Billing Items Actions
- Change Request Link Actions
- Checklist Library Actions
- Checklist Library Item Actions
- Classification Icon Actions
- Company Actions
- Company Alert Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Company Site Configuration Actions
- Configuration Item Actions
- Configuration Item Billing Product Association 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
- Contact Actions
- Contact Webhook Actions
- Contact Groups Actions
- Contact Group Contacts Actions
- Contract Actions
- Contract Block Actions
- Contract Block Hour Factor Actions
- Contract Billing Rule Actions
- Contract Charge Actions
- Contract Exclusion Billing Code 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 Rate Actions
- Contract Role Costs Actions
- Contract Retainer Actions
- Contract Service Actions
- Contract Service Adjustment Actions
- Contract Service Bundle Adjustment Actions
- Contract Service Bundle Actions
- Contract Service Bundle Unit Actions
- Contract Ticket Purchase Actions
- Department Actions
- Project Phase Actions
- Quote Item Actions
- Quote Location Actions
- Quote Template Actions
- Resource Actions
- Resource Role Actions
- Resource Role Queue Actions
- Search Filter Actions
- Service Actions
- Service Call Actions
- Subscription Actions
- Subscription Period Actions
- Ticket Category Actions
- Ticket Category Field Default Actions
- Ticket History Actions
- Ticket Note Actions
Billing Code → Count
AI-generatedOverview
This node interacts with Kaseya's Autotask PSA REST API to perform a count operation on Billing Codes. It is useful for scenarios where you need to determine the number of billing codes that meet certain criteria within your Autotask environment, such as for reporting or data validation purposes.
Use Case Examples
- Count the total number of billing codes available in the system.
- Count billing codes filtered by specific fields or conditions to analyze usage or availability.
Properties
| Name | Meaning |
|---|---|
| Fields | Fields to map and use for filtering or counting billing codes, allowing precise control over which billing codes are included in the count. |
Output
JSON
count- The total number of billing codes matching the specified criteria.
Dependencies
- Requires an API key credential for Autotask PSA REST API authentication.
Troubleshooting
- Ensure the API credentials are correctly configured and have sufficient permissions to access billing code data.
- If the count operation returns zero unexpectedly, verify the field mappings and filters are correctly set to include the desired billing codes.
- Common errors may include authentication failures or invalid field mappings; check error messages for guidance and verify API access and parameter correctness.
Links
- Autotask PSA REST API Documentation - Official documentation for the Autotask PSA REST API used by this node.