Requirements
To use Autocalls AI on WEXTL you need an active account and an API access token from your account settings.[3]
Get your Autocalls AI credentials
- API KeypasswordRequired
Log in to your Autocalls account at https://app.autocalls.ai. Navigate to the “API Keys” page. Click on the “Create new API Key” button.
[1]
Connect Autocalls AI in WEXTL
- Log in to your WEXTL account, add the Autocalls AI node module to your workflow, and click Create new credential.Instant triggers use webhooks — click Create a webhook first when adding one, then create the credential.
- Optional: In the Credential name field, enter a name for the credential.
- Enter the authentication credentials you copied from your Autocalls AI 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 →
Autocalls AI node modules
The list below is a reference of every Autocalls AI node module the integration supports. You will be able to pick any of them on the workflow canvas while building automations.
Open any Autocalls AI node module below to inspect its input parameters, outputs, and connection requirements.
Watch CallsTrigger
Output fields[3]
| Field | Type |
|---|---|
| ID | number |
| Assistant name | text |
| Campaign name | text |
| Type | text |
| Duration | number |
| Assistant phone number | text |
| Client phone number | text |
| Status | text |
| Transcript | text |
| Variables | object |
| Customer name | text |
| Interest level | text |
| Follow up date | text |
| Evaluation | object |
| Sentiment | text |
| Outcome | text |
| Score | number |
| Webhook response | object |
| Status | text |
| Data | object |
| Carrier cost | number |
| Total cost | number |
| Answered by | text |
| Recording URL | text |
| Created at | date |
| Updated at | date |
Watch Inbound EventsTrigger
No fields documented.
Watch LeadsTrigger
Output fields[3]
| Field | Type |
|---|---|
| ID | number |
| Campaign ID | number |
| Phone number | text |
| Variables | object |
| Customer name | text |
| text | |
| Status | text |
| Created at | text |
| Updated at | text |
| Campaign | object |
| ID | number |
| Name | text |
| Secondary contacts | array |
List LeadsSearch
Search CallsSearch
Input fields[3]
| Field | Type |
|---|---|
| Status | choice |
| Type | choice |
| Phone Number | text |
| Assistant ID | choice |
| Campaign ID | number |
| Date From | date |
| Date To | date |
| Limit | number |
Output fields[3]
| Field | Type |
|---|---|
| ID | number |
| Assistant name | text |
| Campaign name | text |
| Type | text |
| Duration | number |
| Assistant phone number | text |
| Client phone number | text |
| Status | text |
| Transcript | text |
| Variables | object |
| Customer name | text |
| Interest level | text |
| Follow up date | text |
| Evaluation | object |
| Sentiment | text |
| Outcome | text |
| Score | number |
| Webhook response | object |
| Status | text |
| Data | object |
| Carrier cost | number |
| Total cost | number |
| Answered by | text |
| Recording URL | text |
| Created at | date |
| Updated at | date |
Create a LeadAction
Input fields[3]
| Field | Type |
|---|---|
Phone NumberRequired | text |
Campaign IDRequired | choice |
| Variables | object |
| Customer Name | text |
| Allow Duplicate | boolean |
| Secondary Contacts | array |
Output fields[3]
| Field | Type |
|---|---|
| Message | text |
| Data | object |
| ID | number |
| Campaign ID | number |
| Phone number | text |
| Variables | object |
| Status | text |
| Created at | text |
| Updated at | text |
| Campaign | object |
| Secondary contacts | array |
Delete a CallAction
Input fields[3]
| Field | Type |
|---|---|
Call IDRequired | choice |
Delete a LeadAction
Input fields[3]
| Field | Type |
|---|---|
Call IDRequired | choice |
Make a Phone CallAction
Make an API Calluniversal
Send an SMSAction
Update a LeadAction
Input fields[3]
| Field | Type |
|---|---|
Lead IDRequired | choice |
| Phone Number | text |
| Campaign ID | choice |
| Status | choice |
| Variables | array |
| Key Name | text |
| Value | text |
Output fields[3]
| Field | Type |
|---|---|
| Message | text |
| Data | object |
| ID | number |
| Campaign ID | number |
| Phone number | text |
| Variables | object |
| Status | text |
| Created at | text |
| Updated at | text |
| Campaign | object |
| Secondary contacts | array |
Templates
Look for Autocalls AI templates in the WEXTL template library.
Browse templates →Explore alternative apps
- Bandwidth[2]Enterprise communications APIs for voice, messaging, and phone number services.
- AcumbamailEmail marketing platform for campaigns, lists, and subscriber automation.
- ButtondownIndie newsletter platform for writing, sending, and managing email lists.
- CallTrackingMetricsCall tracking for businesses, with numbers, texts, and routing.
- BatchDialerCloud predictive dialer for sales and collections teams with contacts and campaigns.
References
- WEXTL® Autocalls AI Source Code connector implementation.
- Our users use cases and automations.
- Official API Documentation for Autocalls AI.
- WEXTL® visual workflow builder data.
Last updated: Jul 23, 2026 22:38