Skip to main content

​
Why does an error occur when importing an n8n Agent into the Creator Studio interface?

  1. The n8n JSON does not comply with the current platform’s import technical specifications.
  2. The n8n JSON contains Credentials not currently supported by the platform.
  3. The workflow itself has issues with its code logic. You can debug it within the n8n workflow interface and then try importing again.

​
What technical specifications must n8n workflows meet for import at this stage?

We have established technical specifications for n8n workflow integration based on the platform’s current capabilities.

​
What APIs does our platform currently offer?

We provide comprehensive technical documentation detailing the types of APIs currently supported.

​
Which Credentials are currently supported by the MuleRun platform?

Currently, the Credentials we support can be broadly categorized into two types: API Key and OAuth. We will publish the list of supported model types and integrated platforms on our documentation site.

​
How do I publish an n8n Agent on our platform?

First, you need to apply to become a Creator on our platform. After your application is approved, you must import the Agent code into the Creator Studio interface, configure the relevant information, and submit it for review. Once approved, we will publish your n8n Agent on the MuleRun Explore page.

​
Which version of n8n does Creator Studio support?

When selecting an n8n image, we provide an option for the n8n JSON version. You can configure it according to your preferred n8n version.

​
Some n8n image-generation nodes return Base64, but MuleRun requires a URL in markdown_content. What do I do?

There are two common approaches to resolve this:
  1. Configure n8n node to output URLs directly a. Many n8n large-model nodes allow you to specify the output format. b. Set the output to URL instead of Base64.
  2. Convert Base64 to URL via storage service a. If the node only outputs Base64, you can upload the image to an object storage service (e.g., Supabase, AWS S3, GCP Storage, etc.). b. Once uploaded, use the returned public URL to populate the markdown_content field.

​
How do I use OpenAI models not yet supported by MuleRun API?

Such as DALL·E? When building an agent in n8n, if you need to use an OpenAI model that is not currently supported by MuleRun API, you can configure the workflow as follows:
  • For AI Agent nodes using unsupported models, create a separate credential with your own OpenAI API key.
  • This separates unsupported nodes from supported ones. MuleRun API will automatically handle the supported models, while unsupported models will use your custom credentials directly.

​
Which workflows are supported for import?

We currently support importing n8n workflows. Support for Dify and ComfyUI is planned, while there are no current plans to support Coze.

​
What payment methods are available for purchasing API access?

The following payment methods are supported:
  • Alipay
  • Visa
  • Master

​
If an n8n workflow runs locally, can it be uploaded to MuleRun and used directly, or does it need modifications?

If the workflow contains custom nodes or community nodes, is configured with special OAuth credentials, or uses niche APIs, it may not work on MuleRun without adjustments. See the details at https://mulerun.com/docs/creator-guide/agent/n8n-agent-specs.

​
Which Google nodes are supported?

We support n8n official supported Google nodes, including Google Docs, Google Sheets, Google Drive, etc. Creator should provide its own Google Service OAuth credentials. Here is the instructions for creating a Google credential. See the full list of supported Google node here: https://docs.n8n.io/integrations/builtin/credentials/google/#compatible-nodes

​
Where do agents run?

n8n workflows run on MuleRun servers (runtime), not on the creator’s own machine.

​
If an agent needs asynchronous processing and takes about 10 minutes to return feedback to the user, how is that handled?

Planned feature: MuleRun agents will be able to send in-site messages to users with two notification types:
  • Inbox notifications
  • Optionally, users can choose to sync in-site messages to email
MuleRun agents support various asynchronous workflows; you can run tasks offline for one or two hours, or even a full day, without issues.
⌘I