Actions222
- Application Baseline Actions
- Attack Surface Actions
- Backup Software Actions
- EDR Actions
- Tags Actions
- PII Actions
- External Scan Actions
- Settings Actions
- Compliance Assessment Actions
- Reports Actions
- Compliance Actions
- Jobs Actions
- Active Directory Actions
- Retrieve Ad Roles
- Retrieve Ad User Licenses
- Retrieve Azure Licenses
- Retrieve Azure Ad Logs
- Retrieve Azure Secure Score
- Retrieve Ad Password Policies
- Retrieve Ad Groups View
- Retrieve Ad Ous View
- Retrieve Ad Gpos View
- Retrieve Ad Computers View
- Retrieve Ad Users View
- Retrieve Ad Domain Details
- Retrieve Ad Gpos Details
- Retrieve Get Ous Details
- Retrieve Get Groups Details
- Retrieve Ad Group Users
- Retrieve Ad Group Computers
- Retrieve Get User Details
- Retrieve Get Computer Details
- Retrieve Ad Roles Details
- Retrieve Ad Roles Member
- Retrieve Ad Basic Info
- Audit Log Actions
- Ad Audit Actions
- Asset Data Actions
- Retrieve Bios Info
- Retrieve Bio Info
- Retrieve Browser Extensions
- Retrieve Browser Extension
- Retrieve Ciphers View
- Retrieve Cipher View
- Retrieve Windows Protection Status
- Retrieve Window Protection Status
- Retrieve Asset Compliance Report Card
- Retrieve Asset Firewall Policy
- Retrieve Asset Installed Drivers
- Retrieve Asset Installed Driver
- Retrieve Asset Interface
- Retrieve Asset Msdt
- Retrieve Asset Ports
- Retrieve Asset Port
- Retrieve Asset Security Report Data
- Retrieve Asset Security Report Datum
- Retrieve Asset Shares
- Retrieve Asset Share
- Retrieve Asset Storages
- Retrieve Asset Storage
- Retrieve Asset Unqouted Services
- Retrieve Asset Unqouted Service
- Retrieve Asset User Shares
- Retrieve Asset User Share
- Retrieve Asset Video Info
- Retrieve Asset Windows Reboot Required
- Retrieve Asset Window Reboot Required
- Vulnerabilities Actions
- Firewall Actions
- Integration Actions
- Retrieve Integration Credentials
- Retrieve Integration Credential
- Create Integration Credential
- Update Integration Credential
- Delete Integration Credential
- Retrieve Integration Rules
- Retrieve Integration Rule
- Create Integration Rule
- Update Integration Rule
- Delete Integration Rule
- Retrieve Company Mappings
- Retrieve Company Mapping
- Create Company Mapping
- Update Company Mapping
- Delete Company Mapping
- Event Set Actions
- Ticket Template Actions
- Scheduler Actions
- Credentials Actions
- Asset Actions
- Retrieve Records
- Retrieve Assets
- Retrieve Asset
- Create Asset
- Update Asset
- Delete Asset
- Retrieve Asset Stats
- Retrieve Asset Stat
- Retrieve Asset View
- Retrieve Cron Jobs
- Retrieve Kernel Modules
- Retrieve Suid Permissions
- Retrieve Ufw Firewall Rules
- Retrieve Selinux Settings
- Retrieve Asset Iptables Rules
- Retrieve Asset Users
- Retrieve Asset Processes Running
- Retrieve Asset Services
- Retrieve Asset Patches Info
- Retrieve Asset Firewall Rules
- Retrieve Asset Registry Misconfiguration
- Retrieve Asset Open Ports
- Retrieve Notification Tickets View
- Retrieve System Events View
- Discovery Settings Actions
- Retrieve Discovery Settings
- Retrieve Discovery Setting
- Create Discovery Setting
- Update Discovery Setting
- Delete Discovery Setting
- Retrieve Agent Discoverysettings Mapping
- Retrieve Agent Discoverysetting Mapping
- Create Agent Discoverysetting Mapping
- Update Agent Discoverysetting Mapping
- Delete Agent Discoverysetting Mapping
- Auth Actions
- Company Actions
- Agent Actions
Overview
The "Migrate Agents" operation under the "Agent" resource is designed to facilitate the migration and management of agents between companies within a system. This node allows users to perform actions such as migrating agents from one company to another, restarting agents, or updating agent information. It is particularly useful in scenarios where organizational restructuring occurs, or when agents need to be reassigned or refreshed programmatically.
Practical examples include:
- Migrating a set of agents from an old company account to a new company account after a merger.
- Restarting specific agents remotely to apply updates or resolve issues.
- Updating agent configurations or metadata in bulk.
Properties
| Name | Meaning |
|---|---|
| X USER ID | The user identifier making the request; required for authentication or tracking purposes. |
| Company Id | The numeric ID of the source company from which agents will be migrated or managed. |
| Dest Company Id | The numeric ID of the destination company to which agents will be migrated. |
| Message | The action to perform on the agents. Options: "Migrate Company", "Restart Agent", "Update Agent". |
| Agent Ids | A JSON array containing the IDs of the agents to be affected by the operation. |
Output
The node outputs JSON data representing the result of the requested operation on the agents. This typically includes status information about the migration, restart, or update process, such as success confirmation, error messages, or details about the affected agents.
If binary data were involved (e.g., logs or files), it would be summarized here, but this node appears to focus solely on JSON responses related to agent operations.
Dependencies
- Requires an API key credential for authenticating with the Connect Secure API.
- Depends on the Connect Secure API endpoint that handles agent migration and management.
- The node uses routing to send headers and body parameters correctly formatted for the API.
Troubleshooting
Common Issues:
- Missing or invalid "X USER ID" header can cause authentication failures.
- Incorrect company IDs or agent IDs may lead to errors or no changes applied.
- Providing malformed JSON in the "Agent Ids" property can cause parsing errors.
Error Messages:
- Authentication errors indicating missing or invalid user ID header.
- Validation errors if required fields like company IDs or message type are missing.
- API errors returned from the Connect Secure service, such as "Agent not found" or "Migration failed".
Resolutions:
- Ensure all required properties are provided and correctly formatted.
- Validate JSON input for agent IDs before execution.
- Confirm that the API credentials have sufficient permissions.
Links and References
- Connect Secure API Documentation (Replace with actual URL)
- n8n documentation on HTTP Request Node for understanding routing and headers setup.