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
Configuration Item → Move Configuration Item
AI-generatedOverview
This node operation moves a configuration item from a source company to a destination company within the Autotask PSA system. It supports copying user-defined fields, attachments, notes, and note attachments from the source to the destination configuration item. The operation can optionally deactivate the source configuration item after a successful move and add audit notes to both the source and destination items for traceability. It also supports dry run mode to generate a migration plan without making changes, and includes options for handling masked user-defined fields, attachment size limits, retry strategies for transient failures, and impersonation of resources for audit attribution.
Use Case Examples
- Moving a configuration item from one company to another while copying all related data such as attachments and notes, and deactivating the original item after the move.
- Performing a dry run to generate a migration plan for moving configuration items without actually creating or updating records.
- Moving a configuration item and adding custom audit notes to both the source and destination items for compliance and tracking purposes.
Properties
| Name | Meaning |
|---|---|
| Source Configuration Item ID | The ID of the source configuration item to be moved. |
| Destination Company ID | The ID of the destination company where the configuration item will be moved. |
| Destination Company Location ID | Optional ID of the destination company location; leaving blank clears the location. |
| Destination Contact ID | Optional ID of the destination contact; leaving blank clears the contact linkage. |
| Copy UDFs | Whether to copy user-defined fields from the source to the destination configuration item. |
| Copy Attachments | Whether to copy attachments from the source configuration item. |
| Copy Notes | Whether to copy all notes from the source configuration item. |
| Copy Note Attachments | Whether to copy attachments on the copied notes. |
| Deactivate Source | Whether to deactivate the source configuration item after successful move. |
| Source Audit Note | Audit note text to leave on the source configuration item, supporting placeholders for dynamic data. |
| Destination Audit Note | Audit note text to leave on the destination configuration item, supporting placeholders for dynamic data. |
| Dry Run | Whether to perform a dry run that returns a migration plan without creating or updating records. |
| Idempotency Key | Optional key for idempotency to include in audit notes and output for traceability. |
| Impersonation Resource ID | Optional resource ID to impersonate for audit attribution; if blank, uses the credential user. |
| Proceed Without Impersonation If Denied | Whether to proceed without impersonation if permission is denied when impersonation is set. |
| Masked UDF Policy | Policy for handling masked user-defined field values in source data. |
| Attachment Oversize Policy | Policy for handling attachments that exceed the configured single-file size limit. |
| Partial Failure Strategy | Strategy for handling partial failures after destination configuration item creation. |
| Max Retries | Maximum number of retries for transient attachment copy failures. |
| Retry Base Delay Milliseconds | Base delay in milliseconds for retry backoff. |
| Retry Jitter | Whether to apply jitter to retry delays to avoid retry storms. |
| Max Bytes Per 5 Minutes | Rolling upload throughput limit in bytes per five minutes to throttle uploads. |
| Max Single File Bytes | Maximum allowed size in bytes for a single attachment file. |
Output
JSON
newConfigurationItemId- ID of the newly created configuration item at the destination.newConfigurationItemLink- URL link to the newly created configuration item.migrationPlan- Details of the migration plan when dry run mode is enabled.auditNotes- Audit notes added to source and destination configuration items for traceability.errors- Any errors encountered during the move operation.
Dependencies
- An API key credential for Autotask PSA REST API
Troubleshooting
- Ensure the source and destination configuration item IDs are valid and accessible with the provided credentials.
- Check permissions for impersonation if using the impersonation resource ID option; fallback behavior depends on the 'Proceed Without Impersonation If Denied' setting.
- Attachment size limits and upload throughput limits may cause failures; adjust 'Max Single File Bytes' and 'Max Bytes Per 5 Minutes' accordingly.
- Masked user-defined fields may cause failures depending on the 'Masked UDF Policy' setting; choose to omit or fail as needed.
- Partial failures after destination creation can be handled by deactivating the destination or leaving it active with a note, based on the 'Partial Failure Strategy' setting.
Links
- Autotask n8n Node GitHub Repository - Source code and documentation for the Autotask n8n integration.
- Autotask PSA REST API Documentation - Official API documentation for interacting with Autotask PSA.