CALL-E and Sonix Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Keep CALL-E and Sonix matched by integrating their events and actions. When ai events happen in CALL-E, update the Sonix automatically - without any line of code in visual workflow builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about CALL-E and Sonix

Detailed info you need to know about CALL-E and Sonix integrations in WEXTL. Explore which modules apps support and how you connect them.

  • CALL-E

    • AI
    • 1 trigger
    • 5 searches
    • 4 actions

    Place AI phone calls, read call results and transcripts, and run published goals.[5]

  • Sonix

    • AI
    • 6 searches
    • 6 actions

    Automated transcription and translation for audio and video content.[6]

How to connect CALL-E to Sonix

Set up your CALL-E and Sonix integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between CALL-E and Sonix work in WEXTL?

WEXTL exposes actions and triggers for CALL-E and Sonix that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

CALL-E triggersSonix actions

CALL-E modules

  • 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.
  • 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.
  • Make an API Call Makes an authorized free-form request to the CALL-E REST API with your saved credential.
  • 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.

Sonix modules

  • Create a New Media Uploads an audio or video file to Sonix for transcription in a Language. Use File URL for files over 100MB, or Transcript Text to align an existing transcript instead of transcribing.
  • Create a Translation Requests a translation of a transcribed recording into another Language. Run Get a Translation Status to follow its progress.
  • Delete a Media Removes a recording from your Sonix account.
  • Get a JSON Transcript Pulls the finished transcript of a completed recording in structured JSON form, with the Name of the recording alongside it.
  • Get a Media Status Looks up one recording and reports its Status, Language, Created at, Public URL and Custom Data.
  • Get a Text Transcript Returns the transcript of a finished recording as text, looked up by its Media ID.
  • Get a Translation Retrieves the translated transcript of a recording. Use Language to choose which translation to read, and only completed recordings are offered.
  • Get a Translation Status Looks up the Status of the translation of a recording into one Language, using its Media ID.
  • Make an API Call Runs a free-form request against the Sonix REST API using your saved credential.
  • Search Media Finds recordings in your Sonix account. Use Search to match by name, Status to keep completed, transcribing, aligning or failed ones, and Limit to cap how many are returned.
  • Submit Multitrack Media Submits a recording with several audio tracks for transcription, with Multitrack turned on. Use Speaker Labels for a JSON array of speaker names and Keywords to hint at words the engine should expect.
  • Update a Media Changes a recording in Sonix. Set Name to rename it, Custom Label to label it, or Folder ID to put it in another folder.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with CALL-E and Sonix integrations. Pick any from the list below if the current combination isn't the one you need.

Automate CALL-E and Sonix on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting CALL-E and Sonix.

How do I connect CALL-E and Sonix?

Connect your CALL-E and Sonix accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between CALL-E and Sonix?

Example: when the "Watch Call Completed" trigger in CALL-E fires, WEXTL can "Create a New Media" in Sonix. CALL-E has 1 trigger (including Watch Call Completed). Sonix has 12 actions (including Create a New Media, Create a Translation, and Delete a Media). Add filters and transforms between steps when you need them.[1]

Can CALL-E trigger actions in Sonix, and Sonix in CALL-E?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate CALL-E and Sonix?

No. CALL-E-to-Sonix automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does CALL-E integrate with Sonix in real time?

Yes. Trigger-based automations start the moment CALL-E (or Sonix) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a CALL-E + Sonix integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect CALL-E with Sonix?

You can build your CALL-E + Sonix automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

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

  1. CALL-E and Sonix integration source code, module specs and credentials implementation.
  2. Our CALL-E and Sonix integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for CALL-E and Sonix, 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. CALL-E integration information
  6. Sonix integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

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

Explore CALL-E and Sonix, or get started