Skip to Content
InvyteDocs
Jobs & workflows

List the fields a Decision rule can check

Before writing a Decision step's rules, read which fields they may compare: UMatch and other Application signals (overall score, red flags, must-haves, experience, verification) and earlier steps' results, each with its type, scale, allowed values and operators. Name a Job (its workflow draft), a workflow or a template, and the Decision step or the step a new Decision will follow. Rules go in the Decision's settings as `paths: [{ name, logic: "and", conditions: [{ sourceType, signalKey or sourceNodeId, field, operator, value }] }]` with `elsePath`, the path everyone else takes; each path name and the elsePath is an exit to connect. Never guess a field; a rule that reads one not listed here is refused.

POST
/operations/workflows.decisionFields

Authorization

bearer
headerAuthorizationBearer <API key or OAuth token>

An organization API key (ink_live_…, ADR-0124), or the OAuth access token a person's AI client gets from the Recruiter MCP sign-in. Only the Authorization header is accepted.

Header Parameters

Idempotency-Key?string

Makes a write safe to repeat: the same key and input return the first result. Required for agents' writes and for anything a person confirms.

Match^[A-Za-z0-9._:-]+$
Length8 <= length <= 128

Request Body

application/json
  1. body
input*
confirmation?string

The id from a confirm or awaiting_approval Outcome, sent with the same input and key to go ahead.

Response Body

Done. A replay of the same key and input omits output.

application/json
  1. response
status*unknown
output?
actionId*string
Example Request
curl -X POST 'https://www.invyte.ai/api/recruiter/v1/operations/workflows.decisionFields' \  -H 'Content-Type: application/json' \  -d '{  "input": {}}'
Example Response
{  "status": "done",  "output": {    "stepId": "string",    "sources": [      {        "label": "string",        "sourceType": "global",        "signalKey": "string",        "sourceNodeId": "string",        "fields": [          {            "field": "string",            "label": "string",            "type": "string",            "description": "string",            "numeric": {              "min": 0,              "max": 0,              "step": 0,              "displayScale": 0,              "unit": "percent"            },            "options": [              {                "value": "string",                "label": "string"              }            ],            "operators": [              "string"            ]          }        ]      }    ]  },  "actionId": "string"}

Create a workflow POST

Create a workflow in the organization's library, blank (Application Received only) or from a template. Then edit its steps with workflows.update.

Delete a workflow template POST

Remove one of your organization's templates from its template library. Workflows and Jobs started from it keep their steps; Invyte's templates can't be deleted.