Postman is useful when you want to look closely at one API conversation: send a request, inspect the response, change a parameter, see an error.

A workflow platform such as n8n.io becomes useful when you want to watch several of those conversations turn into a workflow. That makes it a useful product-literacy tool even if you are not trying to become an automation engineer. A requirement such as “get a location, retrieve the forecast, decide whether rain is likely, then return a useful result” can stay abstract on a whiteboard. In n8n, we can wire the real calls together and watch data move from one step to another.

So we’re going to build a single companion workflow that goes with the article. It supports a manual learning path, useful failure handling and an externally callable webhook path, all using the same underlying geocoding, forecast and product-decision logic.

The completed workflow, its README and the downloadable n8n JSON are available in the public GitHub repository PM API Literacy Lab — Umbrella Weather Check. You can inspect the workflow structure there before importing it, or download the JSON and import it directly into your own n8n instance. (Note that there’s no guarantee that this will be continually updated, but it’s all been checked and working as of this writing.)

[Read more…]

In this part 5 of 5 for the series, we’re going to tie everything we’ve gone over about digital product connectivity together with a In this part 5 of 5 for the series, we’re going to tie everything we’ve gone over about digital product connectivity together with a field guide with learning references.

The first four parts are intended to offer a survey of product technical communications interfaces from APIs to agents and so on. This page is a See Also reference for more detailed information. A lot of it was used to craft the article series. Practically by definition, as a curated list of web things, it is likely to be outdated quickly. So consider this as just a snapshot for what the landscape of this space looks like in 2026.

Start with the landscape

• Postman, State of the API 2025 – useful current data on API-first adoption, API revenue, AI agents as API consumers and MCP awareness.
• Google, Developer’s Guide to AI Agent Protocols – a current map of MCP, A2A and newer agent protocols using one worked scenario.
• Every API Authentication Method Explained (Don’t Choose the Wrong One) (YouTube)

Core interface references

• OpenAPI Specification 3.2 – the formal description standard for HTTP APIs, including webhooks.
• GraphQL Specification – authoritative GraphQL language and execution model.
• gRPC Introduction – service definitions, RPC methods and Protocol Buffers.
• gRPC Core Concepts – unary and streaming RPC models.
• gRPC in 5 Minutes – YouTube
• AsyncAPI Documentation – event-driven and message-based API concepts.
• Apache Kafka Documentation – event streaming, producers, consumers, topics and decoupled processing.
• MDN Server-Sent Events – practical reference for one-way server-to-browser streams.

Enterprise messaging and batch integration

Not every important integration is an always-on API or event stream. Many industries still rely heavily on structured business-document exchange and scheduled or batch-oriented flows.

• What is Messaging? (IBM)
• X12 – EDI standards used across healthcare, finance, transportation, supply chain and other industries.
• UN/EDIFACT Executive Guide – United Nations global EDI standard for computer-to-computer exchange of business documents such as purchase orders, invoices and customs declarations.
• What is a MESSAGE QUEUE and Where is it used? (YouTube)

Device and industrial connectivity

IoT is not one separate interface category. Connected devices may use request/response, publish/subscribe messaging, streams, command/control or other patterns depending on constraints such as bandwidth, power, connectivity and scale. These are useful starting points:

• Blogs/An Overview of Industrial Communication Protocols
• MQTT (Message Queuing Telemetry Transport) – lightweight publish/subscribe messaging designed for IoT and constrained or unreliable network environments.
• OPC UA Overview – industrial interoperability across sensors, actuators, control systems, enterprise software and cloud integration, including IIoT and M2M.
• Which IoT Protocol Is Best (LoRa, Thread, MQTT, CoAP & Matter Explained) (YouTube)
• MQTT Tutorial: An Easy Guide to Getting Started with MQTT

Agent interfaces

• Model Context Protocol
• Introducing the Model Context Protocol
• Agent experience: How to design products that agents can actually use
• The New Front Door – Agents Don’t Click
• MCP July 28, 2026 Specification Update – current major MCP release and the move to a stateless protocol core.
• MCP Tools – how servers expose discoverable functions to AI applications.
• A2A Protocol – current documentation for agent-to-agent interoperability.
• A2A v1.0 announcement – why the 1.0 release matters and how A2A complements MCP.

Product-manager-oriented explainers

• IdeaPlan, API Design for Product Managers (This is a great writeup, but even though only from February, 2026, it’s already slightly out of date. They say, “Your API is a product with its own users (developers).” This is true. but increasingly, it’s going to be about AI agents as well.)
• Every Type of API Simply Explained in 9 Minutes! (YouTube)
• Department of Product, APIs Explained for Product Managers
• Department of Product, Webhooks Explained for Product Managers
• Smashing Magazine, Understanding API-Based Platforms
• REST APIs for Product Managers
• Unified.to, MCP Guide for Product Managers
• Snyk, MCP Servers for Product Managers

