Verified is not the same as listed: getting API Indonesia onto n8n.io/integrations

Description and use

A verified API Indonesia node was missing from the n8n integrations directory. After contacting n8n with the company name, it was marked official and listed.

Problem

A verified n8n community node was not appearing in the n8n integrations directory, preventing discoverability.

Outcome

The node became discoverable in the n8n integrations directory, improving visibility and installability.

Workflow

• 1. Verify the node with n8n (23 Sep).
• 2. Publish to n8n Cloud (24 Sep).
• 3. Check registry status via API call to confirm isOfficialNode and companyName.
• 4. Notice missing directory listing.
• 5. Email n8n creators team with company name (28 Oct).
• 6. Receive confirmation and updated registry record (29 Oct).
• 7. Directory page appears with partner attribution.

Evidence

n8n approved the node for verification on 23 September, and it was published to n8n Cloud the next day.

Source

Searching "indonesia" on n8n.io/integrations returned zero results.

Source

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.

Source

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".

Source