Connect your electronic signature to the tools you use every day — with simple code or with no code at all. Automatic storage of signed contracts, instant notifications for your team, CRM integration, and full automation through Zapier, Make and n8n. And if you want complete control, everything is available through the REST API and Webhooks.
Ready native integrations, no-code connectors and an open API. The status is stated honestly on every card: Available now, or Through Zapier / Make / API, or Coming soon as a native connector.
Saves every signed contract automatically to a folder on Drive as soon as signing completes.
How to connect it: Enable it from the dashboard, connect a Google account and choose the destination folder — the signed PDF is uploaded with its reference as soon as the event signature_request.completed.
Uploads signed contracts to a Dropbox folder organised by reference and date.
How to connect it: A native connector is being released. Until then, connect it today via Zapier or Make, or directly with the Webhook and then GET /download.
Automatic archiving of signed contracts in OneDrive or SharePoint.
How to connect it: A native connector is coming soon, and it is available now through Zapier or Make, or by calling the API directly after each completed signature.
Sends a notification to your team channel the moment any request finishes signing.
How to connect it: Create a Zap with a "signing completed" trigger and a "Slack message" action. Or receive the Webhook and forward it to your channel's Incoming Webhook.
A notification card in a Teams channel on every signing or identity verification event.
How to connect it: A native connector is coming soon; available today via Make, or a Webhook pointed at the Teams channel's Incoming Webhook.
Notifications, signing invitations and automatic reminders for every party — built into the platform.
How to connect it: Enabled by default for every request. Control the reminders through reminders in the request body, and enable or disable the messages for each template from the settings.
Attaches the signed contract to the deal and updates its stage as soon as signing completes.
How to connect it: A Zap with a "signing completed" trigger and an "attach file / create note" action on the deal, connected through metadata.order_id or reference.
Updates the records and attaches the signed document to the opportunity or account automatically.
How to connect it: A native connector is coming soon; it is available now through Zapier or Make, or by making a REST call from Apex or Flow to fetch the document and link it.
Moves the deal along the pipeline and attaches the signed contract to it.
How to connect it: Make scenario: a Webhook module captures the event, then an "attach file to deal" action in Pipedrive after downloading the PDF.
Connects Wthaiq events to thousands of apps without writing a single line of code.
How to connect it: Use "Webhooks by Zapier" to receive our events as a trigger, then choose any action in your favourite apps. No code and no hosting.
Visual scenarios that capture the events and run sequential steps automatically.
How to connect it: A Webhook module receives the event, and an HTTP module calls GET /download to fetch the PDF, then any destination module you choose.
Self-hosted open-source automation, with full control over the data flow.
How to connect it: A Webhook node captures the event and an HTTP Request node calls the API; self-host it or run it in the cloud while keeping your keys with you.
Full programmatic control: creating requests, downloading documents and tracking events.
How to connect it: A unified interface across wthaiq.com/api/v1 with a secret key sk_ (or public pk_ for the browser). Read Full documentation.
Signed real-time events that reach your system as soon as each change occurs in the request.
How to connect it: Subscribe to the events you care about, and verify the header Wthaiq-Signature with HMAC. Read The Webhooks guide.
You do not need a ready-made connector. Everything you see here is built on the same two foundations available to you: Webhooks notifies you in real time, andREST API gives you every document and event. Any system with an HTTP endpoint can be connected.
Subscribe to signature_request.completed at your endpoint, and verify the signature Wthaiq-Signature.
Call GET /signature_requests/{id}/download to fetch the sealed document as a PDF.
Save it to storage, attach it to the customer record, or trigger any internal action — all in under five seconds.
// Webhook endpoint — pushes the signed contract into your system
$payload = file_get_contents('php://input');
$sig = $_SERVER['HTTP_WTHAIQ_SIGNATURE'] ?? '';
// 1) Verify the HMAC-SHA256 signature before trusting the event
if (!wthaiq_verify($payload, $sig, getenv('WTHAIQ_WHSEC'))) {
http_response_code(400); exit;
}
$event = json_decode($payload, true);
// 2) When signing completes: download the PDF and push it to your destination
if ($event['type'] === 'signature_request.completed') {
$sr = $event['data']['object'];
$pdf = $wt->signatureRequests->download($sr['id']);
save_to_drive($pdf, $sr['reference'] . '.pdf');
}
http_response_code(200); // Fast response < 5 seconds# Direct download of the signed PDF over REST
curl https://wthaiq.com/api/v1/signature_requests/sr_3n8Kd2Qa1V/download \
-H "Authorization: Bearer sk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
-H "Wthaiq-Version: 2026-07-01" \
-o "signed.pdf"Tip: Make your endpoint idempotent by deduplicating events evt_ duplicates, and run heavy work asynchronously after responding with 200.
The most requested flows — built in Zapier or Make with a few clicks, without writing code.
signature_request.completed
GET /download
chat.postMessage
The result: the moment signing completes, the contract is archived automatically and your team knows immediately — with no manual follow-up. The reference WTQ-XXXXXX ties everything together.
No for the no-code automation tools: Zapier, Make and n8n capture our events and run the actions with a few clicks, without a single line of code. If you want full control and a bespoke link to your system, the REST API and Webhooks are fully available to you — and the right choice depends on how much customisation you need.
Google Drive and email notifications are natively built in and work today. The Zapier and Make automation tools are available today through Webhooks, and n8n through the API. The remaining connectors — such as Dropbox, OneDrive, Microsoft Teams and Salesforce — currently work through Zapier, Make or the API, and we are working on releasing further native connectors, marked "Coming soon". We do not promise more than what is actually available.
in two ways: receive the event signature_request.completed then call GET /signature_requests/{id}/download to fetch the sealed PDF; or read the field download_url from the request object once its status completes. In both cases you get the document as a PDF in PAdES format, with a public verification reference.
Yes. Every Webhook event is signed with the header Wthaiq-Signature with HMAC-SHA256, and it must be verified with a constant-time comparison before processing, rejecting events older than 300 seconds. There is no separate test mode — every key sk_ live, and the publishable key pk_ Limited in privileges and locked to your domains when used in the browser.
Not a problem at all. Every capability in the platform is available through the REST API and Webhooks, so any system with an HTTP interface can be connected — whether through a no-code tool such as Zapier and Make, or with a custom integration you build yourself. Start from Documentation then connect whatever you like.
Start with a no-code tool in minutes, or build your own integration with the REST API and Webhooks. Everything you need is ready.