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
Contact → Count
AI-generatedOverview
This node operation counts the number of Contact records in the Kaseya Autotask PSA system. It is useful for scenarios where you need to quickly determine the total number of contacts, such as generating reports, monitoring contact database size, or validating data synchronization processes.
Use Case Examples
- Count the total number of contacts in the Autotask system to monitor CRM growth.
- Use the count operation to verify the number of contacts before performing bulk updates or exports.
Properties
| Name | Meaning |
|---|---|
| Fields | Fields to map for the count operation, allowing selection and mapping of specific contact fields to include in the count. |
Output
JSON
count- The total number of Contact records matching the criteria.
Dependencies
- Requires an API key credential for Kaseya Autotask PSA REST API authentication.
Troubleshooting
- Ensure the API credentials are correctly configured and have sufficient permissions to access Contact data.
- If the count operation returns zero unexpectedly, verify that any filters or field mappings are correctly set and that contacts exist in the system.
- Common errors include authentication failures and permission denials; check API key validity and user roles in Autotask.
Links
- Kaseya Autotask PSA REST API Documentation - Official API documentation for interacting with Autotask resources including Contacts.