Signed contracts to the records system
When an envelope completes, a flow transfers the agreement into the contract folder in Laserfiche or SharePoint.
DocuSign eSignature is used by city purchasing, legal, HR and permit offices to collect signatures on contracts, agreements and forms. Each request is an envelope that moves from sent to completed.
SentraBridge reads envelopes changed since the last run and creates new envelopes from templates. Flows can record a signed status in another system or file the completed agreement. Envelope details pass through SentraBridge without being stored; run history shows counts and envelope IDs.
| resource | read | write | changes only | fields |
|---|---|---|---|---|
| Envelopes | list, read one | create | yes | Envelope ID, Status, Subject, Sent, Completed, Status changed |
When an envelope completes, a flow transfers the agreement into the contract folder in Laserfiche or SharePoint.
Completed envelopes update a contract tracking table in SQL Server that purchasing and finance report from.
New hires read from NEOGOV get an offer or onboarding envelope sent from a DocuSign template.
Envelopes still out after ten days are listed and emailed to the contract administrator each Monday.
Systems cities commonly connect with DocuSign, each with its own connector page.
Yes. The DocuSign eSignature REST API lets apps create envelopes and read their status, signed in with OAuth.
Yes. A flow reads completed envelopes and uses the Transfer file step to move the signed document into a Laserfiche folder with metadata.
No. Documents and envelope data pass through memory during a run. Only counts, timings and envelope IDs are kept.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.