Pipeline

Add a note to a candidate's application, or to one of their workflow steps (stageId) or Activity Runs (activityRunRef). Everyone on the Job's team can read it.

One Job's Review Board counts and conversion, with UMatch, each named Interview activity and each Job Workflow Playground activity scored separately; plus the Command Centre's figures: email reach, the Pitch Room funnel, 14-day and week-on-week history, sources and days waiting per stage.

Move an Applied candidate to Invyted. Invyte emails them an invitation to continue their application, with your own message if you write one. The result says whether the email is queued, sent, failed or unconfirmed, and what to do next.

Shortlist or reject a candidate on the board. Nothing is emailed; their open steps close and their application page closes. Moves that would close work they have started need those warnings confirmed by name. When it would cancel an invitation or reminder email still waiting to go to them, it lists those emails and waits for your go-ahead.

Move a candidate to a step of the Job's workflow (pipeline.placementMap lists the steps). Run pipeline.previewPlacement first. When the move opens steps for them, Invyte emails them that their next step is ready. Returns the plan it committed.

Choose a path for a candidate waiting at a Human Review step. When the path opens steps for them, Invyte queues an email telling them their next activities are ready. Returns where the candidate went and whether that email was queued.

Schedule reminder emails asking a candidate to finish their steps (gentle, standard or finish today), or stop them.

Record a call with a candidate: how it went, details they shared, a note and a follow-up date. Nothing is sent to them; "Not interested" stops their reminder emails.

For Talent Hub people (keys as `talent.list` gave them, an Invyte Network person's `person_v1.…` key included), which email each would get if added to this Job now. Adds no one.

An Application's contact history, newest first: emails sent or held (what happened to each), calls, reminders, notes and moves, plus the next call-back and reminders.

Email a candidate about their next step on this Job, in your words or Invyte's. Only when a Nudge is due: not while one is waiting, after they unsubscribed, or once the Job is closed.

Put a Talent Hub person forward for a Job, by the key `talent.list` gave (an Invyte Network person's `person_v1.…` key works too). A member who said yes to roles like this joins the pipeline and is told; anyone else is asked first by email (members to say yes, others to join Invyte). Never sends when they declined this Job, asked not to be emailed about roles, or have no address: it is refused with the reason and what to do instead.

One Job's Review Board, a page of cards at a time with the whole board's counts: each card with the candidate's place, UMatch, steps, card footer (what is next), invitation and contact state. Contact details only on request, to those who may contact the Job's candidates.

One Job's Application updates, newest first: moves, decisions, placements and status changes, with who made them. 20 a page by default; pass `next` as `cursor` for older ones.

One Application's progress ledger, oldest first: applied, invited, work started and finished, evidence ready, gates, reviews, decisions, placements and dispositions, as ids and codes.

One Job's to-dos as the Command Centre lists them, and the candidates who stopped moving, each with why, since when and who moves them: an operation you can run, or in words when someone else must (another recruiter, or Invyte, which handles it). Candidates come a page at a time.

Each undecided candidate on a Job with the facts that decide whether to act: UMatch fit against the Job's floor, how they engaged, their Decision path and its track, momentum against the Job, whether the Job still needs people, and nudges sent. `allowed` is what an agent may do for them now, already filtered by the nudge limits; fast-track candidates come first. Without `jobId`, every open Job you can see, one Job a page.

One Job's open Human Review tasks, a page at a time, with every group's step, instructions, task count and the paths a decision can take.

What happened since your cursor on the Jobs you can see: contact, email delivery, progress, share and sourcing events, oldest first. Poll with the returned cursor.

The candidates you bookmarked on one Job's board. Bookmarks are private to you.

Bookmark candidates on a Job's board, or remove the bookmark, for up to 100 at once. Bookmarks are private to you; nobody is told.

Extend the Pitch Room deadline by 1, 3, 7 or 14 days for up to 25 candidates whose deadline passed with steps still to do. Every candidate named must be due for it; anyone who isn't is named in the refusal, to leave out. Invyte emails each their new deadline, except candidates who haven't signed in yet, whose remaining steps wait on a check or review, or who have nothing left to do: the review and the result say per candidate who is emailed, and why not.

Call back a Nudge before it goes, by the notificationId pipeline.nudge or outreach.send returned, until its undoUntil. After that it has been sent and can't be undone.

When reminder emails at an urgency (gentle, standard, finish today) would reach a candidate, or why none would. Schedules nothing; pipeline.setReminders does.

What moving a candidate to a workflow step would do, as the board's Move dialog shows it: where they land and what they're asked to do; any Human Review or wait they're left at, and why; the path a Decision on the way takes; steps and other reviewers' open review tasks it closes; Intake checks it skips; work kept; work they started that must be confirmed; and whether they're emailed. A Decision that needs a path names its paths. Moves no one; pipeline.placeAtNode does.

Every step of a candidate's workflow, with where they are on each and whether they can be placed there now (and why not): activities, Decisions with their paths, Human Reviews, Short List and Reject. Use it to pick pipeline.previewPlacement's targetNodeId, including to undo a rejection.

The team's notes on a candidate's application, newest first, with who wrote each: all of them, or those on one workflow step or Activity Run.

Change a note's text or rating. Only its author, or an organization admin, may.

Delete a note for good. Only its author, or an organization admin, may.