# Respond.io AI integration on Definable

> AI-powered customer conversation management software.

## What this connects

AI-powered customer conversation management software.

Vendor: https://respond.io

## Tools available

**7** tools available. First 7:

- `RESPOND_IO_CREATE_COMMENT` — Add internal comment to conversation — Tool to add a comment (internal note) to a contact's conversation. Use after verifying the contact identifier.
- `RESPOND_IO_CREATE_CONTACT` — 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.
- `RESPOND_IO_CREATE_SPACE_TAG` — 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.
- `RESPOND_IO_GET_MESSAGE` — Get Message — Tool to retrieve a specific message. Use when you need the details of a message sent to or received from a contact.
- `RESPOND_IO_LIST_CHANNELS` — 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.
- `RESPOND_IO_LIST_USERS` — 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.
- `RESPOND_IO_UPDATE_SPACE_TAG` — 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.

## Auth

Auth schemes: `API_KEY`.

## How agents use Respond.io

Inside a Definable workflow, Respond.io is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Respond.io** — the Researcher (GPT-5.5) pulls context from Respond.io (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Respond.io** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Respond.io (create record, post message, draft email).
- **Designer / Engineer → Distributor → Respond.io** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Respond.io (attach file, open PR comment, post status).

The Verifier checks every Respond.io call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- customer support — https://definable.ai/apps/category/customer-support/
- team chat — https://definable.ai/apps/category/team-chat/

## Related

- HTML page: https://definable.ai/apps/respond_io/
- Same category (customer support): https://definable.ai/apps/category/customer-support/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt