Make.com Calendar Automation Setup
Budget: £10 – £20 GBP
I already have an AI chat bot running on Buildmyagent.io, and I want it to offer live booking slots without double-booking me. What I need is a Make.com scenario that continuously checks the current date-time, waits at least two hours before the first possible slot, and then reads my Google Calendar (respecting its native time zone) to pull only the genuinely free periods.
Here’s the workflow I picture: a webhook from Buildmyagent.io pings Make; Make instantly grabs “now”, adds a two-hour buffer, queries Google Calendar for the rest of the day (and following days if needed), filters out busy blocks, and sends the first few open slots back to the chatbot in JSON. The scenario must run reliably even if no webhook arrives—so a timed trigger that refreshes availability on a rolling basis is essential.
All I’m looking for is the Make.com portion: modules configured, relevant filters / functions applied, and clear mapping back to my chatbot’s expected payload.
Deliverables
• A fully built Make.com scenario, documented node-by-node
• Test proof (video or screenshots) showing the bot receiving correct slots
• Brief hand-off notes so I can tweak the buffer or slot length later
If you’ve handled Google Calendar and dynamic time calculations inside Make before, this should be a quick win for both of us.
I have uploaded the Make.com JSON files which are not working for me, they may help you identify my mistakes
Here’s the workflow I picture: a webhook from Buildmyagent.io pings Make; Make instantly grabs “now”, adds a two-hour buffer, queries Google Calendar for the rest of the day (and following days if needed), filters out busy blocks, and sends the first few open slots back to the chatbot in JSON. The scenario must run reliably even if no webhook arrives—so a timed trigger that refreshes availability on a rolling basis is essential.
All I’m looking for is the Make.com portion: modules configured, relevant filters / functions applied, and clear mapping back to my chatbot’s expected payload.
Deliverables
• A fully built Make.com scenario, documented node-by-node
• Test proof (video or screenshots) showing the bot receiving correct slots
• Brief hand-off notes so I can tweak the buffer or slot length later
If you’ve handled Google Calendar and dynamic time calculations inside Make before, this should be a quick win for both of us.
I have uploaded the Make.com JSON files which are not working for me, they may help you identify my mistakes