Organize Campaign Workflows
Use this guide when you already know your campaign direction and want the same working set to keep moving through the beta marketing ops pages.
Recommended minimal loop
- Start with one campaign anchor that reflects your market, objective, and working scope
- Move reviewed creators into a collection instead of leaving them scattered across separate sessions
- Use
collection add-creatorsfor reviewed creator IDs, orcollection import-filewhen you are importing your own creator URL spreadsheet - Use collection validate/preview/apply workflows before high-side-effect grouped operations
- Move the right collection + platform slice into CRM when relationship state, labels, or add-to-email work is needed
- Use CRM labels when you need stable follow-up segmentation across creators
- Use Product Center when an email task needs product cards
- Use email tasks for first email outreach to known, approved recipients
- Use message threads only for existing
thread_idreplies - Use email reports, team summary, and team breakdown after send when you need reply metrics
- Launch collection, CRM, or brand-monitor exports when you need a shareable file
- Feed the updated result back into the same campaign context
Useful command sequence
Use this as a starting shape; inspect schema before preparing JSON bodies:
noxinfluencer campaign get <campaign_id>
noxinfluencer collection add-creators --body-file add-creators.json --force
noxinfluencer collection refresh-email validate --body-file refresh-email.json
noxinfluencer collection refresh-email preview --body-file refresh-email.json
noxinfluencer collection refresh-email apply --body-file refresh-email.json --force
noxinfluencer crm labels list --page_size 20
noxinfluencer crm batch-update preview --body-file crm-batch-update.json
noxinfluencer crm batch-update apply --body-file crm-batch-update.json --force
noxinfluencer email report <task_id>
noxinfluencer export get <export_id>
What to keep stable
- The campaign goal and market
- The creator identities you decided to keep
- The logic behind who was included or excluded
- The approval state for recipients, sender, content, and scheduled time
- The
label_id,product_collect_id,task_id,thread_id, andexport_idvalues used in follow-up operations - The reason you exported the working set
Current boundary
- This is a beta workflow bridge, not a full external CRM, email, messaging, or spreadsheet playbook
- You may still rely on discovery, analysis, outreach preparation, and monitoring for the core creator decisions




