Notifications
Clear all
How To
4
Posts
3
Users
0
Reactions
4
Views
Topic starter
I have a workflow configured where:
A caller requests an appointment time.
If the requested time is available, the AI agent (via callin.io) books the appointment.
If the time is unavailable, it suggests alternative available times.
However, I'm encountering two primary issues:
The workflow is not proceeding past the filter applied after the “Make a Basic Auth Request” step.
When I examine the error, it returns:
json
{"statusCode":401,"message":"Invalid JWT"}
Despite this, I am using my GoHighLevel (GHL) API key, which I have confirmed is correct.
Additionally, when the workflow attempts to find similar times, it sometimes proposes random times that are not actually available.
Could you assist me in understanding:
Why the error message indicates “Invalid JWT” when I'm using my API key?
What could be causing the workflow to halt at this particular stage?
Why it's suggesting unavailable times when offering alternative options?
Posted : 26/11/2024 6:28 am
Hi there,
Were you able to resolve this? I'm encountering the same error.
Please share your solution.
Posted : 09/01/2025 4:14 pm
Topic starter
The problem stemmed from the HTTP request. When setting up a new keychain, the username and password fields at the top were auto-populating. It's important to leave these fields empty. Kindly attempt this and inform me if it resolves the issue.
Posted : 10/01/2025 12:38 pm
Hey there, you mentioned “When creating a keychain, the username and password fields at the top were autofilling. These fields need to be left blank.” and I don’t see anywhere that has a username or password to leave blank. What am I missing?
Posted : 22/01/2025 5:38 pm