> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hopae.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflows

> A workflow decides which connections are offered, which data you receive, and how the hosted screen looks.

A **workflow** is one verification setup inside an app. Every verification runs one workflow. Edit workflows in the Console under **Verification → Workflow**.

## The default workflow

* A **Quickstart** sandbox app and a production app start with a default workflow.
* In a **Start from scratch** sandbox app, create one. The first workflow becomes the default.
* Verifications use the default unless you pass `workflow_id` (OIDC) or `workflowId` (REST). Copy the id next to the workflow name in the editor.

Without any workflow, verifications fail with `409 WORKFLOW_NOT_CONFIGURED`.

## What a workflow controls

The editor has one tab for each part:

| Tab | Controls |
| :- | :- |
| **Claims** | The [normalized claims](/v2/guides/verifications/normalized-user-data) you receive, plus extra claims for specific connections. Tick **Source ID** to receive `source_id`, a stable identifier for the person. Claims the source could not provide are listed in `missing_claims`. |
| **Connections** | Which [activated connections](/v2/guides/concepts/connections/activation) are offered. Only enabled connections appear in the hosted flow or can be started with the API. Others return `403 PROVIDER_DISABLED_IN_WORKFLOW`. |
| **Branding** | The name and logo users see. See [Branding](/v2/guides/concepts/branding). |
| **Flow** | Rules after the verification, such as a minimum level of assurance (advanced). See [Workflow Nodes](/v2/guides/reference/workflow-nodes). |
| **Settings** | **Automatically enable newly activated connections**: enrol future activations in this workflow. |

## Use a workflow

<CodeGroup>
  ```text OIDC theme={null}
  https://connect.hopae.com/v2/auth?client_id=APP_ID&response_type=code&scope=openid%20hopae&redirect_uri=...&workflow_id=wf_01J8XJ4Q2R7TPX9K
  ```

  ```bash REST theme={null}
  curl -X POST "https://api.hopae.com/connect/v2/verifications" \
    -u "APP_ID:APP_SECRET" \
    -H "Content-Type: application/json" \
    -d '{"connectionId": "smart-id", "workflowId": "wf_01J8XJ4Q2R7TPX9K"}'
  ```
</CodeGroup>

`GET /connections?workflowId=…` shows which connections a workflow enables.

## Try it without code

The **verification link** at the top of the editor opens the hosted flow for this workflow. Open it or copy it. Its settings let you choose the redirect URI and whether to show the intro page.

<Note>
  Changes to a production app's workflow apply to live traffic as soon as you save. See [Apps & Environments](/v2/guides/concepts/apps#saving-changes).
</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.