Campaigns — search audience, hydrate, and run

What a campaign is

A campaign is an outbound workspace effort built from:

• LinkedIn profiles discovered using a Fulreach-supplied search URL.
• Behaviour flags (daily invite limit, send windows, optional invite note, optional behaviours like reviewing profile/post before invites where enabled).

Fulreach ingest flows pull profiles → creates campaign prospect links queued for invitation → background workers honour scheduling + provider constraints.

Campaign list responses compute totals & status:

• Paused (active=false)
• Empty / pre-first-send (queued style rollup)
• In progress (in_progress)
• Exhausted queued attempts vs total (completed when every tracked prospect transitioned through relevant terminal states aggregated by server logic described in internals)

Updating name, invite note, daily limit, windows, behavioural toggles PATCHes persisted fields and may trigger reschedule for queued invitations per backend implementations (Fulreach evolves across Python scheduling vs TypeScript coordinator—expect some subtle differences surfaced as “rescheduled count” metadata).

Optional auto‑DM/video interplay may auto-insert default conversational templates when flagged at creation time (best‑effort; failure does not block campaign creation internally).

Campaign creation rejects early if eligible candidate count undershoots a minimum guard—Fulreach deletes the tentative campaign returning 409 style guard telling you widen search loosen filters versus raising dead campaigns.