Does the n8n node work on n8n Cloud or only self-host?

Both. On self-host, run `npm install n8n-nodes-aistemsplitter` from your custom-nodes directory and restart n8n. On n8n Cloud, open Settings → Community Nodes, paste n8n-nodes-aistemsplitter, and confirm — community-node install is supported on all current Cloud plans (legacy tenants may need to enable community nodes in workspace settings first).

How does the workflow handle long-running jobs without timing out?

Two patterns. The Wait for Split operation pauses the current workflow until the job finishes (good for low-volume queues). The dedicated AI Stem Splitter Trigger node receives the completion webhook in a separate workflow (better for high volume — main workflow returns immediately, downstream actions fire when stems are ready). Stem separation typically takes 30 seconds to a few minutes per file.

Does the trigger node work behind a firewall or behind a VPN?

The Trigger node needs an inbound webhook URL the API can POST to. On n8n Cloud, the trigger URL is automatically public. On self-host behind a firewall, use n8n's built-in tunnel (n8n start --tunnel) for testing, or expose the webhook via a reverse proxy / Cloudflare Tunnel for production. If inbound webhooks aren't possible at all, fall back to the Wait for Split operation (polling, no inbound).

Can I export and share a workflow that uses this node?

Yes. Use n8n's standard Workflow → Download to export the workflow as JSON. Credentials are referenced by ID, not embedded — recipients re-create the AI Stem Splitter API credential with their own ast_live_ key when they import. The same workflow JSON works across self-host and Cloud as long as the recipient also installs n8n-nodes-aistemsplitter.

Will the node break when n8n core upgrades?

Community nodes pin against n8n's stable interfaces. We test against each new minor n8n release and publish a matching version of n8n-nodes-aistemsplitter to npm within a few days when needed. Pin a specific node version in your custom-nodes package.json if you want zero surprise; the GitHub repo's release notes call out any breaking change explicitly.

How is per-job cost calculated when the workflow runs on every upload?

Per minute of input audio against credit packs that never expire — $0.08–$0.14 per minute depending on pack size. A 4-minute song is ~$0.32–$0.56; a 60-minute podcast is ~$4.80–$8.40. The first 3 minutes are free with no card required. There's no per-call surcharge, no concurrency tier gate, and no monthly subscription — only audio you actually process.

n8n node 能在 n8n Cloud 上用，还是只能 self-host？

两者都可以。Self-host 时，从你的 custom-nodes directory 运行 `npm install n8n-nodes-aistemsplitter`，然后重启 n8n。在 n8n Cloud 上，打开 Settings → Community Nodes，粘贴 n8n-nodes-aistemsplitter 并确认——当前所有 Cloud plans 都支持 community-node install（legacy tenants 可能需要先在 workspace settings 里启用 community nodes）。

workflow 怎样处理长时间运行的 job，避免 timeout？

两种模式。Wait for Split operation 会暂停当前 workflow，直到 job 完成（适合低量队列）。专用的 AI Stem Splitter Trigger node 会在另一个 workflow 中接收完成 webhook（更适合高量场景——主 workflow 立即返回，下游 actions 在 stems ready 后触发）。Stem separation 通常每个文件需要 30 秒到几分钟。

Trigger node 在 firewall 或 VPN 后面能工作吗？

Trigger node 需要一个 API 可以 POST 到的 inbound webhook URL。在 n8n Cloud 上，trigger URL 会自动公开。Self-host 且位于 firewall 后面时，测试阶段可以使用 n8n 内置 tunnel（n8n start --tunnel），生产环境则通过 reverse proxy / Cloudflare Tunnel 暴露 webhook。如果完全无法接收入站 webhooks，请退回到 Wait for Split operation（polling，无需 inbound）。

我可以导出并分享使用这个 node 的 workflow 吗？

可以。用 n8n 标准的 Workflow → Download 将 workflow 导出为 JSON。Credentials 只会按 ID 引用，不会内嵌——接收方导入后，用自己的 ast_live_ key 重新创建 AI Stem Splitter API credential。只要接收方也安装了 n8n-nodes-aistemsplitter，同一个 workflow JSON 就能同时在 self-host 和 Cloud 上运行。

n8n core 升级时，这个 node 会坏吗？

Community nodes 会 pin 到 n8n 的 stable interfaces。我们会针对每个新的 n8n minor release 做测试，并在需要时几天内把匹配版本的 n8n-nodes-aistemsplitter 发布到 npm。如果你希望零意外，可以在 custom-nodes package.json 中 pin 特定 node version；GitHub repo 的 release notes 会明确标出任何 breaking change。

当 workflow 对每次上传都运行时，每个 job 的成本怎么算？

按输入音频分钟数从永不过期的积分包扣费——按包大小不同，每分钟 $0.08–$0.14。一首 4 分钟歌曲约 $0.32–$0.56；一集 60 分钟 podcast 约 $4.80–$8.40。前 3 分钟免费且无需绑卡。没有 per-call surcharge、没有 concurrency tier gate，也没有月订阅——只为你实际处理的音频付费。

MIT licensed·9 ops

拖入一个 node，分离任意音频。

