> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/integrations/identity-verification/sailpoint-identity-verification-for-workflows/1kosmos-workflow-identity-verification.md).

# 1Kosmos Workflow: Identity Verification

After the user clicks the verification link in the email from SailPoint, they are redirected to the 1Kosmos platform to complete the Identity Verification process. Once the user completes their identity verification the 1Kosmos workflow invokes a SailPoint endpoint.&#x20;

The 1Kosmos workflow is built in 1Kosmos's own workflow builder. It's what actually runs when the user clicks their verification link, and it's responsible for calling back to SailPoint Workflow 2 when it's done. &#x20;

#### Configure the Verification Flow&#x20;

The verification flow defines what "verified" means for your organization, for example, which claims to check (name, date of birth), how strictly they must match (exact vs. fuzzy), and how long a session stays valid before expiring. During verification, 1Kosmos compares the claims sent by SailPoint against the data extracted from the user's identity document using this configuration. For setup instructions, see [Configuring Verification Flows ](/identity-verification/configurations.md)in the 1Kosmos documentation. Your 1Kosmos representative can help you determine the right settings for your use case. &#x20;

#### Configure the Workflow Steps&#x20;

Build the sequence of verification steps the user goes through, for example: scan ID, take a selfie, liveness check, using the verification flow to determine what's being checked at each step. Make a note of the workflow access code that is generated when the workflow is created. This is the workflowId referenced in Sailpoint Workflow 1. For setup instructions, see [Workflow Builder ](https://docs.1kosmos.com/workflow-builder/)in the 1Kosmos documentation.&#x20;

#### Configure the Callback to SailPoint&#x20;

As the final step in the 1Kosmos workflow, add a step that calls the SailPoint external trigger endpoint, passing the workflow instance ID. This is what starts Workflow 2 in SailPoint.&#x20;

`POST https://{tenant}.api.{domain}.com/beta/workflows/execute/external/{external_trigger_id}`&#x20;

`Authorization: Bearer {external_trigger_access_token}`&#x20;

`Content-Type: application/json` &#x20;

`{`&#x20;

&#x20;   `"wfInstanceId": "{wfInstanceId}"`&#x20;

`}`&#x20;

&#x20;

Authenticate this call using the OAuth 2.0 client\_credentials grant, with the client ID and client secret from the External Trigger step you configured in Sailpoint Workflow 2.&#x20;

&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.1kosmos.com/integrations/identity-verification/sailpoint-identity-verification-for-workflows/1kosmos-workflow-identity-verification.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
