Behind every automation, apps are passing data to each other. This module explains how that conversation works, so that when a workflow breaks or a tool has no ready-made integration, you know what is going on and how to fix it.
An API is the set of rules an app exposes so other software can ask it for data or tell it to do something. Each call is an HTTP request made of a URL, a method such as GET to fetch or POST to send, headers, and sometimes a body. The reply comes back with a status code and a body, and that body is almost always JSON, a simple text format for structured data that you will read and edit constantly.
Webhooks flip the direction. Instead of your workflow asking an app again and again whether anything changed, the app sends a message to a URL of yours the moment an event happens. In tools like n8n, Make, and Zapier, a webhook is one of the most common ways to start a workflow, and the HTTP Request step lets you call any API, even when no built-in connector exists. Watch the lessons in order, then continue on to No-Code Automation Platforms.
What an API is and how to read its documentation, the four parts of an HTTP request, status codes and responses, and how webhooks differ from polling.
What JSON is, why it is the standard format for sending data between apps, and how its syntax works, with examples you can follow along.
A ground-up look at REST APIs and how to use the HTTP Request node to connect a workflow to almost any service.
A longer hands-on walkthrough that puts the module together: building a first workflow, calling APIs with HTTP requests, and triggering workflows with webhooks.