How to use this guide

A PM does not need to read every specification front to back. Start with the taxonomy from Part 2, identify the interaction you are trying to understand, read one PM-oriented explanation, then go to the primary specification when a decision depends on precise behavior.

The companion code from Part 3 is the hands-on layer. The goal is not certification in protocols. It is enough fluency to recognize the decision, ask better questions, and know where to go deeper.

In this part 4 of 5 for the series, we’re going to look at the “So What?” of digital connectivity among products.

The product goal and product manager’s role with regard to things like products’ technical communication structures is to make sure the team has correctly defined the interaction the product needs. This includes customer and business consequences that will help engineering choose implementation options. This way, engineers can better determine what interface patterns and technologies are worth consideration.

There’s also a second-order goal. Product needs to determine if something should become a long-term supported product surface at all. Whether it’s an external API, webhook, event stream, device interface or something else, the moment there are external dependencies on these things, they become long-term promises involving versioning, reliability, support and so on. There are clearly costs to this, and Product, likely along with Finance and Engineering, needs to have those costs and benefits modeled.

[Read more…]

In this part 3 of 5 for the series, we’re going to look at the “How”of digital connectivity among products.

This will be a deeper dive, and links to some interactive tools and exercises will be included below. A taxonomy of anything is useful until it becomes a giant set of overwhelming boxes. So instead, one way to illustrate the differences for this set of things to use examples and show where the parts can be applied in useful ways. This will ideally be more effective than just a basic chart alone. Several practical test examples will be built and linked into this article so. you can manipulate some of these things yourself if you like.

Let’s pretend we have a logistics service. We’ll call it ScottsHouseOfLogistics. Because no one is likely going to bother getting that URL and this way I have a place to put all the stuff I want to sell. Ideally we’ve got customers. We’ll also have packages, drivers, delivery stops, tracking events and support cases. Our overall realm will be the same. What changes are the interaction scenarios.

We won’t just pick a solution and use that function repeatedly. These tools aren’t necessarily competitors. Several may coexist because they’re solving different interaction problems. Any PM that’s been around awhile has seen choices made based on what “we have on hand and know right now.” That might be a bad idea, but often can be the best course of action. You use the tools you have and know. But is that always the best practice? Unlikely. This isn’t about product managers learning to call every one of these shots. Still, if it’s your product and you’re on the hook for success / failure, maybe P&L, then you should at least be asking the right questions or understand what your colleagues are telling you about choices.

[Read more…]

In this part 2 of 5 for the series, we’re going to look at the “What & When”of digital connectivity among products.

The fastest way to make this whole topic area a confusing mess is to just list out technology definitions. This might not be the best way to learn how things work. Though we do need to quickly visit buzzwords like REST, GraphQL, gRPC, webhooks, MCP, and some others. They don’t all sit at the same conceptual level, and they’re not interchangeable answers to one problem. What we’re going to do in this article series is look at some use cases and a handful of popular options. And in the very next installment, some live examples and work products of things you can try yourself if you want to dive in a bit. Again, we’re not trying to be coders. We won’t be experts. But sometimes just seeing something actually work can bring those Aha moments we can keep with us over time vs. just spewing buzzwords. It’s the difference between sleepily scanning another bullet point list vs. “oh, yeah… I see how that works now.” (We are going to ask some questions and run some lists first before we get to the fun stuff though.)

A useful direction in this space can perhaps start by asking ”What interaction are you trying to create?” Then look at technologies that can do it. Or you can always ask your dev, architect or AI team members. Yeah, I said it. “AI team members.” While I believe in the “mostly sort of trust, but verify” framework here, at this point, I’ve found our still somewhat new AI friends rise to that level. Maybe they still have that fresh new AI smell, and we still need to sort out best ways to use them, but there you go.

Diving deeper now, we can see things like OpenAPI and AsyncAPI can describe interfaces. OAuth 2.0 handles delegated authorization. JSON and Protocol Buffers represent data. SDKs package interfaces for developers. HTTP, WebSockets and MQTT move information. All these things matter, but they are not all separate product interaction categories.

[Read more…]

In this part 1 of 5 for the series, we’re going to look at the “Why” of digital connectivity among products first. Then we’ll dig into some details including several real-world hands-on examples.

Why APIs and Interfaces need a fresh high-level consideration.

We know the role “Digital Product Manager” has always been ambiguous. Still, ideally any Product Manager should have something to do with market awareness, looking around corners, and so on. And this includes the building blocks we may choose. A lot of us may have come from some kind of coding background, but certainly not always. In any case, even if we don’t, (or shouldn’t), need to be expert developers, we should understand how our products are stitched together.

[Read more…]