TL;DR: This webinar shows how the BoldSign eSignature Skill helps generate a production-ready eSignature integration using AI, including document sending, embedded signing, and real-time webhook tracking, all connected end-to-end.
In this session, Gayathri, Software Developer at BoldSign, demonstrated how developers can quickly build a complete eSignature integration using AI by adding workflow context through the BoldSign eSignature Skill.
Instead of manually fixing gaps in generated code, teams can create reliable, end-to-end integrations faster, covering document sending, embedded signing, and webhook handling.
If you missed the live session or would like to watch it again, the recording is available on this page and can also be accessed on our YouTube channel.
Webinar recap
The session highlighted a key challenge. While AI can generate code quickly, building a production-ready integration still takes time due to missing connections between steps.
To demonstrate this, the session began with a basic AI-generated ASP.NET Core MVC application. The application ran successfully, but it exposed common gaps such as incomplete webhook verification and disconnected workflow logic. Each issue was fixable, but together they created delays that often turn a simple task into a longer development effort.
Next, the same prompt was used with the BoldSign eSignature Skill, which adds workflow-level context to AI generation. This resulted in a fully connected application that included:
- Document sending
- Embedded signing within the application
- Real-time webhook tracking with proper verification
- Automatic download of signed documents and audit trails
This clearly showed how adding workflow context transforms generated code into a complete, production-ready implementation.
The session also compared email-based signing with embedded signing. Email-based flows work, but they interrupt the user journey. Embedded signing keeps users inside the application, creating a smoother signing experience and improving completion rates.
Another key improvement was webhook handling. Instead of manually checking document status, the application received and processed events such as Sent, Viewed, Signed, and Completed in real time. This allowed the system to automatically trigger actions like downloading signed documents without additional effort.
By the end of the session, a complete workflow was built live. This included the UI, document sending, embedded signing, webhook tracking, and post-signing automation. It was not just a demo, but a solid foundation for a production-ready implementation.
Watch the webinar
Timestamps
[00:00] Welcome and session introduction
[01:17] Session goal and agenda
[02:19] Poll: What slows down API and AI-assisted integrations?
[03:14] Generating an eSignature integration with a basic AI prompt
[07:10] Reviewing workflow gaps in the generated application
[09:13] Introducing BoldSign eSignature Skills
[10:02] Installing and configuring BoldSign AI Skills
[11:25] Running the same prompt with workflow context
[14:55] Reviewing the generated production-ready workflow
[15:53] Building and testing the application
[16:21] Adding API credentials
[17:23] Configuring webhook endpoints and verification
[18:39] Running the application and sending a document
[20:24] Limitations of traditional email-based signing workflows
[20:48] Extending the application with embedded signing
[22:22] Configuring public URLs for embedded signing
[23:15] Embedded signing experience demonstration
[23:45] Real-time webhook tracking and document processing
[24:58] Recap: What was built during the session
[25:34] Benefits of using BoldSign AI Skills
[26:35] Additional resources and documentation
[27:02] Poll: Feedback on BoldSign eSignature Skills
[27:46] Staying connected and product resources
[28:24] Final takeaways and closing remarks
[28:56] Q&A
Key takeaways
- AI needs workflow context to generate production-ready eSignature integrations.
- Embedded signing improves user experience and completion rates.
- Webhooks enable real-time tracking and automation.
- The BoldSign eSignature Skill helps reduce development time and complexity.
Q&A
I may have missed this, but why is the same prompt being used again?
We used the same prompt intentionally to show the difference between using the BoldSign eSignature Skill and not using them. With skills, the workflows (including webhooks) work correctly and more reliably.
Do you provide services to build a signing webhook for users?
Yes, BoldSign provides APIs and webhooks to receive real-time signing events (sent, viewed, signed, etc.). You can use them to automate workflows in your application.
Final takeaway
Building a production-ready eSignature workflow doesn’t have to be time-consuming or complex. With the right workflow context, teams can move from basic code generation to a fully connected, reliable implementation much faster.
The BoldSign eSignature Skill helps bridge the gap between code that looks correct and code that works in real-world scenarios, enabling faster development, fewer errors, and more predictable delivery.
For a deeper understanding, refer to the BoldSign blog on using the eSignature Skill in GitHub Copilot.
Ready to try it yourself?
Start with a free sandbox account, explore the BoldSign eSignature Skill, and build your first eSignature workflow integration with AI.
Build faster, launch sooner, improve reliability, and deliver a smoother signing experience that helps you close deals faster.
