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

1. Start with one campaign anchor that reflects your market, objective, and working scope
2. Move reviewed creators into a collection instead of leaving them scattered across separate sessions
3. Use collection add-creators for reviewed creator IDs, or collection import-file when you are importing your own creator URL spreadsheet
4. Use collection validate/preview/apply workflows before high-side-effect grouped operations
5. Move the right collection + platform slice into CRM when relationship state, labels, or add-to-email work is needed
6. Use CRM labels when you need stable follow-up segmentation across creators
7. Use Product Center when an email task needs product cards
8. Use short links when an approved destination needs a normal Nox tracking link
9. Use affiliation when the workflow is specifically about Shopify affiliate campaigns, members, discount codes, or affiliate tracking links
10. Apply email recipient filters when the task should hide creators already contacted, grouped, or present in another email task
11. Add email collaborators when another team member needs task access or member-management permission
12. Attach approved briefs or files to the email task when the outreach requires them
13. Use email tasks for first platform email outreach by creator_id, or for approved external email recipients you already own
14. Use message threads only for existing thread_id replies, and attach draft files before send or schedule when needed
15. Use needs_reply and last_message_direction instead of unread count to decide which message tasks still need action
16. Use message creator/project filters when you need to find threads by SaaS task owner, team member, project, cooperation status, or label
17. Use message projects <thread_id> when the opened task is already replied but NoxInfluencer still shows pending work for the same creator
18. Use email reports, team summary, and team breakdown after send when you need reply metrics
19. Launch collection, CRM, or brand-monitor exports when you need a shareable file
20. 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 recipients filter options
noxinfluencer email collaborators list
noxinfluencer email attachments list <task_id>
noxinfluencer email attachments upload <task_id> --file brief.pdf --force
noxinfluencer short-link list --page_size 20
noxinfluencer affiliation stores list
noxinfluencer affiliation campaigns list --store-id <store_id> --page_size 20
noxinfluencer message creator-filters
noxinfluencer message project-filters --creator_uids <user_uid>
noxinfluencer message list --status deal --page_size 20
noxinfluencer message list --project_ids email_task:<task_id> --creator_uids <user_uid>
noxinfluencer message get <thread_id>
noxinfluencer message projects <thread_id>
noxinfluencer message attachments list <thread_id>
noxinfluencer message attachments upload <thread_id> --file brief.pdf --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, attachments, and scheduled time
• Whether a link is a normal Nox short link or an affiliate tracking link
• Shopify store_id, affiliate campaign_id, and member_id values when the workflow uses Affiliation
• The reply-state fields that drove message follow-up decisions, especially needs_reply, last_message_direction, and pending_reason
• The message filter IDs used to reconstruct a thread view, including project_ids, creator_uids, label_id, and coop_status
• The label_id, product_collect_id, task_id, thread_id, attachment_id, and export_id values 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
• Message pending state cannot be cleared with an empty reply; task-level mark-handled is not exposed in the current public commands
• Shopify store authorization stays in SaaS; do not treat the CLI as a store authorization surface
• You may still rely on discovery, analysis, outreach preparation, and monitoring for the core creator decisions

Recommended reading

• Manage Campaigns
• Collections
• CRM
• Email Tasks
• Message Threads
• Exports
• Product Center
• Short Links
• Affiliation
• Brand Monitor