5 分钟内把 stem 分离加入任意 n8n workflow——无需胶水代码、无需服务器，支持 n8n Cloud 或 self-host。维护中的 community node 提供 async operations（Submit Split、Wait for Split，以及专门接收 webhook 的 AI Stem Splitter Trigger），让长时间运行的 job 不会拖到 execution timeout。

安装社区节点获取 API key

POST /v1/audio/splits

$ curl -X POST https://api.aistemsplitter.org/v1/audio/splits \
 -H "Authorization: Bearer $AISTEMSPLITTER_API_KEY" \
 -d '{"input": { "type": "direct_url", "url": "…" }, "stemModel": "6s" }'

HTTP/1.1 200 OKsucceeded

/ 可构建内容

这个 node 已经端到端支持的三个 workflow

自动拆分 Dropbox uploads

监听 Dropbox folder 中的新音轨。每次上传都会运行 Submit Split，等待完成，并把四条 stem set 写回 Drive 或 Dropbox 中对应音轨的 subfolder。

每日 karaoke playlist（YouTube cron）

Schedule（cron）trigger 拉取某个 channel 当天的 YouTube uploads，把每条音轨送进 Submit Split，并 suppress vocals stem，再把 karaoke version 推送到公开 playlist 或 CDN bucket。

Slack stem bot

Slack slash command 提交一个音频链接。AI Stem Splitter Trigger node 接收完成 webhook，并在 thread 内回复每条 stem 的下载链接。

/ 安装

安装到 n8n Cloud 或 self-host

Self-hosted（npm）

从你的 custom-nodes directory 运行 npm install n8n-nodes-aistemsplitter，然后重启 n8n。适用于 Docker、npm 和 desktop self-host installs。MIT licensed。

txt

# 1. Install the package
npm install n8n-nodes-aistemsplitter

# 2. Restart your n8n instance
n8n start

# 3. The "AI Stem Splitter" node appears in your nodes panel.

n8n Cloud（Settings → Community Nodes）

打开 Settings → Community Nodes，点击 Install，粘贴 n8n-nodes-aistemsplitter，并确认。适用于已启用 community nodes 的 Cloud tenants。

txt

# In n8n Cloud:
# 1. Settings → Community Nodes → Install
# 2. npm Package Name: n8n-nodes-aistemsplitter
# 3. Tick "I understand the risks", click Install
# 4. Refresh the workflow editor — node now in the panel

/ 第一个 workflow

5 步搭好你的第一个 workflow

添加 trigger

选择与你 workflow 匹配的 trigger：按需分离用 Webhook，cron jobs 用 Schedule，upload-driven runs 用 Google Drive 或 Dropbox，chat-driven splits 用 Slack。这个 trigger 会把 audio URL 传给 step 3。

Screenshot — Trigger picker（Webhook / Schedule / Drive / Slack）

创建 credential

打开 Credentials → New，搜索 AI Stem Splitter API，粘贴你的 ast_live_ key，并保存。这个 node 会用 API 验证 key，并显示 ✓ Connected。同一个 credential 会被这个 instance 里的每个 AI Stem Splitter node 复用。

AI Stem Splitter credentialsConnected

API Key

ast_live_••••••••••••••••••••

Base URL

https://api.aistemsplitter.org (default)

添加 AI Stem Splitter node

把 AI Stem Splitter node 拖到 canvas 上，选择 operation Submit Split，并填写三个字段：audioUrl（来自 trigger）、model（默认 htdemucs_ft，四条 stem——需要 guitar 或 piano 时切换到 six-stem model），以及 stems（用 chip 选择要返回的 stems）。

AI Stem Splitter — Submit Split

Resource

Split

Operation

Submit

Audio URL

Model

htdemucs_ft

Stems

vocalsdrumsbassguitarpianoother

等待完成

Stem splitting 每个文件需要 30 秒到几分钟。选择两种模式之一：Wait for Split operation 暂停本次 execution 直到 job 完成；或者让专用的 AI Stem Splitter Trigger node 在独立 workflow 中接收完成 webhook——更适合不应阻塞主 run 的高量队列。

Screenshot — Wait for Split node OR AI Stem Splitter Trigger

使用 stems

输出是一个 stem URLs array（vocals、drums、bass、other；请求时还可加 guitar 和 piano）。把这些 URLs 接到下游 nodes——Whisper 做 vocal-only transcription，Drive 或 S3 做存储，Slack 做聊天回复，Notion row 做 stem library entry。

Screenshot — 6 条 stem URLs 流入 Drive / Slack / ffmpeg

/ templates 与延伸阅读

Templates 与延伸阅读

Workflow templates

预构建 n8n workflows：stem-on-upload、daily karaoke、Slack stem bot。

API reference

完整 REST endpoints、error codes、OpenAPI 3.1 spec。

其他集成

GitHub Action、Docker/CLI、Pipedream——同一个 API key。

/ 常见问题

FAQ

