I’m moving an automation from Zapier to Make and I’m struggling to replicate a specific Discord feature.
My Setup:
Trigger: A Baserow Webhook (Advanced plan) that fires when a row enters a specific view.
Module 1: A “Custom Webhook” listener in Make to catch the Baserow data.
The Goal: Send a formatted message to Discord that includes a custom name, a custom mascot avatar, and an embedded image from the Baserow record.
The Problem: In Zapier, the Discord module has built-in fields for “Bot Name,” “Bot Icon,” and “Image URL.” I can’t find these equivalent fields in the standard Make Discord module.
Following some advicefor good ol’ Google Gemini (ugh), I’ve added a HTTP “Make a request” module (between the Baserow webhook and Discord modules) to send a POST request directly to a Discord Webhook URL. I’ve successfully set up the Webhook in Discord with my mascot, but I’m lost on the “Body” configuration in Make.
Where I’m stuck:
Gemini is trying to have me select or fill out options that are not present in the module’s configurations.
Does anyone have a better approach to this? I am a free-tier user.
The good news - you already have the right approach.
Here’s how to configure the HTTP module:
URL: your Discord webhook URL + ?wait=true (without this, Discord always returns 204 regardless of whether the message was actually saved – wait=true forces a proper response and surfaces any errors) Method:POST Body content type:application/json Body input method:JSON string Body content:
Replace the static values with your Baserow bundle mappings:
username → your custom bot name (equivalent to Zapier’s “Bot Name”)
avatar_url → public URL of your mascot avatar (equivalent to Zapier’s “Bot Icon”)
content → text above the embed, or remove it entirely if you only want the embed
embeds[].title / embeds[].description → whatever fields from Baserow you want to display
embeds[].image.url → map your Baserow image URL field here (equivalent to Zapier’s “Image URL”)
One thing worth knowing: username and avatar_url only work on webhook requests - they don’t exist on the standard Discord module in Make, which is why you need the HTTP module in the first place.
Sample body (you can paste it to your HTTP module and give a try)
So I tried that out and I keep getting an error. Gemini is telling me its because my description (mapped from Baserow) has line breaks and suggested I use the code below. Then it suggested I use a “transform json” module. However, I once again run into the issue of the Ai wanting me to change things that are not there.
I got the previous suggested setup to work (the one without the json module), but it was adding \n\n into my messages and messing up my discord header the “### header here”. I assume its because it it had the \n attached in front of it?
Hey everyone!\n\n### Lets go and work! Bold text worked!\n\nTime to get a new module?\n\nLet’s use up out 1000 free credits testing a module that don’t work! YAY!
Ask an LLM (or use my example) to generate a sample JSON body, then change the Body input method in the HTTP module from JSON string to Data structure.
Make.com will ask you to select or create a data structure – use the sample generated earlier (or use sample JSON which I provided earlier) with the Generate function to save time.