Receber por email
← Voltar para o catálogo

Autotask CRM

Use this skill when working with Autotask CRM - companies, contacts, sites/locations, and opportunities. Essential for MSP account management, client onboarding, and relationship tracking in Autotask PSA.

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-crm/svg)](https://www.skillteca.com.br/skills/autotask-crm)

Skills relacionadas

Ver todas de Documentos →

Alerta por categoria

Receba novas skills de Documentos toda segunda

1 email curto, só com as skills novas de Documentos. 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 CRM Management

Overview

Autotask CRM manages the core entities that define your client relationships: companies (accounts), contacts, and sites. Proper CRM data is foundational - tickets, contracts, projects, and billing all depend on accurate company and contact information.

Key Concepts

Company (Account)

The primary entity representing a client organization.

| Field | Description | Required | |-------|-------------|----------| | id | Unique identifier | System | | companyName | Official company name | Yes | | companyType | Customer, Lead, Prospect, etc. | Yes | | phone | Main phone number | No | | address1 | Street address | No | | city | City | No | | state | State/Province | No | | postalCode | ZIP/Postal code | No | | country | Country | No | | webAddress | Website URL | No | | parentCompanyID | Parent company for hierarchies | No | | ownerResourceID | Account manager | No | | classification | Classification category | No |

Company Types

| ID | Type | Use Case | |----|------|----------| | 1 | Customer | Active paying clients | | 2 | Lead | Potential new business | | 3 | Prospect | Qualified leads | | 4 | Dead | Churned/lost clients | | 5 | Vendor | Suppliers and partners | | 6 | Partner | Strategic partners |

Contact

Individual people at a company.

| Field | Description | Required | |-------|-------------|----------| | id | Unique identifier | System | | companyID | Associated company | Yes | | firstName | First name | Yes | | lastName | Last name | Yes | | emailAddress | Primary email | No | | phone | Direct phone | No | | mobilePhone | Mobile number | No | | title | Job title | No | | isActive | Active status | Yes | | isPrimaryContact | Primary contact flag | No |

Site/Location

Physical locations for a company (for on-site service).

| Field | Description | Required | |-------|-------------|----------| | id | Unique identifier | System | | companyID | Parent company | Yes | | name | Site name | Yes | | address1 | Street address | No | | city | City | No | | isActive | Active status | Yes | | isPrimaryLocation | Primary site flag | No |

API Patterns

Creating a Company

POST /v1.0/Companies
Content-Type: application/json
{
  "companyName": "Acme Corporation",
  "companyType": 1,
  "phone": "555-123-4567",
  "address1": "123 Main Street",
  "city": "Springfield",
  "state": "IL",
  "postalCode": "62701",
  "country": "United States",
  "webAddress": "https://acme.example.com",
  "ownerResourceID": 29744150
}

Searching Companies

GET /v1.0/Companies/query?search={"filter":[{"field":"companyName","op":"contains","value":"acme"}]}

Common Search Patterns

Search by name:

{
  "filter": [
    {"field": "companyName", "op": "contains", "value": "acme"}
  ]
}

Active customers only:

{
  "filter": [
    {"field": "companyType", "op": "eq", "value": 1},
    {"field": "isActive", "op": "eq", "value": true}
  ]
}

Companies by account manager:

{
  "filter": [
    {"field": "ownerResourceID", "op": "eq", "value": 29744150}
  ]
}

Updating a Company

PATCH /v1.0/Companies
Content-Type: application/json
{
  "id": 12345,
  "phone": "555-987-6543",
  "webAddress": "https://newsite.acme.com"
}

Creating a Contact

POST /v1.0/Contacts
Content-Type: application/json
{
  "companyID": 12345,
  "firstName": "John",
  "lastName": "Smith",
  "emailAddress": "john.smith@acme.example.com",
  "phone": "555-123-4567",
  "mobilePhone": "555-987-6543",
  "title": "IT Director",
  "isActive": 1,
  "isPrimaryContact": true
}

Searching Contacts

Contacts for a company:

{
  "filter": [
    {"field": "companyID", "op": "eq", "value": 12345},
    {"field": "isActive", "op": "eq", "value": 1}
  ]
}

Search by email:

{
  "filter": [
    {"field": "emailAddress", "op": "eq", "value": "john.smith@acme.example.com"}
  ]
}

Creating a Site

POST /v1.0/CompanyLocations
Content-Type: application/json
{
  "companyID": 12345,
  "name": "Main Office",
  "address1": "123 Main Street",
  "city": "Springfield",
  "state": "IL",
  "postalCode": "62701",
  "country": "United States",
  "isPrimaryLocation": true,
  "isActive": 1
}

Common Workflows

Client Onboarding

  1. Create company record
  2. Set company type to Customer
  3. Assign account manager
  4. Add billing information
  1. Create primary contact
  2. Mark as primary contact
  3. Verify email address
  1. Create site(s)
  2. Add all service locations
  3. Mark primary location
  1. Set up contract
  2. Associate with company
  3. Define service levels
  1. Configure billing
  2. Payment terms
  3. Tax information

Contact Management

  1. Verify before creating
  2. Search for existing contact by email
  3. Check for duplicates
  1. Maintain accuracy
  2. Update titles when employees change roles
  3. Mark contacts inactive when they leave
  4. Add new contacts as needed
  1. Track relationships
  2. Note who can authorize work
  3. Track technical vs billing contacts

Company Hierarchy

For MSPs managing parent/child company relationships:

  1. Create parent company first
  2. Create child companies with parentCompanyID
  3. Contracts can roll up to parent
  4. Reporting aggregates by hierarchy

Error Handling

Common API Errors

| Code | Message | Resolution | |------|---------|------------| | 400 | Duplicate company name | Check for existing company, use unique name | | 400 | Invalid email format | Verify email address syntax | | 404 | Company not found | Verify company ID exists | | 409 | Contact already exists | Search for existing contact first |

Validation Errors

"CompanyName is required" - Company name cannot be empty or null

"Invalid companyType" - Must use valid company type ID from picklist

"Email already exists" - Contact with this email already exists

Best Practices

  1. Standardize naming - Use consistent company name formats
  2. Verify before creating - Always search first to prevent duplicates
  3. Maintain data quality - Regular audits of contact information
  4. Use classifications - Categorize companies for reporting
  5. Track account managers - Assign ownerResourceID for accountability
  6. Keep contacts current - Inactive former employees
  7. Document relationships - Use notes for key account information

Related Skills

  • [Autotask Tickets](../tickets/SKILL.md) - Service tickets for companies
  • [Autotask Contracts](../contracts/SKILL.md) - Service agreements
  • [Autotask Projects](../projects/SKILL.md) - Project management
Compartilhar X LinkedIn