Email Tasks

Current status: Beta

Email Tasks lets you manage NoxInfluencer email-task records after you have selected creators and confirmed reliable email addresses.

Best-fit scenarios

You want to create or inspect email-task records
You need to manage recipients, sender settings, and approved content for an email task
You need to filter recipients by prior contact, CRM, collaboration, collection, or task state
You need to manage task collaborators and their member-management permission
You want to send or schedule a task after confirming the exact recipients, sender, timing, and content

Current beta scope

List email tasks and drafts
Read one task by task_id
Create, update, copy, or delete email tasks
Add, replace, and list task recipients
Delete or clear task recipients on unsent tasks
Save and inspect task-scoped recipient hide/deduplication filters
List available recipient filter options and filterable email tasks
List, replace, add, or remove task collaborators
Save task content and update sender settings
Send, schedule, or cancel an email task
List, save, and apply email content templates
List, replace, and delete email product cards
Read email task reports, team summary, and team breakdown metrics

Safe execution rules

Many email commands are JSON-first and use --body-file
Mutations default to dry-run; use --force only after you approve the exact action
Before email send or email schedule, read back the task and recipients
Confirm recipients, sender, scheduled time when relevant, and content approval before execution
email schedule requires plan_send_at in ISO 8601 format with a whole-hour timezone offset, such as Z, +08:00, or -05:00
Email reports distinguish email tracking replies from creator-level replied counts and inbound message counts
Team report filters use SaaS team member uid, not Gmail or enterprise sender mailbox accounts
Product cards use Product Center product_collect_id values
Recipient filters use the public body patches returned by email recipients filter options; do not invent raw SaaS field names
Collaborator commands use SaaS team user_uid; list collaborators first when you need to discover valid team members

Key commands

Inspect schema before building task, collaborator, recipient, filter, content, sender, template, or product-card bodies:

noxinfluencer schema "email create"
noxinfluencer schema "email collaborators add"
noxinfluencer schema "email recipients add"
noxinfluencer schema "email recipients filter update"
noxinfluencer schema "email content save"
noxinfluencer schema "email products replace"

Read task state before sending:

noxinfluencer email list --keyword shoes --page_size 10
noxinfluencer email drafts --page_size 10
noxinfluencer email get <task_id>
noxinfluencer email recipients list <task_id>

Manage recipient hide and deduplication filters only after reading supported options:

noxinfluencer email recipients filter options
noxinfluencer email recipients filter tasks
noxinfluencer email recipients filter get <task_id>
noxinfluencer email recipients filter update <task_id> --body-file recipient-filter.json --force

Manage task collaborators by team member user_uid:

noxinfluencer email collaborators list
noxinfluencer email collaborators list <task_id>
noxinfluencer email collaborators add <task_id> --body-file collaborator.json --force
noxinfluencer email collaborators remove <task_id> --body-file collaborator.json --force

Build the email task after you already have approved recipients and content:

noxinfluencer email create --body-file email-task.json --force
noxinfluencer email recipients add <task_id> --body-file recipients.json --force
noxinfluencer email recipients delete <task_id> --body-file recipient-delete.json --force
noxinfluencer email content save <task_id> --body-file content.json --force
noxinfluencer email sender update <task_id> --body-file sender.json --force

Send or schedule only after reading the task back:

noxinfluencer email send <task_id> --force
noxinfluencer email schedule <task_id> --body-file schedule.json --force
noxinfluencer email cancel <task_id> --force

Use email reports for post-send analysis:

noxinfluencer email report <task_id>
noxinfluencer email team-summary --task-ids <task_id>,<task_id>
noxinfluencer email team-breakdown --task-ids <task_id>,<task_id> --page_size 20

Attach product cards only after product records exist in Product Center:

noxinfluencer email products list <task_id>
noxinfluencer email products replace <task_id> --body-file email-products.json --force
noxinfluencer email products delete <task_id> <email_product_id> --force

Current boundary