# Legacy Twitter direct messages

Review the legacy Twitter direct-message connection, its supported content and account subscriptions in INSIDE.

*Release 3.3 · admin, operator, visitor*

**Settings › General Settings › Integrations**

## What it is

**Twitter** is a legacy direct-message connection retained in INSIDE 3.3. It handles supported private messages and provider read updates for a connected account. Twitter is hidden from the integration **Add** popup in this release.

## Who uses it and why

- Operators review retained direct-message conversations and handle supported replies where the connection remains available.
- Administrators arrange account credentials and subscriptions with Powerfront.
- Visitors exchange private messages through the connected account.

## Where to find it

Open an existing **Twitter** conversation or find it in conversation history. Powerfront manages the retained **Twitter** connection under **Settings › General Settings › Integrations**.

## How it works

The account-activity subscription sends direct-message events to INSIDE. INSIDE verifies incoming notifications and associates the message with the customer and configured account. Messages sent by the connected account have separate handling so they are not treated as new customer messages.

You can send text, supported images and video. Shared offers, products and rich links are converted for the Twitter message format. INSIDE records the provider's message identity so later read notifications can update the matching message.

Powerfront can inspect and verify the account, register or validate the notification connection, and manage account-activity subscriptions. Both a working account connection and its subscriptions matter for inbound messages.

## Configure it

Ask Powerfront to review the retained account's **App Environment Name**, application credentials, access credentials and **Application Id**. New Twitter accounts are not offered in **Add**.

Powerfront can check the registered notification connection and subscribed account. Each configured account needs a distinct **Consumer API Key** and **Name**. An error about an existing account can indicate a duplicate key or name.

Confirm external account eligibility with Powerfront before planning activity around this legacy connection.

### Settings

| Setting | Where | Applies to | Default | Who can change it | What it does |
|---|---|---|---|---|---|
| Enable Twitter Integration | Settings › General Settings › Integrations | channel | On in the new-account editor; Off if absent from a saved account | Powerfront, on request | Enables the selected Twitter account connection. |

### Fields

| Field | Where | Required | What it is for |
|---|---|---|---|
| Name | Settings › General Settings › Integrations | Yes | Identifies the Twitter account in INSIDE and must be unique ignoring letter case. |
| App Environment Name | Settings › General Settings › Integrations | No | Selects the Twitter account-activity environment used by the connection. |
| Consumer API Key | Settings › General Settings › Integrations | Yes | Identifies the Twitter application and must differ from other configured Twitter application keys. |
| Consumer API Secret Key | Settings › General Settings › Integrations | No | Authenticates the application and verifies incoming notifications. |
| Access Token | Settings › General Settings › Integrations | No | Authorises access to the Twitter account. |
| Access Token Secret | Settings › General Settings › Integrations | No | Completes the account's access credentials. |
| Application Id | Settings › General Settings › Integrations | No | Identifies the sending application so its own message notifications can be recognised. |

## Limits and good to know

- Direct JPEG and PNG images and MP4 video must be strictly smaller than 5,000,000 bytes. GIF images must be strictly smaller than 15,000,000 bytes.
- A file exactly on either size boundary is rejected, even if the displayed error describes the boundary as inclusive.
- Unsupported direct file formats produce a sending error.
- Typing indicators, outgoing reactions, location requests and authentication requests are unsupported.
- This article covers private direct messages. Public-mention notifications are a separate legacy feature.

## Depends on and works with

### This feature uses

- **Requires** [Messaging channel connections](CHN-001.md): Twitter messaging needs a connected business account and its authorisation.
- **Requires** [Messaging conversations](CHN-002.md): Direct-message conversations retain their account and customer identity.
- **Requires** [Webhooks and message status](CHN-003.md): Signed account-activity notifications bring messages and read updates into INSIDE.
- **Configured in** [Website, channel and subsite access](ADM-009.md): Website and channel access governs which conversations an operator can handle.
- **Works better with** [Message delivery and read receipts](CHAT-003.md): Matching provider read notifications can mark an outgoing message as read.
- **Works better with** [Attachments in conversations](CHAT-018.md): Supported images and video can be exchanged in direct messages.
- **Related** [Conversation history and search](CHAT-024.md): History lets operators review retained messages even when the legacy connection is unavailable.

### Used by

- **Configures** [Webhooks and message status](CHN-003.md): Twitter account credentials and subscriptions control signed incoming notifications.

## FAQ and troubleshooting

### Why can I read old messages but receive no new ones?

Retained history does not depend on a working current provider connection. Ask Powerfront to check credentials, external account eligibility and the account-activity subscription.

### Why did an image or video fail to send?

Check both its type and its size. The direct upload limits are strict, so files exactly at the stated byte boundaries are too large.

### Why don't typing indicators appear?

The Twitter connection does not provide working typing indicators in this release.

### Can Powerfront add a Twitter account?

The integration is hidden from that popup in INSIDE 3.3. Ask Powerfront about the existing connection you need to review.