> 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/sailpoint-workflows/workflow-1-enroll-a-new-identity-for-verification.md).

# Workflow 1: Enroll a New Identity for Verification

This workflow starts a verification session in 1Kosmos, creates a matching account in the source, and emails the user a link to begin verification. 

#### Steps

| # | Step                             | SailPoint Step Type |
| - | -------------------------------- | ------------------- |
| 1 | Identity Created                 | Trigger             |
| 2 | Create 1Kosmos Workflow Instance | HTTP Request        |
| 3 | Create Account                   | Create Account      |
| 4 | Send Verification Email          | Send Email          |

 

#### Identity Created 

Set the workflow trigger to Identity Created. This fires whenever a new identity is created in SailPoint from any of your sources, and makes that identity's attributes (email, first name, last name, identity ID) available to the rest of the workflow. 

#### Create 1Kosmos Workflow Instance 

Add an HTTP Request step that calls the 1Kosmos Create Workflow Instance API to start a new IDV session for the user, using the trigger data from Step 1.  

`POST https://{1kosmos_host}/workflowapi/workflow_instance/tenant/{tenant_id}/community/{community_id}/create` 

`Accept: application/json` 

`Content-Type: application/json` 

`keyId: {keyId}` 

`keySecret: {keySecret}` 

`license: {license}` 

`requestfromswagger: true`  

`{` 

    `"data": {` 

        `"metaData": {` 

            `"email": "{{$.trigger.attributes.email}}",` 

            `"firstName": "{{$.trigger.attributes.firstname}}",` 

            `"identityId": "{{$.trigger.identity.id}}",` 

            `"lastName": "{{$.trigger.attributes.lastname}}"` 

        `},` 

        `"workflowId": "{your 1Kosmos workflowId}"` 

    `}` 

`}` 

#### Response 

`{` 

    `"data": {` 

        `"wfInstanceId": "wfi-abc123-def456-ghi789",` 

        `"wfInstanceUrl": "https://{1kosmos_host}/workflow/wf_instance/wfi-abc123-def456-ghi789"` 

    `}` 

`}` 

 

#### Create Account 

Add a Create Account step in the workflow. This will create an account in the source using the trigger data from Step 1 and the wfInstanceId returned in Step 2. 

`POST https://{tenant}.api.{domain}.com/v3/accounts` 

`Authorization: Bearer {access_token}` 

`Content-Type: application/json` 

`{` 

    `"attributes": {` 

        `"createDate": "{{$.now()}}",` 

        `"email": "{{$.trigger.attributes.email}}",` 

        `"lastName": "{{$.trigger.attributes.lastname}}",` 

        `"firstName": "{{$.trigger.attributes.firstname}}",` 

        `"id": "{{$.hTTPRequest.body.data.wfInstanceId}}",` 

        `"idvStatus": "PENDING",` 

        `"name": "{{$.trigger.attributes.email}}",` 

        `"sourceId": "{your source ID}"` 

    `},` 

    `"identityId": "{{$.trigger.identity.id}}"` 

`}` 

The id value you set here becomes the account's nativeIdentity in SailPoint (SailPoint separately generates its own internal account ID). Workflow 2 uses nativeIdentity as the key to find this account again, so it must match the wfInstanceId from Step 2. 

#### Send Verification Email 

Add a Send Email step to notify the user: 

* Recipient: identity.attributes.email 
* Link: the wfInstanceUrl returned in Step 2 


---

# 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/sailpoint-workflows/workflow-1-enroll-a-new-identity-for-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.