Connect Wthaiq with your existing systems.
Connect your e-signature to the tools you use every day: automatic storage of signed contracts, notifications for your team, a link to your CRM, and automation through the Webhook modules in Zapier, Make and n8n. And if you want full control, everything is available through the REST API and Webhooks.
Pick your tool and connect it in minutes.
Ready native integrations, connections through automation tools, and an open API. Each card shows the integration status plainly: Available with a native connector, or Through Zapier / Make / API with a setup you configure yourself.
Storage and documents
5Google Drive
Saves a PDF copy of every completed live signature request to a “Wthaiq” folder in your Drive, automatically.
How to connect it: In one click from “External integrations” in the developer portal, on the Business and Enterprise plans.
Dropbox
Saves a PDF copy of every completed live signature request to the app folder in your Dropbox account, organized by year.
How to connect it: In one click from “External integrations” in the developer portal, on the Business and Enterprise plans.
OneDrive
Saves a PDF copy of every completed live signature request to the app folder in your OneDrive account, organized by year.
How to connect it: In one click from “External integrations” in the developer portal, on the Business and Enterprise plans.
SharePoint
Saves a PDF copy of every completed live signature request to a SharePoint library you choose, organized by year.
How to connect it: In one click from “External integrations” in the developer portal, on the Business and Enterprise plans.
Box
Saves a PDF copy of every completed live signature request to a “Wthaiq” folder in your Box account, organized by year.
How to connect it: In one click from “External integrations” in the developer portal, on the Business and Enterprise plans.
Notifications and teams
3Slack
Sends a notification to your team channel the moment any request finishes signing.
How to connect it: In Zapier: a "Webhooks by Zapier" trigger receives the signing-completed event from an endpoint you add in the developer portal, then a "Send message" action in Slack.
Microsoft Teams
A notification card in a Teams channel on every signing or identity verification event.
How to connect it: A Make scenario: a Webhook module catches the signing or identity event, then a Microsoft Teams module posts a message to the channel.
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.
CRM and sales
3HubSpot
Attaches the signed contract to the deal and updates its stage as soon as signing completes.
How to connect it: In Zapier: a "Webhooks by Zapier" trigger receives the signing-completed event, then a "Create note" action on the deal, matched through the field metadata.order_id or reference.
Salesforce
Updates the records and attaches the signed document to the opportunity or account automatically.
How to connect it: Call the API from Apex or Flow to fetch the document and attach it to the opportunity, or use the Webhook modules in Zapier or Make.
Pipedrive
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.
Automation tools
3Zapier
Connects Wthaiq events to thousands of apps with a no-code setup.
How to connect it: There is no dedicated Wthaiq app in Zapier yet; use "Webhooks by Zapier" to receive our events as a trigger, then pick any action in your favourite apps, with no code or hosting.
Make (Integromat)
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 final document link and its verification reference, then pass the link to any destination module you choose.
n8n
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.
Custom — full control
2REST API
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.
Webhooks
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.
Cannot find your tool? Connect it yourself.
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, and REST 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 get the link to the final document, ready to print or save as 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# Signed contract links over REST (JSON containing final_document_url)
curl https://wthaiq.com/api/v1/signature_requests/sr_3n8Kd2Qa1V/download \
-H "Authorization: Bearer sk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
-H "Wthaiq-Version: 2026-07-01"Tip: Make your endpoint idempotent by deduplicating events evt_ duplicates, and run heavy work asynchronously after responding with 200.
Ready-made recipe: Sign, save, and notify your team.
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-XXXXXXXXXXXX ties everything together.
Questions about Integrations.
Do the integrations require writing code?
Not necessarily: the automation tools Zapier, Make and n8n receive our events through their generic Webhook modules and run actions with a no-code setup; none of them has a dedicated Wthaiq app yet. And if you want full control and a custom link to your system, the REST API and Webhooks are fully available to you — the right choice depends on how much customisation you need.
Which integrations are native today, and which are coming soon?
Email notifications are built in natively and work now, as does saving to Google Drive, OneDrive and Dropbox from "External integrations" on the Business and Enterprise plans. Zapier and Make work today through their generic Webhook modules, n8n through the API, and the other tools — such as Slack, Microsoft Teams, HubSpot and Salesforce — connect through them or directly through the API. We do not promise a connector that has not been built.
How does the signed file reach my system?
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 with a public verification reference; a PAdES signature is embedded only for signers who used a token.
Are the integrations secure?
Yes. Every Webhook event is signed with the header Wthaiq-Signature using HMAC-SHA256, and must be verified with a constant-time comparison before processing, rejecting events older than 300 seconds. The key sk_ is live unless it is a test key (sk_test_), and the publishable key pk_ Limited in privileges and locked to your domains when used in the browser.
What if I cannot find the tool I use in the list?
No problem at all. Every capability on the platform is available through the REST API and Webhooks, so any system with an HTTP interface can be connected — either through an automation tool such as Zapier or Make, or with a custom integration you build yourself. Start from Documentation then connect whatever you like.
Connect Wthaiq to your stack today.
Start with an automation tool such as Zapier or Make, or build your own integration with the API and Webhooks. Everything you need is ready.