I'm encountering an issue with the Contact Get tool I built, which is integrated with GoHighLevel. The tool is designed to pull lead information based on their phone number, and it works perfectly when I run it outside of a workflow. However, when I try to run the same tool inside a workflow, it fails and throws an error indicating that the email field is missing or empty. It seems like the tool is expecting an email input when used inside the workflow, even though it's configured to look up contacts by phone number — just like it does successfully outside the workflow. Can you help me understand why this behavior is occurring, and how I can ensure the tool works within the workflow using only the phone number as input? Let me know if you need any logs, screenshots, or workflow IDs for reference.

GoHighLevel workflows require either a phone or email to identify a contact at the trigger stage; while your tool works with just a phone outside the workflow, inside a workflow you must ensure the phone number is included and correctly mapped in the trigger to avoid the “email missing” error.

And how do I ensure that? I do not see anywhere inside the workflow to edit the logic?

Hi, First off, we want to sincerely apologize for the delay in getting back to you. We understand how frustrating it is to wait - especially when you're counting on us - and we owe you a clear explanation of what’s been happening and how we’re addressing it. Over the past few weeks, we've seen a significant increase in support requests. While this reflects exciting growth, it has also stretched our small team and exposed some real challenges in scaling our support operations. To improve your experience, we’ve taken a step back to reassess our approach. Here’s what we’re implementing: - Smarter Support Through Automation: We’re investing in our AI support systems to help you resolve issues more efficiently. Soon, our support bot will offer expanded capabilities, making it easier to access accurate, instant help—particularly for common or repetitive queries. - Expanding the Support Team: To meet growing demand, we’re adding 2–3 new team members focused on managing support volume and improving response times. - Prioritized SLAs for High-Usage Accounts: We’re introducing service level improvements for users who are growing with us: - Accounts with usage over 1,000 minutes/month will receive prioritized support. - For all general inquiries, we’re establishing a standardized 48-hour response time. We’re confident these steps will lead to faster, more reliable support and help us better serve you as you grow with us. Also, in case you still need help with this ongoing ticket, do let us know, and we will help you get this resolved as soon as possible. Thank you for your continued patience and for being part of our journey. Warm regards, Vapi Team