Connect CALL-E integrations

Verified

Place AI phone calls, read call results and transcripts, and run published goals, connected to WEXTL workflows and AI agents. Your workflows can send CALL-E results straight into the tools that act on them. Start with Watch Call Completed, then use Get a Call or Get a Goal to turn the output into a next step.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region
  • CALL-E
  • WEXTL
  • Sonix
  • Scrape Graph AI
  • Granola AI
  • Moonshot
  • Placid
  • Mureka AI
  • Tiliter
  • Docparser
  • DeepSeek
  • CustomGPT
  • Vapi
  • Alibaba Cloud (Qwen)
  • Jina AI
  • Lindo AI
  • Dust
  • OpenAI
  • Hedy AI
  • Minimax
  • Dappier

Supported triggers and actions for CALL-E integration

Triggers can detect changes in CALL-E and run actions that can create, search or modify data inside CALL-E automatically[3], exactly how you set them.

  • Watch Call Completed Starts the workflow the moment CALL-E delivers a finished call, whether it completed, failed or was canceled. It runs instantly through a webhook, so the address of this node is pasted into the call you create.
  • Get a Call Reads the saved state of one call by its Call ID, with the Status, Result and Transcript. Reading never dials, and the same call may be read repeatedly while its Result Status says pending.
  • Get a Goal Returns one goal from your account, including the schemas in its Published Run Spec. Look at them before Create a Goal Run to see which Variables a call expects.
  • Get a Goal Run Checks how a goal run is going, using the Goal Run ID from Create a Goal Run. It returns the Call Outcome, the Result and the Transcript. Run it again until the Result Status is no longer pending.
  • List Call Events Lists what happened during a call, from accepted through ringing and connected to completed, oldest first. A Starting Cursor continues a list you read earlier, and every event is one row you can map.
  • List Goals Shows the goals published in your CALL-E account, with the Title, Description, Status and Published Run Spec of each. Use Limit to cap how many are returned.
  • Cancel a Call Stops a call that has not been handed to the telephone provider yet. Once dialing has started the call cannot be hung up, and a call that already finished is returned unchanged.
  • Create a Call Places an AI phone call to a Phone number that carries out a Task and collects the answers described by your Result Fields. Add a Webhook URL to be notified when the call ends, and Metadata for your own labels.
  • Create a Goal Run Starts a call to a Phone number for one goal, filled in with Variables sent as text, numbers or Yes or No values. The call runs in the background, so use Get a Goal Run to read its Result later.
  • Make an API Call Makes an authorized free-form request to the CALL-E REST API with your saved credential.

How to integrate CALL-E in automation workflow?

CALL-E in three steps: start with "Watch Call Completed", connect one credential, then add your next step.

How CALL-E connects and integrates with WEXTL

Save and approve your credentials once. WEXTL® stores authorization information encrypted and reuses the authentication whenever CALL-E app is called in workflows. That allows your ai automations to run without your attention, per defined schedule[7]. See the integration guide[6] for a detailed list of fields that CALL-E supports.

Full CALL-E API documentation

The following table illustrates what fields CALL-E integration require during authorization flow inside our workflow builder[4].

Connect CALL-E

  • API Key*Text

    ••••••••

Demonstration of CALL-E connection step inside WEXTL Workflow Builder[4].
FieldTypeHelp
API KeyRequired
password

Create it in the dashboard under Account, API keys. Production keys start with iams_live_.

Connect CALL-E to popular apps on WEXTL

Enter a name of the other app you want to sync with CALL-E below. Click on selected app to explore integration options with CALL-E. If the app you search for is not available in WEXTL yet, you can use HTTP node[10] instead to integrate it directly.

Example automation with CALL-E integration

Select Watch Call Completed trigger from CALL-E - this will be a starting point in your automation. Whenever event happens in CALL-E, workflow will start[7] from Watch Call Completed node.

Search for Create a Call, connect it as the next step of integration sequence. You can use filters between Watch Call Completed and Create a Call, so only important data pass from Watch Call Completed to the next step. WEXTL gives you full control over the process of CALL-E automation. All parts of workflow are visible on the canvas[4].

CALL-E on WEXTL has 10 modules for combining ai automations. Explore CALL-E documentation for more.

  • CALL-EWatch Call Completed
  • SonixPerforms action

OR

  • SonixTriggers
  • CALL-ECreate a Call
Demonstration of how visual CALL-E automation[6] looks in WEXTL.

Frequently asked questions

Common questions about automating CALL-E in your workflows.

What triggers does CALL-E support?

CALL-E has 1 trigger, including "Watch Call Completed". Triggers are start points of the workflow, and automations may start from them.

What actions can I run in CALL-E?

Integration has 9 actions, including "Get a Call", "Get a Goal", and "Get a Goal Run", and more. Refer to our CALL-E Documentation for detailed inputs and outputs.

Do I need to write code to build automations?

No. The 9 CALL-E modules, like "Get a Call", are forms on the canvas: pick a field, map data from an earlier step. Code is optional[4].

Is the integration secure?

Yes. You fill in the CALL-E credential once. WEXTL encrypts it at rest, and only your team can use it.

How does WEXTL integrate with CALL-E?

Through the official CALL-E API: 9 modules, plus "Make an API Call" for any endpoint they don't cover[3].

Can I use webhooks with CALL-E?

Yes. "Watch Call Completed" is instant: CALL-E pushes each event, so there is no polling delay.

Why use WEXTL platform for CALL-E automation?

WEXTL is an AI-first visual canvas: describe the CALL-E flow in plain words and AI wires the nodes[4].

Automate CALL-E on WEXTL®

Claim your 3-day trial to build CALL-E integrations and access every WEXTL® feature.

Cancel anytime.

References

List of sources used to gather information about the CALL-E integration.

  1. CALL-E integration source code, module specs and credentials implementation.
  2. Internal CALL-E integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official CALL-E vendor API documentation, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® Visual Workflow Builder, anonymized data from our technical support team.
  5. WEXTL® Apps Library
  6. WEXTL® CALL-E App Documentation
  7. WEXTL® Workflow Scheduler
  8. WEXTL® HTTP node documentation

How we write and maintain CALL-E app documentation

Explore how WEXTL® crafted CALL-E integration page documentation. Used sources, the role of AI, and how the team validates the result.