Most questions have a fixed answer, so they are below. If yours is not here, write to us and a person will reply.
What is a node, exactly?
A block you can drag into an n8n workflow. It wraps one API so the person using it fills in a form instead of building an HTTP request. You describe the API here and get a package n8n installs — no TypeScript and no build step.
Can I build a trigger, or a webhook?
Not yet. Every node built here is an action node: something a workflow calls, not something that starts one. This is the most common thing people arrive wanting, so it is worth knowing before you spend time on it.
Which kinds of authentication work?
An API key, sent either as a header or as a query parameter, and HTTP basic auth. OAuth2 is not supported yet — it is deliberately absent until it can be generated and tested properly rather than nearly working.
Where does my API key go?
Nowhere near our servers. Keys you type while testing a call stay in your browser for that session. The node you build stores the shape of its authentication — that it needs a key, and where the key goes — never a key itself. Whoever installs the node supplies their own inside their own n8n.
Can one node talk to two different hosts?
Not currently. Every operation in a node shares one address, so an API split across a data host and a separate CDN host needs two nodes today.
What happens when I ask to publish?
It goes to a person for review before it reaches npm. Nothing is published without your say-so, and nothing is published automatically.
I deleted a node by mistake.
It is not gone. Deleted nodes sit in
your deleted nodes and can be put back for 30 days, along with every version you kept.