Does the n8n node work on n8n Cloud or only self-host?
Both. On self-host, run `npm install n8n-nodes-aistemsplitter` from your custom-nodes directory and restart n8n. On n8n Cloud, open Settings → Community Nodes, paste n8n-nodes-aistemsplitter, and confirm — community-node install is supported on all current Cloud plans (legacy tenants may need to enable community nodes in workspace settings first).
How does the workflow handle long-running jobs without timing out?
Two patterns. The Wait for Split operation pauses the current workflow until the job finishes (good for low-volume queues). The dedicated AI Stem Splitter Trigger node receives the completion webhook in a separate workflow (better for high volume — main workflow returns immediately, downstream actions fire when stems are ready). Stem separation typically takes 30 seconds to a few minutes per file.
Does the trigger node work behind a firewall or behind a VPN?
The Trigger node needs an inbound webhook URL the API can POST to. On n8n Cloud, the trigger URL is automatically public. On self-host behind a firewall, use n8n's built-in tunnel (n8n start --tunnel) for testing, or expose the webhook via a reverse proxy / Cloudflare Tunnel for production. If inbound webhooks aren't possible at all, fall back to the Wait for Split operation (polling, no inbound).
Can I export and share a workflow that uses this node?
Yes. Use n8n's standard Workflow → Download to export the workflow as JSON. Credentials are referenced by ID, not embedded — recipients re-create the AI Stem Splitter API credential with their own ast_live_ key when they import. The same workflow JSON works across self-host and Cloud as long as the recipient also installs n8n-nodes-aistemsplitter.
Will the node break when n8n core upgrades?
Community nodes pin against n8n's stable interfaces. We test against each new minor n8n release and publish a matching version of n8n-nodes-aistemsplitter to npm within a few days when needed. Pin a specific node version in your custom-nodes package.json if you want zero surprise; the GitHub repo's release notes call out any breaking change explicitly.
How is per-job cost calculated when the workflow runs on every upload?
Per minute of input audio against credit packs that never expire — $0.08–$0.14 per minute depending on pack size. A 4-minute song is ~$0.32–$0.56; a 60-minute podcast is ~$4.80–$8.40. The first 3 minutes are free with no card required. There's no per-call surcharge, no concurrency tier gate, and no monthly subscription — only audio you actually process.
n8n node 能在 n8n Cloud 上用，还是只能 self-host？
两者都可以。Self-host 时，从你的 custom-nodes directory 运行 `npm install n8n-nodes-aistemsplitter`，然后重启 n8n。在 n8n Cloud 上，打开 Settings → Community Nodes，粘贴 n8n-nodes-aistemsplitter 并确认——当前所有 Cloud plans 都支持 community-node install（legacy tenants 可能需要先在 workspace settings 里启用 community nodes）。
workflow 怎样处理长时间运行的 job，避免 timeout？
两种模式。Wait for Split operation 会暂停当前 workflow，直到 job 完成（适合低量队列）。专用的 AI Stem Splitter Trigger node 会在另一个 workflow 中接收完成 webhook（更适合高量场景——主 workflow 立即返回，下游 actions 在 stems ready 后触发）。Stem separation 通常每个文件需要 30 秒到几分钟。
Trigger node 在 firewall 或 VPN 后面能工作吗？
Trigger node 需要一个 API 可以 POST 到的 inbound webhook URL。在 n8n Cloud 上，trigger URL 会自动公开。Self-host 且位于 firewall 后面时，测试阶段可以使用 n8n 内置 tunnel（n8n start --tunnel），生产环境则通过 reverse proxy / Cloudflare Tunnel 暴露 webhook。如果完全无法接收入站 webhooks，请退回到 Wait for Split operation（polling，无需 inbound）。
我可以导出并分享使用这个 node 的 workflow 吗？
可以。用 n8n 标准的 Workflow → Download 将 workflow 导出为 JSON。Credentials 只会按 ID 引用，不会内嵌——接收方导入后，用自己的 ast_live_ key 重新创建 AI Stem Splitter API credential。只要接收方也安装了 n8n-nodes-aistemsplitter，同一个 workflow JSON 就能同时在 self-host 和 Cloud 上运行。
n8n core 升级时，这个 node 会坏吗？
Community nodes 会 pin 到 n8n 的 stable interfaces。我们会针对每个新的 n8n minor release 做测试，并在需要时几天内把匹配版本的 n8n-nodes-aistemsplitter 发布到 npm。如果你希望零意外，可以在 custom-nodes package.json 中 pin 特定 node version；GitHub repo 的 release notes 会明确标出任何 breaking change。
当 workflow 对每次上传都运行时，每个 job 的成本怎么算？
按输入音频分钟数从永不过期的积分包扣费——按包大小不同，每分钟 $0.08–$0.14。一首 4 分钟歌曲约 $0.32–$0.56；一集 60 分钟 podcast 约 $4.80–$8.40。前 3 分钟免费且无需绑卡。没有 per-call surcharge、没有 concurrency tier gate，也没有月订阅——只为你实际处理的音频付费。

今天下班前交付 stem 处理步骤。

前 3 分钟免费开始（无需绑卡）。积分包永不过期——按购买量不同，每分钟 $0.08–$0.14。MIT licensed node，支持 n8n Cloud 或 self-host。

安装社区节点联系团队