Verified is not the same as listed: getting API Indonesia onto n8n.io/integrations
Our n8n node passed verification in September but stayed invisible on n8n.io/integrations for a month. The cause was one registry flag, and the fix was an email.
API Indonesia has had an n8n community node, n8n-nodes-api-indonesia, since September. As of 29 October it also has a page on the n8n integrations directory: n8n.io/integrations/api-indonesia.
Those two things sound like the same milestone. They were a month apart.
What verification gave us
n8n approved the node for verification on 23 September, and it was published to n8n Cloud the next day. An update to version 0.3.0 was approved on 28 September.
Verification is what makes a node installable from the nodes panel. An instance owner or admin searches for it, finds it under “More from the community”, and installs it once for the whole instance. On n8n Cloud that is the only way to get a community node at all.
So from late September the node was usable. It was not findable from the place most people start looking.
What it did not give us
Searching “indonesia” on n8n.io/integrations returned zero results.
The n8n community-nodes registry answered the question. Our record was published, verified, and carried the right version, but it had isOfficialNode: false and no company name. The integrations directory only builds pages for nodes flagged as partner nodes. Verification and partner listing are separate states, and nothing in the verification emails mentions the second one.
You can check your own node’s state with one request:
curl -sg 'https://api.n8n.io/api/community-nodes?filters[packageName][$eq]=YOUR-PACKAGE' \
| jq '.data[0].attributes | {npmVersion, isPublished, isOfficialNode, companyName}'
The fix
On 28 October I wrote to the n8n creators team, asked why a verified node was missing from the directory, and named Khaisa Studio as the company behind it. They routed it to the nodes team the same day.
On 29 October the registry record flipped to isOfficialNode: true and the page went live, describing the node as “built and maintained by our partners at API Indonesia and verified by n8n”.
What is on the page, and what is not
The node covers 31 resources and 106 operations: regions, prayer times, BMKG earthquakes and early warnings, Bank Indonesia exchange rates, public holidays, postal codes, schools, hospitals, halal and BPOM records, NIK and NPWP validation, Transjakarta, and more.
The operations table on the n8n.io page currently shows only the region operations. The full list is in the README.
If you ship an n8n node
- Treat verification and directory listing as two separate goals.
- Check
isOfficialNodeandcompanyNamein the registry after you are verified. If they are empty, ask the n8n team. The listing does not appear on its own. - Have a company name ready. The listing is attributed to a partner, not to a person.