DEV Community: Khairul Muhtadin

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

Khairul Muhtadin — Thu, 29 Oct 2026 13:28:33 +0000

I build and run API Indonesia, a REST API for Indonesian public data. This is a short note on getting its n8n node listed.

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 isOfficialNode and companyName in 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.

Indonesia Regions API: province, regency, district and village data

Khairul Muhtadin — Thu, 29 Oct 2026 07:36:43 +0000

Cross-posted from the API Indonesia blog. Original: https://apiindonesia.id/en/blog/indonesia-regions-api-provinces-to-villages/

I build and run API Indonesia (apiindonesia.id), a REST API for Indonesian public data. This post walks through the region data (38 provinces, 514 regencies/cities, 7,285 districts, 83,762 villages) and how to wire cascading address dropdowns to it, including the code snippets I use myself.

Almost every app that has an address form, from e-commerce and HRIS to government apps, needs cascading region dropdowns: pick a province, then the regency/city appears automatically, then the district, then the kelurahan/desa (village). The problem is that the official Indonesian administrative region data (based on Kepmendagri, the Ministry of Home Affairs decree) is large and changes often because of regional splits (pemekaran). Hardcoding this data in your own app means you have to keep up the maintenance every time something changes.

The Regions API (API Wilayah) from API Indonesia provides the entire administrative region hierarchy, province, regency/city, district, and kelurahan/desa (village), in one REST API you can just call, without storing a static dataset on your own server.

Data Coverage

Provinces: 38 provinces across Indonesia
Regency/City (kabupaten/kota): every regency and city under each province
District (kecamatan): every district under each regency/city
Kelurahan/Desa (village): every kelurahan and desa under each district
Cross-level search: search for a region name without knowing its level first

Endpoint List

Base URL: https://use.apiindonesia.id/api/v1/wilayah

Method	Endpoint	Description
GET	`/provinsi`	List all provinces (paginated)
GET	`/provinsi/:id`	Details of one province
GET	`/kabupaten?provinsi_id=`	List regencies/cities in one province
GET	`/kabupaten/:id`	Details of one regency/city
GET	`/kecamatan?kabupaten_id=`	List districts in one regency/city
GET	`/kecamatan/:id`	Details of one district
GET	`/kelurahan?kecamatan_id=`	List kelurahan/desa in one district
GET	`/kelurahan/:id`	Details of one kelurahan/desa
GET	`/search?q=`	Search regions across all levels at once

All list endpoints support the page and per_page parameters (maximum 100 per page) and return a meta object containing total, page, per_page, and total_pages.

Request Example

Get the list of regencies/cities in West Java:

curl "https://use.apiindonesia.id/api/v1/wilayah/kabupaten?provinsi_id=32" \
  -H "x-api-key: aip_live_xxx"

const res = await fetch(
  'https://use.apiindonesia.id/api/v1/wilayah/kabupaten?provinsi_id=32',
  { headers: { 'x-api-key': process.env.API_INDONESIA_KEY } }
);
const { data, meta } = await res.json();
console.log(data); // [{ id, name, province_id, ... }, ...]

import requests

res = requests.get(
    "https://use.apiindonesia.id/api/v1/wilayah/kabupaten",
    params={"provinsi_id": "32"},
    headers={"x-api-key": "aip_live_xxx"},
)
data = res.json()["data"]

Response Example

{
  "data": [
    { "id": "3273", "name": "KOTA BANDUNG", "province_id": "32" },
    { "id": "3204", "name": "KABUPATEN BANDUNG", "province_id": "32" }
  ],
  "meta": { "total": 27, "page": 1, "per_page": 20, "total_pages": 2 }
}

Building a Cascading Address Dropdown

The most common pattern: keep the provinsi_id the user selected in state, then call /kabupaten?provinsi_id= every time the user changes province. Repeat the same pattern for districts and villages. Because each level has a consistent id that works as a foreign key, you can store province_id, regency_id, district_id, and village_id directly in your own database without copying region names.

If you need free-form address search (for example an autocomplete to find a village), use the /search?q= endpoint, which searches all four levels at once and returns a level field to mark the type of region.

Tips for the /search endpoint:

