Manage Campaigns
Current status: Beta
Manage Campaigns helps you preserve campaign-level context as work moves from creator discovery into later operations.
Best-fit scenarios
- You want one campaign anchor around shortlist, monitoring, and later ops work
- You need basic campaign records and overview data instead of a full CRM
- You want discovery, outreach preparation, monitoring, collections, email/message tasks, CRM, and exports to stay connected
Current beta scope
- Keep campaign-level records and overview data
- List, inspect, initialize, create, update, delete, open dropdown data, and read campaign dashboard data
- Reuse campaign context across adjacent beta operations
What beta means right now
- Public CLI and server commands exist for this domain
- The surface is still stabilizing and should not be treated as a fully mature collaboration suite
Key commands
Use schema before preparing write bodies:
noxinfluencer schema "campaign create"
noxinfluencer schema "campaign update"
Common campaign commands:
noxinfluencer campaign list --keyword shoes --page_size 5
noxinfluencer campaign init
noxinfluencer campaign get <campaign_id>
noxinfluencer campaign dashboard <campaign_id>
noxinfluencer campaign dropdown --page_size 20
Write commands default to dry-run:
noxinfluencer campaign create --body-file campaign.json --force
noxinfluencer campaign update <campaign_id> --body-file campaign.json --force
noxinfluencer campaign delete <campaign_id> --force
Current boundary
- It is not a full CRM
- Email, message, and CRM now have their own beta pages and approval guardrails
- It is not a negotiation execution surface
- It does not replace discovery, analysis, outreach preparation, or monitoring
