CALL-E and Moonshot Integration

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

Connect CALL-E and Moonshot to automate ai workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.

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

Learn about CALL-E and Moonshot

Detailed info you need to know about CALL-E and Moonshot 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]

  • Moonshot

    • AI
    • 52 searches
    • 56 actions

    Kimi models and the Hosted Agents platform from Moonshot AI.[6]

How to connect CALL-E to Moonshot

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

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

WEXTL exposes actions and triggers for CALL-E and Moonshot 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 triggersMoonshot 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.

Moonshot modules

  • Archive a Credential Marks a credential held in a vault as archived, with its secret values erased in the process.
  • Archive a Memory Store Marks a memory store as archived, and its name stays reserved.
  • Archive a Session Archives an agent session, and any work in progress inside it is cancelled.
  • Archive a Skill Moves a custom skill to the archive, which frees its name for a new skill.
  • Archive a Thread Marks one thread of a session as archived.
  • Archive a Trigger Puts a trigger in the archive. Platform-managed triggers, such as dream policy schedules, cannot be archived.
  • Archive a Vault Archives a credential vault along with its active credentials.
  • Archive an Agent Archives an agent. New sessions can no longer start with it, while existing sessions keep running.
  • Archive an Environment Marks an environment as archived, which is final. Existing sessions are not affected, but no new session can use it.
  • Cancel a Batch Cancels a batch job. Requests that already finished keep their results.
  • Check Credential Coverage Looks through your vaults for a credential matching each of 1 to 50 MCP Server URLs. Use Vaults to search only up to 16 of them instead of every vault you can see.
  • Create a Batch Starts a batch job that runs every chat request in an uploaded JSONL Input File. Use Completion Window for the time Moonshot has to finish it, from 12h up, and Metadata to tag it with up to 16 key-value pairs.
  • Create a Chat Completion Gets a reply from a Kimi Model for a series of Messages. Use Max Completion Tokens for the longest reply and Response Format to switch between text and JSON.
  • Create a Credential Saves a credential to a vault, working either as MCP server access or as an environment variable inside the sandbox. Add a Display Name such as GitHub MCP access to recognise it later.
  • Create a Memory Adds a file to a memory store under a relative Path. Leave Content empty to create an empty file, or add text up to 20 MiB.
  • Create a Memory Store Sets up a store whose files sessions mount as a folder. Give it a unique Name for the folder, and add a Description so the model knows what it holds.
  • Create a Message Gets a Kimi answer using the Anthropic-compatible Messages API. Use Max Tokens to bound the reply, and System, Tools and Stop Sequences to steer it.
  • Create a Model Response Generates a response from a plain-text Input or a whole conversation, running the kimi-k3 Model. Use Instructions for a system prompt and Max Output Tokens to bound the length.
  • Create a Session Starts an agent session for an Agent in an Environment that is active and has a finished build. Use Resources to attach files, vaults and memory stores, Agent Version to pin an exact version, and Title for a readable name.
  • Create a Session Event Sends a user message to a session, or interrupts the turn that is running. Use Delivery to queue the message for the next turn or steer the running one, and the output is the Queued Event ID.
  • Create a Session Resource Adds a File that you uploaded to a session that is already running, and places it under upload/ in the workspace. Vaults and memory stores are attached when the session is created.
  • Create a Skill Builds a custom skill from an archive that contains exactly one SKILL.md. The output has the Skill and its First Version.
  • Create a Trigger Sets up recurring runs of an Agent in an Environment on a cron schedule. Use Session Mode to start fresh sessions or continue one, and Opening Messages to give each run its task.
  • Create a Trigger Run Runs a trigger right now, outside its schedule. Paused and platform-managed triggers can still be run by hand. Add a Message to send text into the session as a user message.
  • Create a Vault Creates a vault for the credentials that agent sessions use, under a readable Display Name. Use Metadata to tag it with up to 16 key-value pairs.
  • Create an Agent Creates a hosted agent that runs on a chosen Model under a Name. Add a System Prompt for its instructions, a Description or Toolsets, and use Reasoning Effort or Model Provider to adjust the model.
  • Create an Environment Creates a sandbox for agent sessions from a Name. Use Network Access and Allowed Hosts to control outbound traffic, and list pip, npm, apt or Go packages for the sandbox.
  • Create an OAuth Session Prepares an OAuth authorization for an MCP Server URL in a vault, and returns an Authorize URL. Leave Credential Name empty to use the server URL as the name.
  • Create Credentials Batch Stores between 1 and 20 credentials in a vault in a single call, created in the order of the Credentials list.
  • Delete a Credential Removes one credential out of a vault. The deletion cannot be reversed.
  • Delete a File Deletes a file you uploaded. This cannot be undone.
  • Delete a Memory Removes a file from a memory store.
  • Delete a Memory Store Deletes a memory store with all of its files. This cannot be undone.
  • Delete a Pending Event Withdraws a queued input that an agent session has not processed yet.
  • Delete a Session Removes an agent session. This cannot be undone.
  • Delete a Session Resource Detaches one attachment, whether a file, a vault or a memory store, from a session.
  • Delete a Skill Removes a custom skill by archiving it, which frees its name for a new skill.
  • Delete a Vault Deletes a credential vault together with all its credentials.
  • Delete an Artifact Deletes an artifact together with every version of it. This cannot be undone.
  • Delete an Environment Removes an environment. This cannot be undone.
  • Delete Memory Version Text Removes the stored text of one earlier version of a memory file. This is final.
  • Estimate a Token Count Estimates the token usage of a conversation with the tokenizer of the chosen Model. The output is the Estimate.
  • Fetch a Web Page Pulls the page behind an http or https Page URL and returns the Title with the page text as Markdown.
  • Get a Batch Checks the Status of a batch job along with its Output File ID and Error File ID.
  • Get a Credential Reads a credential stored in a vault, showing its Display Name and Authentication details.
  • Get a Dream Policy Looks up the automatic maintenance policy of a memory store, with its Activity Condition and Schedule Condition.
  • Get a File Reads the File Name, Size (Bytes) and Purpose of an uploaded file, with the Status of its processing.
  • Get a Memory Pulls a file out of a memory store, including its Content (Base64), Path and Content Size (Bytes).
  • Get a Memory Store Reads a memory store, showing its Name, Description and when it was created or updated.
  • Get a Memory Version Looks up an earlier state of a memory file, giving its Operation, Source and Revision.

Explore alternative integrations

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

Automate CALL-E and Moonshot on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting CALL-E and Moonshot.

How do I connect CALL-E and Moonshot?

Connect your CALL-E and Moonshot 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 Moonshot?

Example: when the "Watch Call Completed" trigger in CALL-E fires, WEXTL can "Archive a Credential" in Moonshot. CALL-E has 1 trigger (including Watch Call Completed). Moonshot has 108 actions (including Archive a Credential, Archive a Memory Store, and Archive a Session). Add filters and transforms between steps when you need them.[1]

Can CALL-E trigger actions in Moonshot, and Moonshot 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 Moonshot?

No. CALL-E-to-Moonshot 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 Moonshot in real time?

Yes. Trigger-based automations start the moment CALL-E (or Moonshot) 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 + Moonshot 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 Moonshot?

You can build your CALL-E + Moonshot 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 Moonshot integration.

  1. CALL-E and Moonshot integration source code, module specs and credentials implementation.
  2. Our CALL-E and Moonshot integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for CALL-E and Moonshot, 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. Moonshot 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 Moonshot integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore CALL-E and Moonshot, or get started