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 create a new Contact record. It allows users to define and map specific fields for the Contact resource, enabling automation of contact creation within Autotask. This is useful for workflows that need to add new contacts based on external data or events, such as syncing customer information from other systems or capturing leads.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines and maps the fields to set on the new Contact record when creating it. Users specify which Contact fields to populate and their values. |
Output
JSON
id- The unique identifier of the created Contact record in Autotask.fields- An object containing the data fields of the created Contact as returned by the Autotask API.
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 permissions to create Contact records.
- Verify that all required Contact fields are provided in the mapping; missing mandatory fields may cause API errors.
- Check network connectivity and API endpoint availability if requests fail.
- Error messages from the Autotask API typically indicate invalid field values or permission issues; review the error details to adjust the input accordingly.