Send at least 3 characters before actually calling the API, so autocomplete results do not burn through your quota.
Debounce user input for around 300ms before fetching.
Use the level field in the response to decide the icon or label in the dropdown (for example a "Kota" vs "Kabupaten" badge).

Why Not Hardcode the Data Yourself?

Many teams choose to copy an open-source region dataset into their database. That can work, but there is a risk of the data going stale after a regional split or a change to region codes, and you still have to build your own search and pagination endpoints. With the Regions API, the data always matches the latest region codes and you only need one API key to access every endpoint.

Combining with Other APIs

Region data is only really complete when you pair it with other APIs in the same ecosystem:

Postal Code API: after the user picks a kelurahan, fetch the matching postal codes via /api/v1/kodepos/search?q= so the postal code field fills in automatically. Good for e-commerce checkout and onboarding forms.
KBBI API: if your app shows region names in its content (for example a regional news portal), validate the spelling of place names via /api/v1/kbbi/word/:word.
BI Exchange Rate API: for logistics or e-commerce apps that show multi-currency prices per region, pair it with the official Bank Indonesia rates from /api/v1/kurs-bi/latest.

All of these APIs use the same API key, so integration just means adding a base path, not creating a new account.

FAQ

Does this data follow the latest regional changes? Yes, the data follows the latest Kepmendagri region codes and is updated on the API side, so you do not need to patch your own dataset every time a region splits.

How many kelurahan/desa are available in total? Every kelurahan and desa in Indonesia (more than 80 thousand) is available through the /kelurahan endpoint with pagination.

Can I use it for autocomplete? Yes. The /search?q= endpoint searches all levels at once and works well for autocomplete with client-side debounce.

Is it free? There is no monthly free allowance. New accounts get a one-time 3,000 credit bonus (Rp3,000) after email verification, and a successful request costs 2 credits, which is enough to build an MVP and test it.

Start Now

Get a free API key at dashboard.apiindonesia.id/register and see the full parameter list at docs.apiindonesia.id.

Text classification in n8n without a chat LLM: building a node for TypeSafe's Jev

Khairul Muhtadin — Mon, 21 Sep 2026 10:27:56 +0000

I Built an n8n Node for Decisions, Not Text Generation - Khairul Muhtadin

Why I built n8n-nodes-jev-classification for TypeSafe AI's Jev, how confidence-based routing works, and what I learned shipping it to npm.

khmuhtadin.com

Databases for durable state (sticky note vs filing cabinet)

Khairul Muhtadin — Tue, 18 Aug 2026 11:00:02 +0000

Workflows forget. That is fine for drafts.

It is fatal for orders, tickets, and retries. If state must survive the next run, sticky notes are not enough. You need a filing cabinet.

Swipe for when to store durable state, a create-once flow, and three beginner rules so retries stop inventing duplicates.

What is the one fact your flow keeps forgetting?

Episode 17 of Ship with n8n: 20 builder skills.

AI that stays under control (smart intern, not CEO)

Khairul Muhtadin — Sun, 16 Aug 2026 11:00:00 +0000

AI in n8n is not a magic coworker.

It is a smart intern. Without a job description, tools limits, and stop rules, it will improvise in production.

Swipe for the intern analogy, three rails before the model, and a support-triage flow where refunds still need a gate.

Where does your agent still have unlimited tools?

Episode 16 of Ship with n8n: 20 builder skills.

Wait, schedule, and time (alarm vs kitchen timer)

Khairul Muhtadin — Fri, 14 Aug 2026 11:00:00 +0000

Time in n8n is not “hope it runs later”.

An alarm starts the kitchen. A timer pauses mid-recipe. Mixing those two is how people get double fires and silent delays.

Swipe for a beginner map of Schedule vs Wait, a polite API loop, and three rules so time stays boring.

Do you need a clock, or just a pause?

Episode 15 of Ship with n8n: 20 builder skills.

Secrets that stay secret (your API key is a house key)

Khairul Muhtadin — Wed, 12 Aug 2026 11:00:01 +0000

Your API key is not “just config”.

It is a house key. Leave it on the door and anyone walking by can open production.

Swipe for a beginner map of n8n secrets: what counts as a secret, why hardcoding breaks you, and the simple habit that keeps keys in a vault instead of on the canvas.

