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

# Attentive Webhook Setup Guide

> Configure Attentive to deliver events to StackOne.

## Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See [Getting Started](https://docs.stackone.com/connectors/attentive.md#getting-started) on the Attentive connector page.

## Copy your Native Webhook URL

Attentive webhooks are added manually in Attentive. StackOne does not create them for you. Start by copying the URL Attentive will send events to.

<ul>
  <li>Open the linked account in StackOne.</li>
  <li>Copy the value from **Native Webhook URL**. It is available once the account is connected and is unique to that account.</li>
</ul>

## Adding the webhook in Attentive

Register the Native Webhook URL as a Universal webhook on your Attentive custom app and choose which events it sends.

**1. Sign in to Attentive**

Sign in to your [Attentive account](https://ui.attentivemobile.com).

<ul>
  <li>Navigate to **Setup** > **Marketplace**.</li>
</ul>

![Attentive left sidebar with Setup expanded and Marketplace highlighted](https://mintcdn.com/stackone-60/Jp3CPX_GV8vDON_3/connectors/attentive/images/events-open-marketplace.png?fit=max\&auto=format\&n=Jp3CPX_GV8vDON_3\&q=85\&s=523a647883c06420e507e5d6651a6d15)

**2. Open your custom apps**

On the **App marketplace** page, click the **Built by you** tab.

![App marketplace page with the Built by you tab highlighted](https://mintcdn.com/stackone-60/Jp3CPX_GV8vDON_3/connectors/attentive/images/events-built-by-you.png?fit=max\&auto=format\&n=Jp3CPX_GV8vDON_3\&q=85\&s=eff4a05725d3c35136b943d411d8d779)

**3. Select the custom app**

Click the custom app that holds the API key used by this StackOne account.

![Built by you tab with the custom app card highlighted](https://mintcdn.com/stackone-60/Jp3CPX_GV8vDON_3/connectors/attentive/images/events-select-app.png?fit=max\&auto=format\&n=Jp3CPX_GV8vDON_3\&q=85\&s=986edd9e43ce8d41a6cd13de9ebb5e7f)

**4. Open the Webhooks tab**

On the app page, click the **Webhooks** tab.

![Custom app page with the Webhooks tab highlighted](https://mintcdn.com/stackone-60/Jp3CPX_GV8vDON_3/connectors/attentive/images/events-webhooks-tab.png?fit=max\&auto=format\&n=Jp3CPX_GV8vDON_3\&q=85\&s=76d6d7e43aa1c198e2539469d2f7be21)

**5. Enable the Universal webhook**

Turn on **Event webhook status** so the toggle shows **Enabled**.

<ul>
  <li>Under **Subscribe to event notifications**, select **Universal webhook**.</li>
  <li>Paste the Native Webhook URL into **HTTP Post URL**.</li>
</ul>

![Webhooks tab with the Enabled toggle, the Universal webhook option and the HTTP Post URL field highlighted](https://mintcdn.com/stackone-60/Jp3CPX_GV8vDON_3/connectors/attentive/images/events-configure-webhook.png?fit=max\&auto=format\&n=Jp3CPX_GV8vDON_3\&q=85\&s=bb62ea59a50fa2fbe1a60d05db2c1c31)

**6. Select the events**

Open **Select events to post to URL** and tick each event you enabled in StackOne.

<ul>
  <li>Events are grouped by channel, such as **EMAIL** and **SMS**.</li>
  <li>Attentive recommends that each event type is selected in only one app per company, to avoid duplicate deliveries.</li>
</ul>

![Select events to post to URL dropdown open with the email and SMS events ticked](https://mintcdn.com/stackone-60/Jp3CPX_GV8vDON_3/connectors/attentive/images/events-select-events.png?fit=max\&auto=format\&n=Jp3CPX_GV8vDON_3\&q=85\&s=db2a9d8be35109efb2e184e08e5830d1)

**7. Save the webhook**

Click **Save**. Attentive starts sending the selected events to StackOne.

![Webhooks tab with the selected events listed and the Save button highlighted](https://mintcdn.com/stackone-60/Jp3CPX_GV8vDON_3/connectors/attentive/images/events-save.png?fit=max\&auto=format\&n=Jp3CPX_GV8vDON_3\&q=85\&s=afa5afef2a22b943bc3ba6bba390aaac)

## Available webhook events

The following Attentive events can be enabled. Only events that are enabled in StackOne and selected in the Attentive webhook are delivered.

**1. Subscription events**

Events related to SMS and email opt-ins and opt-outs.

<ul>
  <li>**SMS Subscribed** (`sms.subscribed`) — Fired when a user opts in to SMS marketing or transactional messages</li>
  <li>**SMS Unsubscribed** (`sms.unsubscribed`) — Fired when a user opts out of SMS</li>
  <li>**Email Subscribed** (`email.subscribed`) — Fired when a user opts in to email</li>
  <li>**Email Unsubscribed** (`email.unsubscribed`) — Fired when a user opts out of email</li>
</ul>

**2. Message events**

Events related to messages Attentive sends and how subscribers respond.

<ul>
  <li>**SMS Sent** (`sms.sent`) — Fired when Attentive sends an SMS to a subscriber</li>
  <li>**SMS Link Clicked** (`sms.message_link_click`) — Fired when a subscriber clicks a link in an SMS</li>
  <li>**SMS Inbound Message** (`sms.inbound_message`) — Fired when a subscriber replies to an SMS</li>
  <li>**Email Sent** (`email.sent`) — Fired when Attentive sends an email to a subscriber</li>
  <li>**Email Opened** (`email.opened`) — Fired when a subscriber opens an email</li>
  <li>**Email Link Clicked** (`email.message_link_click`) — Fired when a subscriber clicks a link in an email</li>
</ul>

**3. Custom attribute events**

Events related to subscriber custom attributes.

<ul>
  <li>**Custom Attribute Set** (`custom_attribute.set`) — Fired when a custom attribute is added or updated for a subscriber</li>
</ul>

**4. Active check**

Acknowledges any Attentive delivery without a recognized event type, so Attentive does not retry it.

<ul>
  <li>**Active Check** (`active_check`) — Returns a 200 response for unrecognized deliveries</li>
</ul>

## Delivery format

Details of how Attentive delivers events to StackOne.

**1. One event per request**

Each request carries a single JSON event with its `type`, a `timestamp` in epoch milliseconds, the `company`, the `subscriber` and an event-specific object. Email events are only sent when the Attentive email product is enabled for your company.

## Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.


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