Hi,
I am implementing this signature pad. However, by minute 13:03 (from the video), you got the ID from Workflow Action, but it does not appear in my weweb editor.
how can I resolve this?
If you want to have document signing tool , I suggest docuseal , recently I’ve integrated it in weweb with Xano backend.
@abbasdezaki Using custom Weweb components for the form builder and embedded parts? Or straight from html elements with JS?
for whatever reason my strokes arent lining up, they are way off the signature pad
I did in embedded , I think you be able to use weweb component via api , but it adds up tons of complexity.
Hi Jean-Philippe, how is it going? I followed your tutorial and it worked like a charm… in desktop. I can’t make it work decently in mobile/touch devices, which are the most probable devices in which users will make their signatures.
I have a form with some fields (inputs and selects) and at the end, the canvas. If I load the form and go directly to the canvas I can draw in it, but after I modify any of the other fields the canvas goes back to white, in the other hand if I start the form from the other fields (expected behaviour) the canvas is totally unresponsive.
Any ideas? I would really appreciate your help,
Thanks in advance!
Hey @javierlaborde 
I can’t reproduce your issue. It’s working ok on mobile on my end with this implementation.
Are you using native WeWeb inputs and select? Any workflows attached to the components that could affect the signature pad?
Any way for me to reproduce? Or maybe a video of your setup can be enough 
Yes, all inputs are native from WeWeb, I have a `onPageLoad` workflow that loads some data based on a url parameter, I don’t know if that might be messing it up. Besides that my configuration is pretty straight forward, just a couple of inputs/selects, texts and this canvas at the bottom. The canvas (HTML element) as a component and the component itself with a workflow `onMounted` that triggers the custom JS which is exactly the same as you except for the color of the stroke.
You can see my issue in this video https://deveyxuvjmyiopwqqanz.supabase.co/storage/v1/object/public/otros/WhatsApp%20Video%202026-03-18%20at%2016.49.43.mp4
Thanks in advance,
I see. I could reproduce a similar bug when the pad was being resized. But I’m not too sure how to go about it.
I’ve created a v2 using the same library, but as a custom component (which is more robust). I couldn’t reproduce the bug with this new version. Can you give it a try and see if it meets your needs? You can fork and import the component in your project.
Hi there.
Thanks a lot, really. This solved the problem, plus made the component itself much more friendly now that has all the properties exposed as parameters.
The component is working flawlessly both in desktop and mobile/touch devices.
Again, thanks,
Have a nice day 