Summary  
This chapter explains how to construct and send HTTP requests, covering request methods (GET, POST, PUT), key components (URL, method, headers, body), and common authentication techniques for interacting with APIs.

General domain of usage  
E-commerce inventory management

HTTP requests let Zapier **actively communicate with external systems** through APIs. While webhooks (Catch Hook) receive incoming data, HTTP requests **send outgoing requests**, enabling interaction with services even without native Zapier integrations.

Definition

### Core Concept

The focus shifts in the opposite direction, sending data out.

- **Catch Hook**: like having a mailbox, you receive what others send;

- **HTTP Request**: like making a phone call, you actively reach out to other systems.

HTTP requests allow you to either ask for information or instruct another system to perform an action. If a service exposes an API, and most modern services do, you can connect to it directly from **Zapier**.

**This is one of the most commonly used features in automation.** Understanding HTTP requests dramatically expands what you can build and integrate.

Note

### Components of an HTTP Request

Every HTTP request has four main components. The first is the **URL (endpoint)**, the address you send the request to, where the API lives. APIs expose different endpoints for different actions.

```
# https://api.example.com/contacts     → Working with contacts
# https://api.example.com/deals        → Working with deals
# https://api.example.com/companies    → Working with companies
```

URL parameters: For GET requests, parameters often go in the URL:

```
# https://api.example.com/contacts?email=john@example.com
```

Everything after `?` tells the API what specific data you want. The API documentation specifies which endpoints are available and how to use them.

The next component is the **method**, which defines the type of request, such as GET, POST, or PUT. In Zapier, you select this from a dropdown, and it must match what the API expects for the action you are performing. The documentation clearly states which method to use for each endpoint.

**Headers** contain metadata about the request, including authentication details and the data format being sent or received.

And the last one is The actual data you're sending. Applies to POST and PUT requests (GET typically has no body).

If the API expects specific field names, you must match them exactly. Documentation tells you required fields and their names.

Which HTTP header tells the API what format your request data is in?

Learn how Zapier works and how to build automations from simple one step zaps to advanced multi step workflows. The focus is on core automation concepts such as triggers, actions, filters, paths, and data formatting, and how they work together in real scenarios. You will gain hands on experience chaining actions, shaping data, and applying conditional logic to control workflow behavior. The course also covers webhooks and scaling strategies, enabling you to design reliable automations for real world use.

Making HTTP Requests

Core Concept

Finding HTTP Requests in Zapier

Components of an HTTP Request