# Blend-AI (Actions) Destination

## Destination Info

* Accepts [Page](/docs/segment/connections/spec/page), [Alias](/docs/segment/connections/spec/alias), [Group](/docs/segment/connections/spec/group), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls.
* Refer to it as **Blend Ai** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object)
* This integration is **partner owned.** Please reach out to the partner's support for any issues.
* This destination is **Beta.**

[Blend-AI](https://blend-ai.com/) identifies the most valuable product interaction in your product data and cross references it with new incoming leads.

Blend-AI maintains this destination. For any issues with the destination, [contact their Support team](mailto:support@blnd.ai).

## Getting started

1. From the Segment web app, navigate to **Connections > Catalog**, then select the **Destinations** tab in the catalog.
2. Search for *Blend-AI* and select it.
3. Click **Configure Blend-AI**.
4. Select an existing Source to connect to Blend-AI (Actions).
5. Give the destination a name that is recognizable and detailed.
6. Paste your Blend's API key (found on Blend's integration page under the Segment section).
7. Enable the destination by changing the bottom **Enable Destination** toggle to active.
8. Click **Save Changes**.

## Destination Settings

| Field   | Description                                | Required | Type     |
| ------- | ------------------------------------------ | -------- | -------- |
| API Key | Blend API key - found on integration page. | Yes      | password |

## Available Presets

Blend Ai has the following presets

| Preset Name        | Trigger                                                                                      | Default Action |
| ------------------ | -------------------------------------------------------------------------------------------- | -------------- |
| Send Data to Blend | Event type = "identify", Event  type = "page", Event  type = "screen", Event  type = "track" | Track events   |

## Available Actions

Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following Blend Ai-supported actions:

> \[!NOTE]
>
> Individual destination instances have support a maximum of 50 mappings.

* [\[Deprecated\] Send Data](#deprecated-send-data)
* [Track events](#track-events)

### \[Deprecated] Send Data

\[Deprecated] Send data to Blend AI for product usage insights

\[Deprecated] Send Data is a **Cloud** action. The default Trigger is `type = "identify" or type = "page" or type = "screen" or type = "track"`

This action does not have any fields.

### Track events

Send data to Blend AI for product usage insights

Track events is a **Cloud** action. The default Trigger is `type = "identify" or type = "page" or type = "screen" or type = "track"`

| Field            | Description                       | Required | Type   |
| ---------------- | --------------------------------- | -------- | ------ |
| Event Name       | The name of event, page or screen | No       | STRING |
| Event Type       | The type of event                 | No       | STRING |
| Event Properties | Properties of the event           | No       | OBJECT |
| User Traits      | User profile details / traits     | No       | OBJECT |
| Identifiers      | User identifiers                  | No       | OBJECT |