Custom backend jobs
Run collection from your own app, queue system, cron jobs, or internal services instead of routing everything through a workflow builder.
API access
Build direct integrations for YouTube comment data
Use the API when you want comment collection to plug into your own app, backend, analytics stack, or AI pipeline. This is the route for people who want direct control over how the integration works.
Prefer less plumbing?
Start with the workflow page
Use the n8n route when you want the quicker setup and come back to the API once you need more direct control.
Good fit when
The real job is bigger than a single workflow
Direct data pipelines
Move structured results into warehouses, moderation systems, internal dashboards, or the rest of your application stack.
More control over the flow
Choose exactly how requests are triggered, how status is checked, and what happens after the result is ready.
How it works
Direct integrations usually follow this flow
1
Create an API key
Use the dashboard when you are ready to authenticate requests from your app or service.
2
Start the job
Call the API with the content you want to process and let your own app decide how requests are initiated.
3
Track progress
Poll for status so your system knows when the output is ready and what should happen next.
4
Push the result downstream
Store it, enrich it, alert on it, or hand it off to the rest of your stack.
What you can build
Make comment data part of a bigger system
Moderation and alerting
Trigger keyword checks, review queues, or internal notifications when new comment data lands.
AI enrichment
Send structured comment data into prompts, classifiers, summaries, and analysis layers inside your own pipeline.
Reporting systems
Feed warehouses, dashboards, and internal reporting tools without depending on manual exports.
Product workflows
Make comment data part of the systems your team already uses instead of treating exports as the final destination.
Resources
Start with the docs, then go deeper where you need to
Docs
The best place to start when you want the request flow and examples in plain language.
Open docsSwagger
Use the interactive reference when you want endpoint shapes and request details in one place.
Open SwaggerAPI key dashboard
Create the key you will use when the integration is ready to authenticate.
Open API keysn8n page
If the direct route feels heavier than you need, switch to the workflow setup path instead.
Open workflow page
FAQ
Questions before you wire the direct route
Who is this page for?
Teams and developers who want to build directly in code, wire comment data into existing systems, or control how the integration behaves end to end.
When is the API the better choice than n8n?
Use the API when you want custom orchestration, deeper control, or direct integration with backend systems. Use the n8n page when speed and lower setup overhead matter more.
Do I need Swagger if I already have the docs?
Not always. The docs are usually the easiest place to start. Swagger helps when you want the interactive reference, endpoint shapes, and request details in one place.
Can this fit AI or internal tooling use cases?
Yes. The direct route is especially useful when comment data needs to pass into prompts, classifiers, moderation logic, or systems that already live in your own stack.