Where do your live keys live today: credentials, or still inside a node?

Episode 14 of Ship with n8n: 20 builder skills.

Loops that finish (empty checks, no double-loop)

Khairul Muhtadin — Mon, 10 Aug 2026 11:00:00 +0000

Loops feel powerful until one never ends.

Missing exits, stacked pagination, side effects with no cap.

Swipe for a batch that actually finishes — and the double-loop trap.

Which loop in production would you not want running unsupervised tonight?

Episode 13 of Ship with n8n: 20 builder skills.

Branching without chaos (normalize first, then decide)

Khairul Muhtadin — Sat, 08 Aug 2026 11:00:01 +0000

Branching is where readable workflows go to die.

Nested IFs, no fallback, different shapes per arm, then a hopeful Merge.

Swipe for how I keep routes readable — normalize first, decide once, merge with a contract.

How many nested IFs are in your messiest production flow?

Episode 12 of Ship with n8n: 20 builder skills.

Failure paths on purpose (happy path is half the design)

Khairul Muhtadin — Thu, 06 Aug 2026 11:00:00 +0000

Happy path is not a full design.

If money or customer-facing steps can fail silently, you have hope — not production.

Swipe for how I wire failure on purpose, without the full node lecture in the caption.

Which of your critical workflows still fails quietly?

Episode 11 of Ship with n8n: 20 builder skills.

APIs in production (rate limits, retries, Arc A milestone)

Khairul Muhtadin — Tue, 04 Aug 2026 11:00:00 +0000

Connecting an API in the editor is easy.

Surviving rate limits, expired tokens, and retries is the real skill.

Swipe for batch+wait patterns, idempotent upserts, and an Arc A milestone check.

Would your flakiest integration survive a token refresh right now?

Episode 10 of Ship with n8n: 20 builder skills.

Build n8n Workflows with Indonesian Public Data Using the API Indonesia Community Node

Khairul Muhtadin — Fri, 24 Jul 2026 11:00:00 +0000

Build n8n Workflows with Indonesian Public Data Using the API Indonesia Community Node

Using an API in n8n is easy. Rebuilding the same HTTP Request setup for every workflow is the repetitive part: URLs, headers, API keys, parameters, and response mapping.
The API Indonesia community node packages that work into a native n8n node. Instead of starting from a generic HTTP Request node, you select a resource and operation, configure its fields, and continue building your workflow.

What the node supports

The node exposes Indonesian public-data resources such as administrative regions, prayer times, earthquakes, weather, exchange rates, public holidays, postal codes, schools, universities, and hospitals.
It also includes Quran, Bible, KBBI, vehicle plates, minimum wages, halal certification, BPOM products, Hijri calendar data, astronomy, OJK investment products, early warnings, Bank Indonesia exchange rates, validators, and utility endpoints.

Install the community node

Open n8n.
Go to Settings, then Community Nodes.
Select Install.
Enter n8n-nodes-api-indonesia. After installation, search for API Indonesia when adding a node to a workflow. ## Create credentials once Open the API Indonesia dashboard and create or copy an API key. Then, in n8n, create a credential of type API Indonesia API and paste the key. Production keys start with aip_live_. The default base URL is https://use.apiindonesia.id. You only need to change it when working against a development or staging environment. ## Example: retrieve the latest earthquakes A minimal workflow can be: Manual Trigger → API Indonesia → next action In the API Indonesia node, choose the Gempa resource and the operation for the latest earthquakes. The node returns the latest records, ready to send to a chat alert, database, dashboard, or a filtering step. That is the important difference from a demo-only integration: the node output is normal n8n data, so it can continue through the same workflow patterns you already use. ## Where this is useful Use it when a workflow needs Indonesian public data without manually recreating a request every time. Examples include daily prayer-time notifications, earthquake alerts, regional onboarding forms, weather-aware operations, halal product discovery, and enrichment flows for education or healthcare data. Start small. Pick one resource, run it from a Manual Trigger, inspect the output, then connect it to the next useful action. ## Resources Community node package: https://www.npmjs.com/package/n8n-nodes-api-indonesia API documentation: https://docs.apiindonesia.id/ API key dashboard: https://dashboard.apiindonesia.id/