What is your goal?Need an experienced Make.com automation engineer to troubleshoot an existing Retell AI workflow. The scenario already books appointments through Microsoft 365 Calendar, sends Outlook emails, Twilio SMS and updates Google Sheets. The webhook receives the correct data, but client fields are not flowing correctly through the AI Toolkit into downstream modules. I need someone to review and fix the existing scenario, not rebuild it from scratch.
I can surely assist you with this
email me so we can discuss this in detail
seth “at” cisinlabs . com
Hey @Joseph_Linco,
Sounds like the data’s arriving fine but breaking inside the AI Toolkit handoff — classic mapping gap.
When Retell’s webhook hits Make, the AI Toolkit often nests client fields inside a JSON string or a sub-array, so the downstream modules can’t see them as clean variables. I’d check whether the Toolkit output needs a Parse JSON module before mapping, and confirm the field paths haven’t shifted (Retell sometimes wraps everything under `call.metadata` or `dynamic_variables`). Once the structure’s mapped explicitly, your Outlook, Twilio, and Sheets modules should populate correctly without touching the booking logic.
Happy to jump in and fix this for you I troubleshoot Retell/Make scenarios like this regularly.
───
Website: https://www.pathfinderautomationsolutions.com
Upwork: https://www.upwork.com/freelancers/pathfinderautomate
Book a call: Calendly
Hi Joseph,
This is exactly the kind of troubleshooting work we do at Flowbird Ltd, and we’re also a Make Partner.
From what you’ve described, it sounds like the webhook is receiving the correct payload, so the issue is likely within the AI Toolkit field mapping or how variables are being passed between modules. We regularly debug existing Make scenarios and focus on fixing the root cause rather than rebuilding workflows from scratch.
Happy to take a look and get your current scenario working as intended. Feel free to DM me or email me at [email protected].
Many Thank,
Roshan
Hi @Joseph_Linco ! I would love to help you with your set up. AI toolkit is still in beta in some parts and you may need to find a work around.
We are a small team of make.com experts and have developed plenty of complex integrations. This project should not be a challenge to us.
If you are interested we would love to help you, you can schedule a call in here: Automation Discovery Call | Felipe Saucedo | Cal.com discovery or check our website www.aspirity.com
I should be able to help you with this. I’ve got 2+ years of experience building automations on Make, and have worked with Retell too. DM and we can discuss specifics.
I would not rebuild this first. The fastest diagnostic is a field-contract table across three points:
Retell webhook raw payload
What exact field names arrive from Retell for client name, phone, email, appointment time, and any dynamic variables?
AI Toolkit output
Does the AI Toolkit return those fields as separate mapped values, or does it wrap them into one text/JSON string that downstream modules cannot address directly?
Downstream module requirements
For each target module, list the required field path:
Calendar event title/time, Outlook recipient/body fields, Twilio phone/body fields, and Google Sheets column names.
The likely break is between step 1 and 2: the webhook has the data, but after the AI Toolkit the fields are no longer exposed as stable Make variables.
The smallest proof test:
If Sheets receives the fixed fields correctly, the issue is AI Toolkit output shape / parsing, not Retell or the downstream apps.
If Sheets still receives blanks, inspect the bundle right before Sheets and compare the actual field paths against what the module is mapped to.
Hi Joseph, Welcome to make community 
.
I’d be happy to take a look.
From your description, it sounds like the webhook is receiving the expected payload, but something is breaking between the AI Toolkit output and the downstream mapping. I’ve worked on debugging similar issues involving Make.com, AI agents, webhooks, API integrations, and production workflows where the problem wasn’t the webhook itself but how data was being transformed or referenced further down the scenario.
I generally prefer fixing existing automations rather than rebuilding them, so my first step would be tracing the data through each module to identify exactly where the mapping is failing before making any changes.
If you’re comfortable sharing the scenario (or screenshots together with a sample execution), I can review it and let you know where the issue is.
If it looks like a good fit, we can jump on a quick call and get it resolved.
You can also reach me directly:
Call: Click here to book a walk through call session.
Portfolio: Click here to view my website porfolio.
[email protected]
Looking forward to hearing from you.
Joseph, this sounds less like a Retell webhook problem and more like a bundle/shape problem after the AI Toolkit step.
I would debug it by:
If you still need someone, I can do a fixed $100 troubleshooting pass: review the existing scenario, find the broken field path, add the Parse JSON / Set variable guards, and give you a short before/after note. No rebuild unless the scenario truly needs it.
DM me a sample webhook payload plus one failed execution screenshot and I can confirm fit.
Hi @Joseph_Linco - this sounds like a contained Make mapping/debugging job, not a rebuild.
I’d check the Retell webhook payload against the actual bundle coming out of the AI Toolkit module, then trace which fields are being passed into Outlook/Twilio/Sheets. Usually this kind of issue is either the AI Toolkit returning a different structure than the downstream modules expect, or the later modules are mapped to an older run/output shape.
I work on Make/API/AI workflow fixes like this and could help troubleshoot the existing scenario if you’re looking to hire someone for it.