Requirements
Before you set up the credential, make sure you have an active respond.io account and an API access token from your account settings ready.[3]
Get your respond.io credentials
- Access TokenpasswordRequired
Your API access token. Generate it in Settings -> Integrations - API.
[1]
Connect respond.io in WEXTL
- Log in to your WEXTL account, add the respond.io node module to your workflow, and click Create new credential.
- Optional: In the Credential name field, enter a name for the credential.
- Enter the authentication credentials you copied from your respond.io account, or follow the on-screen instructions to create the credential.
- If prompted, authenticate your account and confirm access.
- If you want to make changes to your credential in the future, follow the steps in Manage credentials →
Notes
Credentials are org-scoped; share them with teammates from the Credentials picker on any of its nodes.For detailed information on connecting an application, see Connect an application →
respond.io node modules
The list below is a reference of every respond.io node module the integration supports. You will be able to pick any of them on the workflow canvas while building automations.
Each respond.io node module below opens to reveal its input parameters, outputs, and connection requirements.
Output fields[3]
| Field | Type |
|---|---|
ID | number |
Name | text |
Source | text |
Created At | date |
Output fields[3]
| Field | Type |
|---|---|
ID | number |
Name | text |
Source | text |
Meta | object |
Last Message Time | number |
Last Incoming Message Time | number |
Created At | date |
Output fields[3]
| Field | Type |
|---|---|
ID | number |
First Name | text |
Last Name | text |
Phone | text |
Email | |
Language | text |
Profile Pic | url |
Country Code | text |
Custom Fields | array |
Name | text |
Value | text |
Status | text |
Tags | array |
Tag | text |
Assignee | object |
ID | number |
First Name | text |
Last Name | text |
Email | |
Lifecycle | text |
Created At | date |
Is Blocked | boolean |
Input fields[3]
| Field | Type |
|---|---|
ContactRequired | choice |
Output fields[3]
| Field | Type |
|---|---|
ID | number |
First Name | text |
Last Name | text |
Phone | text |
Email | |
Language | text |
Profile Pic | url |
Country Code | text |
Custom Fields | array |
Name | text |
Value | text |
Status | text |
Tags | array |
Tag | text |
Assignee | object |
ID | number |
First Name | text |
Last Name | text |
Email | |
Lifecycle | text |
Created At | date |
Is Blocked | boolean |
Input fields[3]
| Field | Type |
|---|---|
ContactRequired | choice |
Output fields[3]
| Field | Type |
|---|---|
Message ID | number |
Channel Message ID | text |
Contact ID | number |
Channel ID | number |
Traffic | text |
Message | object |
Type | text |
Text | text |
Status | array |
Value | text |
Timestamp | number |
Message | text |
Sender | object |
Source | text |
User ID | text |
Team ID | text |
Workflow ID | text |
Broadcast History ID | text |
Input fields[3]
| Field | Type |
|---|---|
Search | text |
Filter | object |
AND | array |
OR | array |
Timezone | time |
Limit | number |
Output fields[3]
| Field | Type |
|---|---|
ID | number |
First Name | text |
Last Name | text |
Phone | text |
Email | |
Language | text |
Profile Pic | url |
Country Code | text |
Custom Fields | array |
Name | text |
Value | text |
Status | text |
Tags | array |
Tag | text |
Assignee | object |
ID | number |
First Name | text |
Last Name | text |
Email | |
Lifecycle | text |
Created At | date |
Is Blocked | boolean |
Input fields[3]
| Field | Type |
|---|---|
ContactRequired | choice |
Limit | number |
Output fields[3]
| Field | Type |
|---|---|
Message ID | number |
Channel Message ID | text |
Contact ID | number |
Channel ID | number |
Traffic | text |
Message | object |
Type | text |
Text | text |
Status | array |
Value | text |
Timestamp | number |
Message | text |
Sender | object |
Source | text |
User ID | text |
Team ID | text |
Workflow ID | text |
Broadcast History ID | text |
Input fields[3]
| Field | Type |
|---|---|
IdentifierRequired | text |
First NameRequired | text |
Last Name | text |
Phone | text |
Email | |
Language | text |
Profile Pic | url |
Country Code | text |
Custom Fields | array |
NameRequired | text |
Value | text |
Input fields[3]
| Field | Type |
|---|---|
NameRequired | text |
Input fields[3]
| Field | Type |
|---|---|
ContactRequired | choice |
Lifecycle StageRequired | text |
Templates
Look for respond.io templates in the WEXTL template library.
Browse templates →Explore alternative apps
- AWS SQS[2]Send, receive, and manage messages on Amazon SQS queues.
- AWS SESSend transactional email and manage Amazon SES identities, templates, contacts, suppressions, and configuration sets.
- BatchDialerCloud predictive dialer for sales and collections teams with contacts and campaigns.
- Bland AIAI phone-calling platform that places and handles automated voice conversations at scale.
- Benchmark EmailEmail marketing platform for campaigns, lists, automations, and subscriber engagement.
References
- WEXTL® respond.io Source Code connector implementation.
- Our users use cases and automations.
- Official API Documentation for respond.io.
- WEXTL® visual workflow builder data.
Last updated: Oct 1, 2026 05:41