Individual skill
aai-pipedrive
Use aai-cli to manage Pipedrive leads, persons, organizations, deals, labels, activities, notes, file attachments, field definitions, users, pipelines and stages, deal flow/stage history, and synced mailbox data.
api/domains/agents/aai_cli_skills/bundled/skills/aai-pipedrive/SKILL.md
Source commit 724a8ace26035d19f64cc707fbc0b4ba110cbc95
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 111
- Repository last updated
- Nov 10, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent Repository topic
- agent-skills Repository topic
- agentic-ai Repository topic
- helm Repository topic
- helm-charts Repository topic
- kubernetes Repository topic
- python Repository topic
- cli Repository topic
- cli-tool Repository topic
- data Derived category
- productivity Derived category
- productivity-notes Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,076 bytesreferences/command-reference.mddoc · 27,003 bytes
Read excerpt
# aai-cli Pipedrive
Use this skill when working with the Pipedrive CRM through `aai-cli pipedrive`.
Before running commands, confirm the active profile or pass `--profile`. Pipedrive profiles use a personal API token (`auth_type = "pipedrive_personal_token"`); no `owner`/`repo`-style scoping is needed since a profile maps to one Pipedrive account.
For a combined view of a CRM record, prefer `deals view` / `persons view` / `organizations view` over separately calling `get` + `activities` + `notes` — it aggregates all three (plus optional email) in one response. For deal stage-transition history specifically, use `deals flow`, which surfaces `dealChange` entries with `field_key: "stage_id"`.
Meeting transcripts and other documents are usually file attachments, not notes. List them with `files list --deal-id` / `--person-id` / `--org-id` and fetch each with `files download <id> --output PATH`, then convert it to text before reading.
Record payloads refer to custom fields by hash key and to option values (Industry, custom dropdowns) by numeric ID. Resolve them with `fields <deals|persons|organizations> list` before matching records by a field's name or value.
List commands stop at `--limit` (usually 50). When `_aai.pagination.status` is `more_available`, the result is partial — raise `--limit` before counting or summarizing records.
