Skip to content
background-image background-image

Respond.io - List Contact Channels

[ | version 3.0]

Connector

The connector is permitted for use of the platform background agent.

Connector processing type: Row by row!

Respond.io is a platform designed for managing and automating customer messages and communications across various channels. This service enables businesses to centralize and manage messages from different messaging applications, such as WhatsApp, Facebook Messenger, Viber, Telegram, LINE, and others, in one place.

Informations about settings for developers and API documentation for Respond.io found here.

List Contact Channels allows you to list all connected channel of a specific contact.


Configuration

Respond.io - Connection

Token

Uses to authorize and authenticate connections. More information about where to find the token can be found here.

Respond.io - List Contact Channels Settings

Error behavior

The available values are:

  • Fail and return response: The connector fails at the specified line but generates output with error details.

  • Fail without response: The connector fails - the error will be displayed only in the log.

  • Do not fail and return response: The connector does not fail but generates output records that may be marked with an error and detailed information.


Input & Output Schema

Input

Respond.io - List Contact Channels Request (ver. 1.0.0)

Column Data type Allow null Description
Identifier String No Identifier of the contact (e.g. id:123, email:abdc@gmail.com, phone:+60121233112)

Output

Respond.io - List Contact Channels Response (ver. 1.0.0)

Column Data type Allow null Description
StatusCode Integer No Response HTTP Code
Message String Yes Error text
Channels Respond.io - List Contact Channels Item v1.0.0 Yes Complex schema

Status Code

  • 200 Success
  • 400 Bad request
  • 500 Server error

Respond.io - List Contact Channels Item (ver. 1.0.0)

Column Data type Allow null Description
ID Integer Yes ID of the channel
Name String Yes Channel name
Source String Yes Type of the channel (e.g. Telegram)
Meta JSON Yes Additional details of the contact as provided by the channel
LastMessageTime DateTime Yes Unix timestamp of the last message received/sent
LastIncomingMessageTime DateTime Yes Unix timestamp of the last incoming message
CreatedAt DateTime Yes Unix timestamp of the channel creation

Release notes

3.0.2

  • First release.