n8n Integration

Template Pack (Import Directly)

Download and import these workflows from the n8n editor: Workflows → Import from file.

All templates are designed for RemoveBGVideo Public API v1 and can run with your X-Api-Key header.

GitHub template repo: https://github.com/JsonChao/removebgvideo-n8n-templates

• URL → Auto Start → Poll: /downloads/n8n/removebgvideo-url-auto-start-poll.json
• Local File Upload → v1/jobs: /downloads/n8n/removebgvideo-local-upload-v1.json
• Draft Job + Start (Pro Prompt): /downloads/n8n/removebgvideo-draft-start-pro.json
• Webhook Callback Receiver: /downloads/n8n/removebgvideo-webhook-receiver.json
• Daily Usage Summary Report: /downloads/n8n/removebgvideo-usage-daily-report.json

Required Variables

Node Screenshot-style Guide

Step 1: Create Job (HTTP Request)

POST /v1/jobs with video_url, model, output_format, auto_start

Step 2: Start Draft Job (Optional)

POST /v1/jobs/{job_id}/start for prompt/composition overrides

Step 3: Poll Status Loop

GET /v1/jobs/{job_id}, check completed/failed/processing branches

Step 4: Webhook Receiver

Receive job.completed and push output_url to downstream apps

Recommended Workflow

1. Trigger: Manual/Cron/Webhook from your business system.
2. HTTP node: POST /v1/jobs (set auto_start true for simplest path).
3. If auto_start false: HTTP node POST /v1/jobs/{job_id}/start.
4. Loop with Wait + HTTP GET /v1/jobs/{job_id} until completed.
5. Success branch: use output_url to send email, upload cloud drive, or callback your app.
6. Failed branch: log error payload and retry with controlled backoff.

Operational Tips

• Use wait node to avoid tight polling loops.
• Persist job_id and request_id in execution data for audit.
• For local files, upload with POST /v1/uploads first, then feed returned video_url into /v1/jobs.
• Add fallback branch for failed jobs.
• Use webhook_url in /v1/jobs payload to reduce polling pressure in high-volume automations.

Operational Patterns

• Use queue-based orchestration for sustained throughput.
• Separate latency-sensitive traffic from bulk processing workloads.
• Centralize webhook/event consumption through one idempotent handler.
• Use dead-letter queue for repeated failures and manual replay.

Go-Live Checklist

1. Load test with realistic clip duration distribution.
2. Validate alerting for error rate, queue lag, and failed jobs.
3. Confirm credit accounting and billing UX alignment.
4. Prepare escalation template containing job_id + payload summary.

n8n Operational Risks

• Avoid tight loops that hit API rate limits.
• Persist job_id and external correlation id in workflow variables.
• Use failure branch for notifications and replay queue.

When to Use n8n Integration

n8n Integration belongs to the Examples & Integrations section and covers production-ready n8n workflows with importable json templates and node-by-node setup guide.

The page is written for developers and operators who need predictable video background removal behavior in production, not just a one-off demo request.

• Use this example when n8n integration matches your deployment shape or automation pattern.
• Start with the reference flow, then replace storage, queue, and database pieces with your production stack.
• Keep one small fixture video for smoke tests and one difficult video for quality regression checks.

Implementation Notes

Before you promote this workflow, test it with at least one short clip, one longer clip, and one visually difficult clip from your actual product or customer segment.

For support and debugging, persist the original input reference, selected model, output format, credit usage, and final job status alongside your internal user or project id.

• Do not copy example credentials, callback URLs, or storage paths directly into production.
• Do not run high-volume jobs synchronously from user-facing request handlers.
• Do not skip observability; every example should emit enough state to replay or debug failed jobs.

Related Documentation

FAQ