Moonshot and OpenMic AI Integration

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

Connect Moonshot and OpenMic AI 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 Moonshot and OpenMic AI

Detailed info you need to know about Moonshot and OpenMic AI integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Moonshot

    • AI
    • 52 searches
    • 56 actions

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

  • OpenMic AI

    • AI
    • 2 triggers
    • 19 searches
    • 21 actions

    Voice AI agents for inbound and outbound phone calls.[6]

How to connect Moonshot to OpenMic AI

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

How does the integration between Moonshot and OpenMic AI work in WEXTL?

WEXTL exposes actions and triggers for Moonshot and OpenMic AI 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.

OpenMic AI triggersMoonshot actions

OpenMic AI modules

  • Add a Contact Saves a person to an OpenMic contact list from a Name and up to three phone numbers. Add Contact Info to give the agent extra details to use on the call.
  • Add an Agent to a Phone Number Connects a voice agent to a number for a chosen Direction, so inbound or outbound calls reach that agent.
  • Add Contacts in Bulk Loads up to 1,000 contacts into a list in one request, each with a Name. You get counts of what was Created and what Failed.
  • Create a Campaign Starts an outbound dialing run over a Contact List, placing calls with an Agent from a From Number. Use Days to limit the weekdays and Timezone to anchor the daily hours.
  • Create a Contact List Makes a list called Name to hold contacts for calling. Its Contact count, Created at and Updated at values are returned too.
  • Create an Agent Sets up a voice agent from a Name and the Prompt it follows on every call. Use First Message for a fixed greeting or Auto First Message to let the agent generate its opening.
  • Create an Agent Tool Gives an agent a tool it can call during a conversation, with a Type and Name. An API Request tool also takes a URL, a Method and an API Timeout.
  • Create an Outbound Call Places a call from one of your numbers to a To Number. Use Dynamic Variables to give the agent values for its prompt and Callback URL to receive the result when the call ends.
  • Delete a Campaign Deletes an outbound dialing campaign and returns its ID with a Deleted flag.
  • Delete a Contact List Removes a whole calling list from OpenMic, along with every contact stored on it.
  • Delete an Agent Removes a voice agent from OpenMic. An agent still linked to a phone number or campaign cannot be removed.
  • Delete an Agent Tool Removes a tool from a voice agent, so the agent has one fewer function to call mid-conversation.
  • Delete Contacts Deletes up to 1,000 contacts from a list in a single request. Use Contact IDs to say which ones.
  • Get a Call Retrieves one call using the Call ID returned by Create an Outbound Call or List Calls, with its Call status, Call type and numbers.
  • Get a Campaign Fetches one campaign showing its Name, Type, Status and the From number it dials from.
  • Get a Contact List Reads one contact list with its Name and Contact count, plus when it was last updated.
  • Get a Phone Number Retrieves one of your OpenMic numbers, showing which agents handle its inbound and outbound calls.
  • Get a Voice Retrieves a single voice with its Provider, Gender, Language and Accent. Look up the ID with List Voices.
  • Get an Agent Reads one voice agent with its Prompt, First message and Knowledge base id.
  • Get an Agent Tool Reads one tool on an agent, with its Type, Description, URL and Method.
  • Get an SMS Log Gets a logged message, showing its Direction, numbers and Session id. Its ID is shown by List SMS Logs.
  • Get the Current User Returns the Name and Email of the user the OpenMic credential belongs to.
  • Get Usage Totals minutes and texts sent over a period, with a Breakdown by Group By interval. Set the range with From Date and To Date.
  • List Agent Tools Retrieves the functions of an agent, optionally restricted by Type, Created After or Created Before.
  • List Agents Lists agents, filtered by text in their Name or by Created After and Created Before. Use Limit to bound the rows read.
  • List Calls Shows past calls filtered by Agent, Customer ID, Call Status or Call Type, within a window from From Date to To Date. Use Limit to stop at a fixed row count.
  • List Campaigns Returns campaigns with their Type and Status. Filter by Status or by creation date with Created After and Created Before.
  • List Contact Lists Fetches your contact lists, each with its Contact count. Filter them by when they were made with Created After and Created Before.
  • List Contacts Reads the people in one contact list, giving each a Name and phone numbers. Use Limit to decide how many are fetched.
  • List Phone Numbers Searches your OpenMic numbers with a fragment of a Phone Number or a Name, and shows which agents are linked.
  • List SMS Logs Pulls the text message log, narrowed by Direction, From Number, To Number, From Date or To Date.
  • List Voices Browses available voices. Use Search for part of a voice name, narrow with Gender, Language, Accent or Provider, and order results with Sort By and Sort Order.
  • Make an API Call Calls the OpenMic AI REST API directly with a free-form request under your saved credential.
  • Remove an Agent from a Phone Number Detaches the agent assigned to a phone number for one Direction.
  • Send an SMS Texts a Message to a To Number. Choose a From Number or leave it empty to let OpenMic select one. The sent message and its Status are returned.
  • Update a Campaign Changes a campaign by giving it another From Number or Contact List, a new Timezone, or different Time Start, Time End or Days.
  • Update a Contact Edits a contact by Contact ID, changing its Name, any of three phone numbers or the Contact Info the agent sees.
  • Update a Contact List Renames a calling list through its Name and returns its Contact count.
  • Update an Agent Edits a voice agent: change its Name, Prompt or First Message, or link another Knowledge Base ID.
  • Update an Agent Tool Changes a tool on an agent, including its Description, URL, Method, API Timeout or Parameters.
  • Watch Call Reports Starts the workflow as soon as OpenMic posts a finished call report, with its Call Duration and Session ID.
  • Watch New Calls Checks for calls created since the last check and runs the workflow once per call. Use Agent to follow one agent and Limit to cap the first check.

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 Moonshot and OpenMic AI integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Moonshot and OpenMic AI on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Moonshot and OpenMic AI.

How do I connect Moonshot and OpenMic AI?

Connect your Moonshot and OpenMic AI 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 Moonshot and OpenMic AI?

Example: when the "Watch Call Reports" trigger in OpenMic AI fires, WEXTL can "Archive a Credential" in Moonshot. Moonshot has 108 actions (including Archive a Credential, Archive a Memory Store, and Archive a Session). OpenMic AI has 40 actions (including Add a Contact, Add an Agent to a Phone Number, and Add Contacts in Bulk). Add filters and transforms between steps when you need them.[1]

Can Moonshot trigger actions in OpenMic AI, and OpenMic AI in Moonshot?

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 Moonshot and OpenMic AI?

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

Does Moonshot integrate with OpenMic AI in real time?

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

You can build your Moonshot + OpenMic AI automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Moonshot and OpenMic AI integration.

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

How we write our apps documentation

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

Explore Moonshot and OpenMic AI, or get started