Third-party integrations

Two unrelated things go by this name. One drives UseNadia from outside; the other pulls media in.

Driving UseNadia from a workflow tool

n8n, Zapier, Make and anything else that speaks HTTP talk to the Public API with your API key. Nothing to install on the UseNadia side.

For n8n specifically there is a node, n8n-nodes-nadia, with an action node and a trigger node, and Settings → Developers → N8N Node points at it. It wraps the same endpoints this documentation describes, so anything the node does you can also do with a plain HTTP request. Installation, credential and operations: n8n node.

Note

The direction matters. To make UseNadia act, call the Public API. To be told when UseNadia has acted, use a webhook — that is the side that fires into n8n rather than out of it.

Pulling generated media in

The original project’s Integrations page (/third-party) also connects external services that produce media — HeyGen and friends — so their output can be pulled into a post without downloading and re-uploading it: paste your own API key for the service, then the Import button in the attachments bar offers it.

The Integrations page only lists automation services

The Integrations entry is in the sidebar for the services your automations write to — Brevo first. The media services are not offered there, so Import has no source. Their code is untouched, which keeps the merge with the original project clean.

The video side of the pipeline is handled elsewhere in this project, not by these connectors.

How this differs from built-in AI generation

	Third-party integration	Built-in AI
Where it runs	The external service	UseNadia
Who pays	You, directly to that service	Nothing on your side
What you get	Whatever that service produces	Images and video from the configured generators
Setup	Your API key, per service	Nothing to set up

See AI generation for the built-in side.