Client Onboarding

Form → Contract → E-Signature

The gap between a verbal yes and a signed contract is where projects die. This workflow takes the intake form, merges the answers into your contract template, sends it for signature, chases it if unsigned and files the executed copy automatically.

7 stepsRequires Zapier Starter or higher25 minMedium

Google FormsGoogle DocsDocuSignGmailGoogle DriveSlackDelay by Zapier

What you get

Contracts go out the same hour the client agrees.

Unsigned contracts get chased automatically.

Signed copies are filed without you touching Drive.

Workflow blueprint

When this happens

Google FormsNew Form Response

1GD

Google DocsCreate Document from Template

2DO

DocuSignCreate Signature Request

3DE

Delay by ZapierDelay For

4GM

GmailSend Email

5GD

Google DriveUpload File

6SL

SlackSend Direct Message

The full blueprint — every field mapping, example value and the written copy for each message — is included with purchase.

Getting it into Zapier

Build this one from the recipe. The blueprint gives you the exact trigger, action events and field mapping for all 7 steps, so it is a copy-and-paste job rather than a design job.

You need your own Zapier account. Zapier’s Free plan runs single-step Zaps only; multi-step Zaps need a paid plan, and Paths and Webhooks need Professional. How this works →

Not on Zapier?

n8n — import and go

An n8n workflow JSON ships with this template. Import it and all 7 steps arrive on the canvas wired in order, and 5 of the 7 nodes arrive with their fields already filled in — the subject lines, the message copy, the delays, the column names. DocuSign has no native n8n node, so that step arrives as an HTTP Request node with the endpoint left for you to fill in.

Google Forms has no n8n node at all, so that step arrives as a native Google Sheets node on the form’s linked responses sheet. It is named for what it is on the canvas rather than for the app it stands in for, and the sticky note under it opens by saying so — the field names are unchanged either way, but the account you connect is the $Google Sheets one.

What an import cannot carry is your credentials, and the IDs that only exist inside your own account — which spreadsheet, which channel, which board. Those stay in a sticky note under the node, listing what is already done so you do not retype it, and what is left so you can see it.

Make — build guide

A Make-specific guide ships with this template: every module in order, every field value, and the concept translations that catch people out — filters live on the links between modules, and the schedule lives on the scenario rather than in a trigger module.

Self-hosted n8n has no per-task fee, which is worth knowing if this workflow runs at volume. Platform coverage →