SignAndGoBuilding SignAndGo into your own systems.
If your team already works in its own software, such as a job management tool, a client portal or an in-house database, sending documents by hand means copying details between screens. The SignAndGo API and webhooks let that system send envelopes and hear back when things change. This guide is for the person planning that work.
Choose the first workflow to automate
Start with one document that your system already knows everything about. A quote accepted in your job tool, a new client created in your practice software, or a contractor onboarded in your rostering system are good candidates. Pick the one that is sent most often and has the fewest variations.
Write down, for that one workflow, which record triggers the send, who signs, in what order, and what should happen in your system when the last signature lands.
Map your records to an envelope
An envelope needs documents, signers and fields. Your system supplies the person's name and email address and the document itself. If the same layout is used every time, build it as a template in SignAndGo first, with a role for each signer, so the integration only fills in who plays each role.
Keep the identifier of your own record alongside the envelope so the two can be matched later. Without it, a webhook arriving next week has nothing to attach to.
Listen with webhooks instead of polling
Webhooks let SignAndGo tell your system when something happens to an envelope, so you do not have to keep asking. Use them to move a job to its next stage, notify the account manager, or pull the completed document into your own records.
Design your handler to cope with the same message arriving twice and with messages arriving out of order. Both happen with any webhook service, and a handler that assumes otherwise is the usual source of duplicate records.
Test with your own team first
Run the full path end to end with colleagues as signers before any client sees it. Check that names and email addresses come through correctly, that fields land on the right page, and that your system updates when the envelope completes or a signer declines.
- An envelope with one signer.
- An envelope with several signers in order.
- A declined envelope, to prove your system handles it.
- A signer with an unusual name, including macrons such as in Māori names.
Other connections that may save you the work
Before building, check whether an existing connection already covers the need. Signed documents can be filed into Xero automatically, and you can connect your AI assistant to check on envelopes and send documents conversationally.
Common questions
- Does SignAndGo have an API?
- Yes. There is an API for sending and managing envelopes, plus webhooks that report changes back to your system.
- Can my integration use our existing templates?
- Yes. Build the template in SignAndGo with signer roles, and your system supplies who fills each role.
- Is there a simpler option than building an integration?
- If you use Xero, signed documents can be filed there automatically without any development.