Moonshot and Parsio Integration

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

Connect Moonshot and Parsio 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 Parsio

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

  • Parsio

    • AI
    • 1 trigger
    • 11 searches
    • 17 actions

    Document parsing service that turns emails, PDFs and images into structured data.[6]

How to connect Moonshot to Parsio

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

How does the integration between Moonshot and Parsio work in WEXTL?

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

Parsio triggersMoonshot actions

Parsio modules

  • Clone Templates Copies parsing templates into another mailbox. Use Target Mailbox to choose which mailbox receives the copies, so extraction rules built once serve a second mailbox.
  • Create a Mailbox Opens a new Parsio mailbox under a Name. Use Preset to choose the parser type, and ML Model to select the OCR or AI engine. Set Keep Raw Data to store the raw data of each document.
  • Create a Webhook Registers a URL that Parsio calls for the chosen Event in a mailbox. Pick a Table when the event is tied to one, and turn off Enabled to hold deliveries back.
  • Delete a Mailbox Deletes a Parsio mailbox you no longer need for incoming documents.
  • Delete Templates Removes several parsing templates in one request.
  • Delete Webhooks Clears out several webhooks in a single request.
  • Disable Templates Turns off parsing templates in bulk, so a whole set of extraction rules stops being enabled in one call.
  • Enable Templates Enables a set of parsing templates in bulk, listing each template ID under Templates.
  • Get a Document Fetches one parsed document by its Document ID, with its Status, Content Type and Processed At date.
  • Get a Mailbox Shows one mailbox with its Email Prefix, Preset and Process Attachments setting.
  • Get a Template Gets one parsing template with its Name, Enabled state and Created At. Use Mailbox to narrow the Template list to a single mailbox.
  • Get a Webhook Gets one webhook with its URL, Event and Enabled setting. Use Mailbox to shorten the Webhook list to one mailbox.
  • Get Parsed Data Pulls the extracted JSON of processed documents in a mailbox. Narrow it with From and To dates, and use Page to move through results and Limit to read fewer.
  • List Collected Emails Returns the addresses a mailbox has collected, each as Email and Name. Use Page to step through them and Limit to cap the total read.
  • List Documents Searches the documents inside a mailbox. Filter on Search text in the name, Statuses for the parsing outcome, and From and To for a date range.
  • List Mailboxes Retrieves every mailbox in the account, each with Name, Email Prefix and Preset. Use Limit to stop after a set number.
  • List Table Fields Shows the table fields defined for a mailbox, each with an ID and Name. Use Limit to read only part of the list.
  • List Templates Finds the parsing templates in a mailbox, with Name, Enabled flag and Created At. Page moves through longer lists.
  • List Webhooks Gathers the webhooks set up for a mailbox. Each carries a URL and Event. Use Limit to trim the output.
  • Make an API Call Runs a free-form request against the Parsio REST API using your saved credential.
  • Parse a Document Again Runs extraction again on a document already in Parsio. This may use parsing quota.
  • Parse a File (Wait for Result) Sends a File to a mailbox and waits until parsing is complete, then returns Status and Processed At for the finished document.
  • Parse Text or HTML (Wait for Result) Parses content in a mailbox and holds the step until parsing ends. The finished document arrives with its Status and Processed At. Send it as HTML or Text.
  • Send Text or HTML for Parsing Queues email-style content for extraction in a Parsio mailbox and returns the Doc ID before parsing finishes. Provide HTML or Text, with optional From, To and Name. Use Meta to attach a JSON object to the parsed data.
  • Skip Documents Marks documents of a mailbox as skipped, taking each document ID from Documents.
  • Update a Mailbox Edits mailbox settings such as Name, Email Prefix and Preset. Use Alert Frequency (Hours) for alert emails and Receive Email to toggle inbound mail.
  • Update a Webhook Changes the Name, URL or Event of a webhook, or turns delivery on or off with Enabled. Use Table when the new event applies to one table.
  • Upload a File for Parsing Uploads a file under a File Name into a mailbox, then returns the Doc ID before parsing finishes. Use Meta to add a JSON object to the parsed data.
  • Watch Events Fires the workflow instantly when Parsio posts a document event to its webhook. Each event brings the document Status and Content Type.

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

Automate Moonshot and Parsio on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Moonshot and Parsio.

How do I connect Moonshot and Parsio?

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

Example: when the "Watch Events" trigger in Parsio fires, WEXTL can "Archive a Credential" in Moonshot. Moonshot has 108 actions (including Archive a Credential, Archive a Memory Store, and Archive a Session). Parsio has 28 actions (including Clone Templates, Create a Mailbox, and Create a Webhook). Add filters and transforms between steps when you need them.[1]

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

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

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

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

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

Explore Moonshot and Parsio, or get started