Connectivity Masterclass: Webhooks & HTTP Requests (Part 5)

· Manuel · 28 min read · Automation

You have reached the level where "No-Code" usually breaks. Most users hit a wall when they want to connect to a specific tool (like a niche [Real Estate](/resources/blog/real-estate-lead-qualification-bilingual-bpo-teams) CRM or a legacy ERP) and they don't see a pretty logo in the library. They say: "Oh, n8n doesn't support X."

Wrong. If a software exists on the internet in 2025, it almost certainly has an API. And if it has an API, n8n supports it better than any other tool on the market.

In Part 5, we are taking off the training wheels. We are going to learn how to speak the language of the web: HTTP. We will cover Authentication, Headers, JSON payloads, and how to reverse-engineer any API docs.

Related Reading

  • [BDR vs SDR: What's the Difference and Which Do You Need?](/resources/blog/bdr-vs-sdr-difference-which-do-you-need)
  • [How to Build a Remote Sales Team in 2025](/resources/blog/how-to-build-remote-sales-team-2025)
  • [Lead Generation on Autopilot: Converting Leads in 60 Seconds (Part 2)](/resources/blog/n8n-lead-generation-autopilot-part-2)

    • The HTTP Request Node: The Skeleton Key

    This single node is more powerful than the other 500 nodes combined. It allows you to simulate a browser or a server making a request.

    The 4 Verbs You Need to Know: 1. GET: "Give me data." (e.g., Get list of contacts). 2. POST: "Here is new data." (e.g., Create a contact). 3. PUT/PATCH: "Update this data." (e.g., Change status to 'Sold'). 4. DELETE: "Destroy this data." (e.g., Remove contact).

    If you understand these four words, you can rebuild the entire internet infrastructure.

    Authentication: Getting Through the Door

    APIs are protected. You need a key. n8n handles auth beautifully with "Credentials".

    Types of Auth:

  • Basic Auth: Username/Password (Old school).
  • Bearer Token: A long string you put in the Header (Most common).
  • API Key: Specific query parameter.
  • OAuth2: The "Sign in with Google" flow. n8n handles the token refresh automatically.

    • Pro Tip: Never hardcode your API keys in the URL. Use \

    Real World Example: Connecting to a Random API

    Let's say you use a niche CRM called "RealtorFlex" (fictional). It has no n8n node. You find their API docs: \

    Webhooks: Receiving Data (The Reverse)

    HTTP Requests are for sending data. Webhooks are for receiving it. We covered this in Part 2, but let's go deeper.

    Security: Anyone can post to your webhook. How do you stop hackers? Header Validation. In your Webhook node, check for a specific header (e.g., \