CRM
Current status: Beta
CRM helps you query and update NoxInfluencer-owned relationship records after creator selection, collection work, or outreach preparation.
Best-fit scenarios
- You need to inspect CRM channels for selected creators
- You want to update cooperation status, labels, owner, email, URL, or notes on a channel
- You want to group CRM records for follow-up work
- You want to add CRM channels to an existing email task
- You need an async CRM export
Current beta scope
- Query CRM channels with JSON-first filters
- Read one CRM channel by opaque
creator_id - Update, archive, and restore CRM channels
- Create CRM export tasks
- Validate, preview, and apply
crm add-to-email - Validate, preview, and apply CRM batch updates
- List, create, update, and delete CRM labels
- List, read, create, update, and delete CRM groups
Safe execution rules
- CRM query and many CRM writes are JSON-first and use
--body-file - Staged workflows should run
validate, thenpreview, thenapply --force - Direct mutations such as update, archive, restore, export, group create/update/delete, and add-to-email apply require explicit approval before
--force - Preserve stable opaque IDs such as
creator_id,group_id,task_id, andexport_id - For batch previews and applies, report existing, creatable, and created counts when present instead of inferring success from requested IDs alone
Key commands
Inspect exact body contracts before building JSON-first requests:
noxinfluencer schema "crm list"
noxinfluencer schema "crm batch-update apply"
noxinfluencer schema "crm labels create"
Read CRM channels and groups:
noxinfluencer crm list --body-file crm-query.json
noxinfluencer crm get <creator_id>
noxinfluencer crm groups list --keyword vip --page_size 20
noxinfluencer crm groups get <group_id>
Manage labels for batch tagging:
noxinfluencer crm labels list --keyword vip --page_size 20
noxinfluencer crm labels create --body-file crm-label.json --force
noxinfluencer crm labels update <label_id> --body-file crm-label.json --force
noxinfluencer crm labels delete <label_id> --force
Use the returned label_id in crm batch-update with labels.operation=add or remove:
noxinfluencer crm batch-update validate --body-file crm-batch-update.json
noxinfluencer crm batch-update preview --body-file crm-batch-update.json
noxinfluencer crm batch-update apply --body-file crm-batch-update.json --force
Bridge CRM channels into an existing email task:
noxinfluencer crm add-to-email validate --body-file crm-add-to-email.json
noxinfluencer crm add-to-email preview --body-file crm-add-to-email.json
noxinfluencer crm add-to-email apply --body-file crm-add-to-email.json --force
Current boundary
- This is NoxInfluencer CRM, not an external CRM integration
- Owner-only or archive-only updates may require an existing CRM channel
- Platform creator IDs can be materialized into CRM only for supported cooperation-status or label update paths; owner-only, email-only, remark-only, and URL-only updates require an existing CRM channel
crm add-to-emailonly adds existing NoxInfluencer CRM channels to an existing email task- CRM labels are shared remark/message labels;
crm_channel_countmay not equal every historical CRM row - CRM does not replace creator discovery, creator analysis, or contact retrieval
