E Sign + StackGo
E Sign at the intake step of a compliance workflow.
E Sign publishes 3 trigger events and 2 actions on its public Zapier listing. That is what a StackGo connector would be built on.
Also listed under Document management
Online document signing platform.
Description supplied by E Sign.
Named fields, not a link to a portal. These are the fields StackGo writes on the systems it connects to today; a E Sign connector would offer the same.
- Verification status
- Risk rating
- Last checked
- Report link
- Verified name
- Date of birth
- Document checked
- Screening result
- Beneficial owners
- Form responses
- Verification report (PDF)
Every field is optional. What each one holds, and which carry personal data, is set out once in what “integrates with” actually means.
E Sign’s public integration surface
The rest of what E Sign exposes on Zapier, beyond the workflow. This is the raw material a connector would use.
- New Completed Envelope
- New Created Envelope
- New Signer
- Create Envelope From Template
- Upload File to E-Sign
Names are E Sign’s own, read from its public Zapier listing on 28 August 2026.
Common questions about E Sign
What is Docusign integration?
There is no StackGo connector for E Sign yet. E Sign publishes 3 trigger events and 2 actions through Zapier, so building one is realistic. Requests decide the build order.
Questions taken from what people actually search in Australia. We answer only the ones our own data answers.
E Sign is made by www.e-sign.co.uk. We are not affiliated with them.
Want E Sign connected?
Requests decide the build order. Tell us and we will tell you where it sits.
Request this integrationReady to make onboarding minutes, not hours?
Start free and run your first check today, or book a demo and we will walk you through it.