DEV Community: Khairul Muhtadin

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/

API Indonesia is now available on RapidAPI

Khairul Muhtadin — Mon, 20 Jul 2026 11:00:00 +0000

API Indonesia is now available on RapidAPI.
If you prefer discovering and testing APIs through a marketplace workflow, you can explore it there. The listing covers Indonesian public data endpoints such as regions, postal codes, public holidays, prayer times, earthquakes, exchange rates, and format validation utilities.
If you prefer the full self-serve path, the main site and docs remain the primary entry points:

https://apiindonesia.id/
https://docs.apiindonesia.id/ RapidAPI listing: https://rapidapi.com/contactmuhtadin/api/api-indonesia This is a distribution update. Existing production base URL and API keys on the main platform stay the same.

Per-product landing pages for API Indonesia

Khairul Muhtadin — Fri, 17 Jul 2026 03:45:37 +0000

API Indonesia now has a product catalog and per-API landing pages.

Instead of forcing every visitor straight into a long docs page, each dataset has its own page under /produk. There are Indonesian and English versions.

Coverage snapshot:

23+ API products
280K+ data records
Regions, weather, Bank Indonesia rates, validation, halal, BPOM, Hijri calendar, schools, earthquakes, and more

What this is for:

discover which public datasets exist
understand use cases before reading the full reference
jump into the right docs section faster

Catalog:

https://apiindonesia.id/produk/

Example:

https://apiindonesia.id/produk/wilayah

This is a discovery and onboarding update. It does not change the production API base URL or existing API keys.

Try API Indonesia endpoints from the docs

Khairul Muhtadin — Thu, 16 Jul 2026 11:00:01 +0000

API Indonesia docs now include an interactive Try It Out console.
You can test endpoints directly in the browser with:

API key
JWT
query params
path params
JSON body This is meant to reduce setup friction. You do not need to open Postman just to see what an endpoint returns. Docs: https://docs.apiindonesia.id/ This is a developer experience update. It does not change the production base URL or existing API keys.