What is your goal?
Connect Heygen to a Scenario
What is the problem?
When I first establish a connection using API, it goes through. I then go to character Settings where I am constantly getting an error - The request failed due to failure of a previous request. Remote procedure timed out. and Shows failed to load data.
It also now changes the connection status and show error - The request failed due to failure of a previous request.
Also uploaded the error screenshot.
What have you tried so far?
I have tried changing and regenerating APIs of Heygen unlimited times.
Added balance to Heygen. Also using a monthly creator plan on Heygen.
I even tried connecting an individual heygen in a new scenerio.
Screenshots: scenario setup, module configuration, errors
Hi @Shami_Bawa,
I was able to replicate the same behavior on my end. It appears the issue occurs while the Make connector is trying to fetch the avatar list from HeyGen. The “The request failed due to failure of a previous request” message is typically a dependent request error, meaning the subsequent request to load the avatars cannot complete because the initial request did not finish successfully (resulting in a timeout).
As a workaround, I tested the same flow using the HeyGen HTTP API, and it worked successfully. You can use the Create Video API endpoint via the HTTP module instead of the native HeyGen module. I’m attaching screenshots of the working setup for reference.
Hope this helps!!!
Best Regards,
@Mohamed_Jahar
Thanks for suggesting the way around. That means the native Heygen Module in Make is not working.
You got the “Remote procedure timed out”, this usually happens when the task (such as retrieve a complex avatar or voice configuration) is too heavy to complete within Make’s default time limit .
Thanks a lot for responding. Well I have only 1 Avatara, not sure if that is heavy, if it is wondering what does the module even support?
Hello,
HeyGen module is developed and maintained by 3rd party.
You can contact with them and let know about bug you found.
https://www.make.com/en/integrations/heygen
Have a nice day,
Michał
Michał Serio!!! I would expect Make as a platform owner would communicate with the plugin creator. You paid them to develop this module and now you are asking the community to do your job! LOL Its not community responsibility to search the developer contact detail they read! I’m taking a SS of this and posting to Google as bad practice from make.com
I don’t think you understand how this works mate. Any one can create apps and Make doesn’t pay us for it. It’s the app creator that handles support and if there is an issue with the app, you contact the creator directly, cause Make doesn’t have access to it.
I was not aware of this. If that’s the policy they should make all the contact details visible on the page of integration. This is not customer centric thinking…very rarely anyone will make effort and find contact details to the integration developer. This makes platform not suitable for many potential users, and tor reliable when you have frictions of that type with support…
Please keep in mind that Community is owned and maintained by Make but besides few Make employees we, users, are voluntarily helping people here.
If you have problem with the platform or the app you can always contact Make.com support directly.
Or try to get help here- especially, if your question isn’t problem related but rather “I need help question” but you must be aware of fact we are community and don’t have all the tools/ resources.
With 3rd party apps you have also additional way of communication- direct contact. But it does not mean that Make.com support won’t contact dev directly, as soon as they get noticed about error.
Please keep in mind that Make.com offers right now over 3000 pre-build apps. It is almost impossible to keep them all monitored 
No! 3rd party apps are created and maintained by 3rd party developers without any compensation from Make.
Anyone can create an app and publish it within Make.
If app is created and maintained by 3rd party it is clearly stated in app information.
Many developers include their info in modules directly but they are not obliged to do so.
But this info is always listed in the app directory, as shown on my previous post.
And they are visible.
I think there is a little misunderstanding here. Community is not the same as support. We are here voluntarily helping other users with Make. But Support is avaliable here:
Have a nice day!
If it’s still failing after reconnecting, I’d also try creating a brand new connection instead of reusing the old one. I’ve had a few integrations where the existing connection looked fine but was actually holding onto an expired token. Recreating it fixed the issue.
