Automate End-to-End Contract Signatures with Google Docs, Drive, and SignNow

This n8n workflow streamlines the entire contract signature process, from document generation to secure signing and storage. It automates the creation of contracts based on form submissions, converts them to PDF, sends them for e-signature via SignNow, and then archives the signed document in Google Drive.

What it does

1. Triggers on Form Submission: Listens for new submissions to an n8n form.
2. Sets Contract Details: Extracts relevant data from the form submission to define contract fields (e.g., contractName, recipientEmail, recipientName).
3. Generates Contract in Google Docs: Creates a new Google Doc using a specified template, populating it with the contract details from the form.
4. Converts to PDF: Exports the newly created Google Doc as a PDF file.
5. Uploads to Google Drive (Temporary): Stores the generated PDF contract temporarily in Google Drive.
6. Sends for Signature via SignNow: Uses an HTTP Request to the SignNow API to send the PDF contract for e-signature to the specified recipient.
7. Conditionally Checks Signature Status: After sending, it checks if the signature request was successful.
8. If Signature Request Successful:
   • Retrieves Signed Document: Fetches the signed document from SignNow.
   • Uploads Signed Document to Google Drive: Stores the final signed PDF document in a designated folder in Google Drive.
9. If Signature Request Fails (or is not yet signed):
   • Logs Failure (Implicit): The workflow would ideally have a separate branch or notification for failed signature requests, though not explicitly shown in this JSON.

Prerequisites/Requirements

• n8n Instance: A running instance of n8n.
• Google Account: With access to Google Docs and Google Drive.
  • Google Docs Credential: Configured in n8n for creating and exporting documents.
  • Google Drive Credential: Configured in n8n for uploading and managing files.
• SignNow Account: An active SignNow account for e-signatures.
  • SignNow API Key/Authentication: Configured as an HTTP Request credential in n8n.
• n8n Form: A pre-configured n8n form with fields corresponding to your contract template (e.g., contractName, recipientEmail, recipientName).
• Google Docs Template: A Google Docs template with placeholders (e.g., {{contractName}}, {{recipientName}}) that the workflow can populate.

Setup/Usage

1. Import the Workflow: Import the provided JSON into your n8n instance.
2. Configure Credentials:
   • Set up your Google Docs and Google Drive OAuth2 credentials.
   • Configure an HTTP Request credential for SignNow, providing your API key or other required authentication details.
3. Configure the "On form submission" Trigger:
   • Ensure the form fields match the data expected by the "Edit Fields" node.
   • Activate the form to receive submissions.
4. Configure the "Edit Fields" Node:
   • Map the incoming form data to the desired output fields (e.g., contractName, recipientEmail, recipientName).
5. Configure the "Google Docs" Node:
   • Specify the Document ID of your Google Docs contract template.
   • Ensure the Values are correctly mapped to your template's placeholders.
   • Set the Operation to "Create Document from Template" and "Export Document".
6. Configure the "Google Drive" Nodes:
   • Specify the Folder ID for both temporary and final signed document storage.
   • Ensure the Operation is set to "Upload File".
7. Configure the "HTTP Request" Node (SignNow):
   • Update the URL and body to match the SignNow API endpoint for sending signature requests.
   • Map the recipientEmail and contractName from previous nodes.
   • Attach the PDF file from the "Google Drive" node.
8. Configure the "If" Node:
   • Adjust the condition to check the response from the SignNow API to determine if the signature request was successfully sent.
   • (Optional) Add a condition to check for signature completion status if SignNow provides immediate status.
9. Activate the Workflow: Once all configurations are complete, activate the workflow.

Now, every time your n8n form is submitted, a new contract will be generated, sent for signature, and archived automatically!