Receber por email
← Voltar para o catálogo

Autotask Configuration Items

Use this skill when working with Autotask Configuration Items (CIs) - asset management, inventory tracking, warranty monitoring, lifecycle management, and relationship mapping. Covers CI types, categories, DNS records, SSL certificates, related items, notes, and contract billing associations. Essential for MSP asset documentation and infrastructure tracking.

31estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: Apache-2.0

Como adicionar

/plugin marketplace add wyre-technology/msp-claude-plugins

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/autotask-configuration-items/svg)](https://www.skillteca.com.br/skills/autotask-configuration-items)

Skills relacionadas

Ver todas de DevOps e Infra →

Alerta por categoria

Receba novas skills de DevOps e Infra toda segunda

1 email curto, só com as skills novas de DevOps e Infra. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Autotask Configuration Items Management

Overview

Configuration Items (CIs) are the backbone of MSP asset management in Autotask. CIs represent any trackable asset—servers, workstations, network devices, software licenses, domains, and more. Proper CI management enables warranty tracking, lifecycle planning, ticket context, and contract-based billing.

CI Status Codes

| Status ID | Name | Description | Business Logic | |-----------|------|-------------|----------------| | 1 | Active | Currently in use | Standard operational state | | 2 | Inactive | Not currently in use | May be spare/storage | | 3 | Retired | End of life | Historical record only | | 4 | Missing | Cannot be located | Requires investigation | | 5 | On Order | Procurement in progress | Expected arrival tracking |

CI Lifecycle Workflow

On Order (5) ────> Active (1) ────> Inactive (2) ────> Retired (3)
                      │                    ↑
                      └────────────────────┘
                      (temporary deactivation)

      Active (1) ────> Missing (4) ────> (investigation)
                            │
                            ├──> Active (1)    (found)
                            └──> Retired (3)   (write-off)

Configuration Item Field Reference

Core Identification Fields

| Field | Type | Required | Description | |-------|------|----------|-------------| | id | int | System | Auto-generated unique identifier | | referenceTitle | string(100) | Yes | Primary name/identifier | | referenceNumber | string(50) | No | Serial number or reference | | companyID | int | Yes | Owner company | | companyLocationID | int | No | Location within company | | configurationItemType | int | Yes | Type classification | | configurationItemCategoryID | int | No | Category classification |

Hardware Specification Fields

| Field | Type | Required | Description | |-------|------|----------|-------------| | productID | int | No | Link to Autotask product | | serialNumber | string(100) | No | Manufacturer serial number | | make | string(50) | No | Manufacturer | | model | string(100) | No | Model name/number |

Network Fields

| Field | Type | Required | Description | |-------|------|----------|-------------| | ipAddress | string(50) | No | Primary IP address | | macAddress | string(50) | No | MAC address | | hostname | string(100) | No | Network hostname |

Lifecycle Fields

| Field | Type | Required | Description | |-------|------|----------|-------------| | isActive | boolean | System | Active status flag | | installDate | date | No | When installed/deployed | | purchaseDate | date | No | When purchased | | warrantyExpirationDate | date | No | Warranty end date | | endOfLifeDate | date | No | EOL date from manufacturer | | retirementDate | date | No | When retired from service | | lastPhysicalLocationDate | date | No | Last physical audit |

Contract & Billing Fields

| Field | Type | Required | Description | |-------|------|----------|-------------| | contractID | int | No | Associated contract | | contractServiceID | int | No | Service on contract | | contractServiceBundleID | int | No | Service bundle | | monthlyUnitCost | decimal | No | Monthly recurring cost | | setupFee | decimal | No | One-time setup fee | | hourlyRate | decimal | No | Hourly rate for T&M work |

RMM Integration Fields

| Field | Type | Required | Description | |-------|------|----------|-------------| | rmmDeviceID | int | No | RMM platform device ID | | rmmDeviceUID | string | No | RMM unique identifier | | rmmDeviceAuditID | int | No | RMM audit record ID | | rmmDeviceAuditLastUser | string | No | Last logged-in user from RMM | | rmmDeviceAuditOperatingSystem | string | No | OS from RMM audit | | rmmDeviceAuditDeviceNetworkAddress | string | No | IP from RMM |

User-Defined Fields

CIs support custom user-defined fields (UDFs) for organization-specific tracking:

  • Asset tags
  • Cost centers
  • Business criticality
  • Compliance tags
  • Custom lifecycle flags

CI Types

Configuration Item Types classify assets at the highest level:

| Type ID | Common Name | Examples | |---------|-------------|----------| | 1 | Server | Physical servers, VMs, cloud instances | | 2 | Workstation | Desktops, laptops | | 3 | Network Device | Routers, switches, firewalls, APs | | 4 | Printer | Network printers, MFPs | | 5 | Mobile Device | Phones, tablets | | 6 | Software | Licenses, subscriptions | | 7 | Domain | Domain names | | 8 | SSL Certificate | SSL/TLS certificates | | 9 | Cloud Service | SaaS subscriptions | | 10 | Other | Miscellaneous assets |

Note: Actual type IDs vary by Autotask instance. Query /v1.0/ConfigurationItemTypes to get your instance's specific values.

Querying Types

POST /v1.0/ConfigurationItemTypes/query
Content-Type: application/json
{
  "filter": [
    {"field": "isActive", "op": "eq", "value": true}
  ]
}

CI Categories

Categories provide secondary classification within types:

| Category Examples | Parent Type | Description | |-------------------|-------------|-------------| | Physical Server | Server | On-premises physical | | Virtual Server | Server | VMware, Hyper-V | | Cloud Server | Server | AWS, Azure, GCP | | Windows Workstation | Workstation | Windows PCs | | Mac Workstation | Workstation | Apple devices | | Firewall | Network Device | Security appliances | | Managed Switch | Network Device | L2/L3 switches | | Wireless AP | Network Device | Access points |

Category Hierarchy

Type: Server
├── Category: Physical Server
│   ├── Rack Mount
│   └── Tower
├── Category: Virtual Server
│   ├── VMware
│   └── Hyper-V
└── Category: Cloud Server
    ├── AWS EC2
    ├── Azure VM
    └── GCP Compute

Type: Network Device
├── Category: Firewall
│   ├── Hardware Firewall
│   └── Virtual Firewall
├── Category: Switch
│   ├── Core Switch
│   └── Access Switch
└── Category: Wireless
    ├── Access Point
    └── Controller

Related Items (CI Relationships)

Related Items establish connections between Configuration Items:

Relationship Types

| Relationship | Description | Example | |--------------|-------------|---------| | Parent/Child | Hierarchical | VM → Host server | | Dependency | Depends on | Application → Database server | | Peer | Equal relationship | Clustered servers | | Backup | Backup target | Primary → Backup NAS | | Network | Network connection | Server → Switch port |

Creating Relationships

POST /v1.0/ConfigurationItemRelatedItems
Content-Type: application/json
{
  "configurationItemID": 12345,
  "relatedConfigurationItemID": 67890,
  "relationshipDescription": "Hosted virtual machines",
  "relationshipTypeID": 1
}

Querying Relationships

{
  "filter": [
    {"field": "configurationItemID", "op": "eq", "value": 12345}
  ]
}

DNS Records

Track DNS records associated with CIs:

DNS Record Fields

| Field | Type | Description | |-------|------|-------------| | configurationItemID | int | Parent CI | | recordType | string | A, AAAA, CNAME, MX, TXT, etc. | | hostname | string | Record hostname | | value | string | Record value | | ttl | int | Time to live | | priority | int | Priority (for MX) |

Creating DNS Records

POST /v1.0/ConfigurationItemDnsRecords
Content-Type: application/json
{
  "configurationItemID": 12345,
  "recordType": "A",
  "hostname": "mail.acmecorp.com",
  "value": "192.168.1.100",
  "ttl": 3600
}

Common DNS Tracking Patterns

// Track all DNS records for a domain CI
const dnsRecords = await queryDnsRecords({
  filter: [
    {field: 'configurationItemID', op: 'eq', value: domainCiId}
  ]
});

// Find CIs with expiring SSL certs
const expiringSSL = await queryCIs({
  filter: [
    {field: 'configurationItemType', op: 'eq', value: SSL_CERT_TYPE},
    {field: 'warranty
Compartilhar X LinkedIn