# Requirements: Account Health Autopilot

> **Version 1.1.0 · Last updated 2026-10-22 · Estimated setup time: 60–120 minutes**

Use this checklist before you hand CLONE-INSTRUCTIONS.md to your clone. Your clone will also check most of this during discovery.

---

## 1. Required skills / operators

Use the exact operator names below. Your clone will report the names it finds in your catalog.

> Skill names can differ slightly between orgs. Confirm the exact names in your skill catalog before saving the skill.

| # | Skill / operator | What it's used for | Notes |
|---|---|---|---|
| 1 | **Salesforce:** `SalesforceAccountOperator`, `SalesforceOpportunityOperator`, `SalesforceCaseOperator`, `SalesforceActivityOperator` **or HubSpot:** `HubspotCompanyOperator`, `HubspotDealOperator`, `HubspotEngagementOperator` | Build the account list, read the support signal, write the three health fields | Choose one CRM. Must support **read and write**. Salesforce: Cases are the support signal. HubSpot: no tickets/cases operator, so notes, tasks and engagements are the signal |
| 2 | **Gmail** (`GoogleGmailOperator`) or **Outlook** (email operator) | Search email by company name and domain; send the approval request and weekly report | Must be the **clone's own** inbox, or one shared with it |
| 3 | **Transcript source:** `GoogleDriveCoreOperator` or `Microsoft_OneDrive` folder, or `meeting_archive` (plus `call_archive` for phone calls) | Read call transcripts from the last 7 days | Folder is `{TRANSCRIPTS_FOLDER}`, or the clone's own archives |
| 4 | **Scheduled task** (`platform`) | Run the skill weekly at `{RUN_TIME}` | Platform feature; the clone may be able to create it |

## 2. Required connections and permissions

| Connection | Minimum permission | Why |
|---|---|---|
| CRM (Salesforce or HubSpot) | **Read** accounts/companies, opportunities/deals, cases (Salesforce) or engagements (HubSpot); **edit** `{PAIN_POINTS_FIELD}`, `{HEALTH_FIELD}`, `{INTEGRATIONS_NEEDED_FIELD}` | Scope, cases, and writing results. **Field-level edit rights are required**, not just record access |
| CRM (setup only, optional) | Admin / metadata rights to create custom fields | Only if you want the clone to create the three fields for you |
| Gmail or Outlook | **Read** + **Send** | Search activity; send the report to `{REPORT_RECIPIENTS}` only |
| Google Drive or OneDrive | **View** `{TRANSCRIPTS_FOLDER}` and subfolders | Read transcripts |
| Linear (if used) | **Read** issues | Open issues, integration requests |
| Slack or Teams (if used) | **Post** to `{TEAM_CHANNEL}` | Report delivery |

All connections are made by **you** through sign-in (OAuth). Your clone never needs your password.

## 3. Optional add-ons

| Add-on | Adds | Examples |
|---|---|---|
| **Linear** (`Linear_Operator`) | Bugs, feature and integration requests per customer (strongly recommended) | Read-only |
| **Slack or Microsoft Teams** | Post the report and approval request to a team channel | Delivery only; cannot be read as a source |
| **Meeting archive** (`meeting_archive`, `call_archive`) | The clone's own meeting and phone call transcripts as a source | Calls the clone attended |
| **Product usage export** (`GoogleSheets-Operator` or `Microsoft_Excel`) | Logins and usage trends; a useful signal for silent risk | Only if you keep a usage export in a sheet |
| **Weekly-Account-Health-Update** (prebuilt skill) | Quick-start alternative, attached via `platform` | This card's custom skill gives full control instead |

> **Strongly recommended:** Linear. Without it, integration requests can't be checked for tickets and bug activity is only seen through the CRM support signal.

### The three CRM fields

| Field | Type | Values / limits |
|---|---|---|
| `{PAIN_POINTS_FIELD}` | Long text area | Capacity 2,000+ characters; content kept under ~1,500 |
| `{HEALTH_FIELD}` | Picklist (single select) | Bright Green, Green, Yellow, Orange, Red, Black (or your `{HEALTH_SCALE}`), spelled exactly the same in the skill |
| `{INTEGRATIONS_NEEDED_FIELD}` | Long text area (or text 255+) | Never blank: "None requested" if none |

All three go on the object you choose as `{WRITE_TARGET}` (account or opportunity). The clone can give your CRM admin step-by-step instructions to create them (Salesforce or HubSpot).

### Salesforce to HubSpot mapping

