> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/stytch.md).

# Stytch

Manage users and authenticate magic links, OTPs, and sessions with Stytch.

## Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector | Authentication |
| --------- | -------------- |
| Stytch    | Credentials    |

### Stytch

Connect to Stytch with project credentials to manage users and authenticate magic links, OTPs, and sessions.

#### Set up in Stytch

1. Prepare the Stytch account or service that the workflow will access. Grant access to the required resources and operations.
2. **Project ID:** Your Stytch project ID from the API Keys page.

#### Set up in StackAI

1. Open **Settings → Connections**, add a connection, and select **Stytch**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field | Required | What to enter                                                                                         |
| ------------- | -------- | ----------------------------------------------------------------------------------------------------- |
| Project ID    | Yes      | Your Stytch project ID from the API Keys page. [Provider instructions](https://stytch.com/dashboard). |
| Secret        | Yes      | The secret for the same Stytch project ID. [Provider instructions](https://stytch.com/dashboard).     |

### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

## Use an action

1. Add the required **Stytch** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

## Actions

### Create user

Create a Stytch user with an email address.

#### Inputs

| Field             | Type    | Required | Description                                                                 |
| ----------------- | ------- | -------- | --------------------------------------------------------------------------- |
| Email             | string  | Yes      | The new user's email address.                                               |
| First name        | string  | No       | The user's optional first name.                                             |
| Last name         | string  | No       | The user's optional last name.                                              |
| External ID       | string  | No       | An optional ID from your own system.                                        |
| Create as pending | boolean | No       | Create the user in pending status instead of active status. Default: false. |

#### Outputs

| Field    | Type   | Description                            |
| -------- | ------ | -------------------------------------- |
| User ID  | string | The created user's Stytch ID.          |
| Email ID | string | The created email address's Stytch ID. |
| Status   | string | The user's active or pending status.   |

### Send magic link email

Send a Stytch login-or-create magic link by email.

#### Inputs

| Field                      | Type            | Required | Description                                                                                                         |
| -------------------------- | --------------- | -------- | ------------------------------------------------------------------------------------------------------------------- |
| Email                      | string          | Yes      | The recipient's email address.                                                                                      |
| Login redirect URL         | string          | No       | Where existing users land after authenticating.                                                                     |
| Signup redirect URL        | string          | No       | Where newly created users land after authenticating.                                                                |
| Show advanced fields       | boolean         | No       | Show expiration, locale, and pending-user options. Default: false.                                                  |
| Login expiration minutes   | integer         | No       | How long login links remain valid.                                                                                  |
| Signup expiration minutes  | integer         | No       | How long signup links remain valid.                                                                                 |
| Locale                     | select (string) | No       | Language for Stytch's email template. Available values: English, Spanish, Portuguese (Brazil), French. Default: en. |
| Create new user as pending | boolean         | No       | Create a new recipient in pending status. Default: false.                                                           |

#### Outputs

| Field        | Type    | Description                                  |
| ------------ | ------- | -------------------------------------------- |
| User ID      | string  | The recipient's Stytch user ID.              |
| Email ID     | string  | The recipient email's Stytch ID.             |
| User created | boolean | Whether this send created a new Stytch user. |

### Verify OTP code

Verify a Stytch OTP code and create a session.

#### Inputs

| Field                      | Type    | Required | Description                                                          |
| -------------------------- | ------- | -------- | -------------------------------------------------------------------- |
| Method ID                  | string  | Yes      | The method ID returned when the OTP was sent.                        |
| OTP code                   | secret  | Yes      | The one-time code received by the user.                              |
| Session duration (minutes) | integer | No       | How long the authenticated session should remain valid. Default: 60. |

#### Outputs

| Field         | Type   | Description                                 |
| ------------- | ------ | ------------------------------------------- |
| User ID       | string | The authenticated Stytch user ID.           |
| Method ID     | string | The authenticated email or phone method ID. |
| Session token | secret | The opaque token for the new session.       |
| Session ID    | string | The newly created Stytch session ID.        |

### Authenticate session

Authenticate a Stytch session token and optionally extend it.

#### Inputs

| Field                       | Type    | Required | Description                                              |
| --------------------------- | ------- | -------- | -------------------------------------------------------- |
| Session token               | secret  | Yes      | The opaque Stytch session token to authenticate.         |
| Extend session to (minutes) | integer | No       | Optionally extend the session from its last access time. |

#### Outputs

| Field      | Type     | Description                             |
| ---------- | -------- | --------------------------------------- |
| User ID    | string   | The user associated with the session.   |
| Session ID | string   | The authenticated Stytch session ID.    |
| Expires at | datetime | When the authenticated session expires. |

### Revoke session

Immediately revoke a Stytch session by ID.

#### Inputs

| Field      | Type   | Required | Description                                  |
| ---------- | ------ | -------- | -------------------------------------------- |
| Session ID | string | Yes      | The Stytch session ID to revoke immediately. |

#### Outputs

| Field       | Type    | Description                         |
| ----------- | ------- | ----------------------------------- |
| Request ID  | string  | Stytch's request identifier.        |
| Status code | integer | The HTTP status returned by Stytch. |

## Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# 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.stackai.com/integrations/catalog/stytch.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.
