DEV Community: Khairul Muhtadin

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.

Agentic Is Powerful. The Bill Is in the Tokens.

Khairul Muhtadin — Wed, 15 Jul 2026 13:00:00 +0000

Agentic workflows are useful. The problem is how fast tokens pile up.

A single do this can turn into dozens of model calls. Context grows every turn. Retries get more expensive late in the session. Even simple search and re-read loops show up on the bill.

That is token addiction: wrapping deterministic work in an LLM every time.

Why agentic cost escalates

Multi-step agent loops turn one goal into many model rounds.
Input context dominates. Files, logs, and tool schemas get re-sent every turn.
Retries late in a session hit a fat context window, so each attempt costs more than the last.

What token addiction looks like

Agent greps the same repo on every run
LLM summarizes JSON that a Set node or script could map
Full HTML dumped into context instead of structured fields
No max steps on tool loops

You are paying for judgment on work that never needed judgment.

A simple control plane

With a clear process, n8n helps you decide when AI should run:

Rules first for structured data, clear if/then paths, and high-volume glue.
One-shot AI when the task is fuzzy but bounded: classify, extract, draft once.
A full agent only when the path is truly unknown, with a budget and a kill switch.

Use AI for judgment. Use workflows for everything else.

Autonomy without routing is just an expensive loop.

Ship with n8n: 20 builder skills

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

Ship with n8n: 20 builder skills.

From a working canvas to systems you can trust in production.

We do not start with agents. We start with control:
• how runs start and how items move
• JSON, HTTP, and readable design
• failures, branches, and secrets
• then models, databases, hosting, and full systems

Three arcs:

Canvas & data (01–10)
Control & safety (11–15)
Operate & scale (16–20)

Save this map. We go one skill per episode.

Next: 01 · What n8n is for.

Which skill do you want first after the fundamentals?

Arc A · Canvas & data
01 What n8n is for · 02 Nodes as units of work · 03 Readable workflow design · 04 How a run starts · 05 Webhooks that are safe · 06 How items move · 07 Expressions without fear · 08 JSON you can debug · 09 HTTP as universal adapter · 10 APIs in production

Arc B · Control & safety
11 Failure paths on purpose · 12 Branching without spaghetti · 13 Batches, waits, and exits · 14 Transform without overkill · 15 Secrets out of the canvas

Arc C · Operate & scale
16 Agents only when needed · 17 One-shot models in a flow · 18 A real source of truth · 19 Own the stack · 20 Systems, not single flows

20 n8n skills that actually matter in production

Khairul Muhtadin — Tue, 14 Jul 2026 11:00:03 +0000

20 n8n skills that actually matter in production.

Not a random tip list. This is the order I use so workflows do not only work in a demo.

We do not start with agents.

We start with control:

• how a run starts

• how items move between nodes

• JSON, HTTP, readable design

• errors and secrets, then models and full systems

I split it into 3 arcs:

Canvas and data (01–10)
Control and safety (11–15)
Operate and scale (16–20)

Arc A · Canvas and data

01 What n8n is for · 02 Nodes as units of work · 03 Readable workflow design · 04 How a run starts · 05 Webhooks that are safe · 06 How items move · 07 Expressions without fear · 08 JSON you can debug · 09 HTTP as universal adapter · 10 APIs in production

Arc B · Control and safety

11 Failure paths on purpose · 12 Branching without spaghetti · 13 Batches, waits, and exits · 14 Transform without overkill · 15 Secrets out of the canvas

Arc C · Operate and scale

16 Agents only when needed · 17 One-shot models in a flow · 18 A real source of truth · 19 Own the stack · 20 Systems, not single flows

One skill per episode: common mistake, checklist, small build.

Next: 01 · What n8n is for.

API Indonesia now ships an OpenAPI 3.1 spec

Khairul Muhtadin — Mon, 13 Jul 2026 12:39:00 +0000

I just published an OpenAPI 3.1 spec for API Indonesia.
If you are integrating Indonesian public data, you no longer need to rebuild the request surface by hand from scattered docs.
What is live:

Official OpenAPI 3.1 document
80 operations
Ready to import into Postman, Insomnia, Bruno, or client generators Spec: https://docs.apiindonesia.id/openapi.json Full docs: https://docs.apiindonesia.id/ This update is about developer experience, not a breaking API change. Existing base URL and API keys stay the same. If you prefer starting from a machine-readable contract, import the spec first, then explore the docs.

Agentcash is giving away $𝟭𝟬𝟬,𝟬𝟬𝟬 𝘁𝗼 𝘂𝘀𝗲𝗿𝘀.

Khairul Muhtadin — Thu, 12 Mar 2026 11:17:07 +0000

Agentcash is giving away $100,000 to users.
Just connect your GitHub account to claim your bonus.

The system will analyze your digital presence to determine how much you get up to $25 per user.
It also uses the x402 protocol, which can be used to pay for API access.

Grab yours here: https://dub.sh/agentcash