| Concept | Salesforce | HubSpot |
|---|---|---|
| **Account / company** | Account (`SalesforceAccountOperator`) | Company (`HubspotCompanyOperator`) |
| **Opportunity / deal** | Opportunity (`SalesforceOpportunityOperator`) | Deal (`HubspotDealOperator`) |
| **Support signal** | Case (`SalesforceCaseOperator`) | No tickets/cases operator: notes, tasks and engagements (`HubspotEngagementOperator`) |
| **Activity / task** | Task / Event (`SalesforceActivityOperator`) | Engagement: note, task, call (`HubspotEngagementOperator`) |
| **Custom field** | Custom field (Object Manager) | Custom property (Settings, Properties) |
| **Long text type** | Text Area (Long) | Multi-line text |
| **Picklist type** | Picklist | Dropdown select |
| **Validation rule** (`{REQUIRED_FIELDS}`) | Validation rule / required field | Required property in pipeline or form |
| **Field-level permission** | Field-level security (profile / permission set) | Property edit permissions |
| **Current customer flag** (`{CUSTOMER_DEFINITION}`) | e.g. Account Type = Customer | e.g. Lifecycle stage = Customer |

Field names vary by setup. Write your own rule for `{CUSTOMER_DEFINITION}` in plain words.

### Google Workspace to Microsoft 365, Slack to Teams

| Concept | Google Workspace | Microsoft 365 |
|---|---|---|
| Email | Gmail (`GoogleGmailOperator`) | Outlook |
| Transcript folder | Google Drive (`GoogleDriveCoreOperator`) | `Microsoft_OneDrive` folder |
| Report delivery | Slack | Microsoft Teams |

## 4. Data prerequisites

- [ ] **Customer accounts have domains.** Each account has a website or email domain filled in, and key contacts have email addresses.
- [ ] **Clear customer flag.** Current customers are consistently marked (your `{CUSTOMER_DEFINITION}`).
- [ ] **Transcripts are saved somewhere the clone can read**, with dates in the file name or metadata, in `{TRANSCRIPTS_FOLDER}` (or the clone attends calls and keeps its own archive).
- [ ] **The three fields exist** (or you're ready to create them) on `{WRITE_TARGET}`.
- [ ] **Picklist values match** `{HEALTH_SCALE}` exactly.
- [ ] **Validation rules known.** You know which fields must be filled for a save (`{REQUIRED_FIELDS}`).
- [ ] **Name mappings drafted.** A starting list of aliases, product names and parent/child links (`{NAME_MAPPINGS}`).
- [ ] **Exclusions listed.** Internal, test and referral/partner records (`{EXCLUSIONS}`).

## 5. Roles and permissions

| Who | Needs to |
|---|---|
| **Clone admin** (owner of the clone in the Clone platform) | Attach skills/operators, approve the plan, save the skill, create/approve the scheduled task |
| **CRM admin** | Create the three fields (if the clone can't), grant the integration user field-level edit rights, confirm validation rules |
| **Connection owner(s)** | Complete OAuth sign-in for CRM, email, file storage, tracker, chat |
| **Transcript folder owner** | Share `{TRANSCRIPTS_FOLDER}` with the clone |
| **Weekly approver** (usually a CS lead, in `{REPORT_RECIPIENTS}`) | Review the change table each week and reply yes / yes except / no |
| **CS team / account owners** | Sanity-check grades for their accounts, suggest name mappings and exclusions |

## 6. Estimated setup time

| Step | Time |
|---|---|
| Pre-flight check (this doc) | 10 min |
| Clone discovery + placeholders + plan | 15–20 min |
| Create CRM fields and permissions (if needed) | 10–30 min |
| Your sign-ins and folder sharing | 10–20 min |
| Save skill + scheduled task | 5–10 min |
| Dry run + review + test-record write | 20–30 min |
| **Total** | **60–120 min** |

## 7. Pre-flight checklist

- [ ] I'm the clone admin (or have one available)
- [ ] Salesforce or HubSpot operators available in my catalog, with **read and write** support
- [ ] I (or a CRM admin) can grant edit access to three fields for the clone's CRM user
- [ ] Gmail or Outlook attached (or can be), with send permission
- [ ] Transcripts are in a folder I can share, or the clone has a meeting archive
- [ ] I can create scheduled tasks (or the clone can)
- [ ] (Optional) Linear operator (`Linear_Operator`) available
- [ ] (Optional) Slack or Teams connection for `{TEAM_CHANNEL}`
- [ ] I know my `{CUSTOMER_DEFINITION}` and `{ACCOUNT_SCOPE}`
- [ ] I've chosen `{WRITE_TARGET}` (account or opportunity)
- [ ] I have a first draft of `{NAME_MAPPINGS}` and `{EXCLUSIONS}`
- [ ] I know (or can find out) `{REQUIRED_FIELDS}`
- [ ] I've decided `{REPORT_RECIPIENTS}`, the weekly approver and `{RUN_TIME}`
- [ ] I can create a clearly labelled test record in the CRM for the write test

## 8. You're ready when…

- ✅ Every **required** item in section 1 is attached and its connection is signed in.
- ✅ The three fields exist on `{WRITE_TARGET}` and the clone's CRM user can edit them.
- ✅ The health picklist values match `{HEALTH_SCALE}` exactly.
- ✅ You have answers for all the placeholders in the README.
- ✅ Someone is named as the weekly approver.
- ✅ You've set aside ~30 minutes for the dry run and review.

Then download **CLONE-INSTRUCTIONS.md** and give it to your clone.