# Respond.io

AI-powered customer conversation management software.

- **Category:** customer support
- **Auth:** API_KEY
- **Composio Managed App Available?** N/A
- **Tools:** 7
- **Triggers:** 0
- **Slug:** `RESPOND_IO`
- **Version:** 20260227_00

## Tools

### Add internal comment to conversation

**Slug:** `RESPOND_IO_CREATE_COMMENT`

Tool to add a comment (internal note) to a contact's conversation. Use after verifying the contact identifier.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `text` | string | Yes | Content of the comment (internal note), up to 1000 characters. You can mention other users using `{{@user.ID}}`. |
| `identifier` | string | Yes | Identifier of the contact; either 'id:<contact_id>', 'email:<email>' or 'phone:<E.164_phone>'. Example: 'id:123', 'email:abdc@gmail.com', 'phone:+60121233112' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Contact

**Slug:** `RESPOND_IO_CREATE_CONTACT`

Creates a new contact in the respond.io workspace with the specified details. The contact is identified by email, phone number, or contact ID. Supports adding profile information, language preferences, and custom fields that have been pre-configured in the workspace.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `email` | string | No | Email address of the contact |
| `phone` | string | No | Phone number of the contact including country code |
| `language` | string | No | ISO 639-1 two-letter language code (e.g., 'en' for English, 'es' for Spanish) |
| `lastName` | string | No | Last name of the contact |
| `firstName` | string | Yes | First name of the contact |
| `identifier` | string | Yes | Unique identifier for the contact in one of these formats: 'email:<email_address>' (e.g., 'email:john@example.com'), 'phone:<phone_number>' (e.g., 'phone:+60121233112' with country code), or an existing contact ID |
| `profilePic` | string | No | URL of the contact's profile picture |
| `countryCode` | string | No | ISO 3166-1 alpha-2 two-letter country code (e.g., 'US' for United States, 'MY' for Malaysia) |
| `custom_fields` | array | No | List of custom fields for the contact. Note: Custom fields must already exist in the workspace before they can be assigned to a contact |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Space Tag

**Slug:** `RESPOND_IO_CREATE_SPACE_TAG`

Creates a new tag in the Respond.io workspace for organizing and categorizing contacts and conversations. Tags help with segmentation, filtering, and workflow automation. Each tag must have a unique name within the workspace.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | Yes | Name of the tag. Must be unique within the workspace. Cannot contain emojis or certain invalid characters. Supports spaces, letters, numbers, and common special characters like !@#$%. |
| `color_code` | string | No | (Optional) Hexadecimal color code for visual identification of the tag in the UI, e.g., '#FF5733'. Note: Currently the API may reject this parameter with validation errors. |
| `description` | string | No | (Optional) Brief text describing the tag's purpose or usage. Helps team members understand when to apply this tag. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Message

**Slug:** `RESPOND_IO_GET_MESSAGE`

Tool to retrieve a specific message. Use when you need the details of a message sent to or received from a contact.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `messageId` | integer | Yes | Unique ID of the message to retrieve. |
| `identifier` | string | Yes | Identifier of the contact, can be a phone number ('+60121233112'), email ('abdc@gmail.com'), or contact ID prefixed by 'id:' (e.g., 'id:123'). |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List channels

**Slug:** `RESPOND_IO_LIST_CHANNELS`

Tool to retrieve a list of channels connected to the workspace. Use when you need to enumerate all messaging channels with pagination support.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | integer | No | Number of items to return (page size). Default is 10, maximum 100. |
| `cursorId` | integer | No | Pointer to the channel ID from where the next batch of records should start. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List users

**Slug:** `RESPOND_IO_LIST_USERS`

Tool to retrieve a list of users in the workspace. Use when you need to fetch all workspace users for auditing or assignment.

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Space Tag

**Slug:** `RESPOND_IO_UPDATE_SPACE_TAG`

Updates an existing workspace tag by its current name. You can modify the tag's name, description, or emoji. Note: Color codes are not currently supported by the API and will be rejected if provided. At least one field besides currentName must be provided to update.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `name` | string | No | New name for the tag (if you want to rename it) |
| `emoji` | string | No | Emoji to associate with the tag (single emoji character) |
| `colorCode` | string | No | Hex color code for the tag (Note: Currently not supported by API and will return error if provided) |
| `currentName` | string | Yes | The current name of the tag you want to update (must match exactly) |
| `description` | string | No | New description for the tag (updates or sets the description) |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |