Aaronontheweb / Aaronontheweb/pipedrive-cli
persons create/update: no way to set person labels
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
What happened
The pipedrive persons update and pipedrive persons create commands do not expose person labels. Labels are a first-class field on a person (the label_ids array, with an accompanying label display name), but there is no flag to set them.
Repro
pipedrive persons update <id> --help
Shows only:
-n, --name-e, --email-p, --phone-o, --org-id-a, --address-c, --custom-field
No --label-id / --labels option. --custom-field cannot be used as a workaround because labels are a dedicated field, not a custom field.
Expected
A way to add/remove person labels from the CLI, e.g. --label-id <id> (repeatable) on both persons create and persons update, mirroring the label_ids field on the person object.
Context
This blocks CRM-hygiene automation (e.g. tagging procurement contacts on an account) that today must fall back to the REST API directly.
Environment
pipedrive --version→0.13.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the implementations of the pipedrive persons create and pipedrive persons update commands, using their help output and the person object's label_ids field as the guide. Add a repeatable label option to both commands and verify that help exposes it and that labels can be set during create and update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100