This article contains affiliate links. If you buy through them, we may earn a commission at no extra cost to you.
n8n + airSlate: Automate Contract Sending and E-Signature Collection in 20 Minutes
Every sales team knows the pain: a deal closes, and then someone has to manually draft the contract, attach it to an email, chase the client for a signature, and update the CRM. It is repetitive, error-prone, and slow. The good news is that you can replace the entire process with a single automated workflow — and you do not need a developer to build it.
This guide shows you how to connect n8n and airSlate to create a fully automated contract pipeline. You can set up the workflow in about 20 minutes, and it will run itself from that point on. If you are new to n8n, you can get started via n8n — it offers open-source workflow automation with 400+ integrations, with a free self-hosting option or a managed cloud plan.
What You Will Build
The workflow covers four steps:
- A trigger fires when a deal is marked as won in your CRM or a form is submitted.
- n8n pulls the client data and fills a contract template.
- The contract is sent to the client via airSlate for e-signature.
- When the client signs, n8n updates your CRM and notifies your team in Slack or by email.
For the e-signature and document workflow side, airSlate handles document creation, sending, and legally binding e-signature collection without writing a single line of code.
What You Need Before You Start
- An n8n instance (cloud or self-hosted)
- An airSlate account with a contract template already set up
- API credentials for your CRM (HubSpot, Pipedrive, Airtable, or similar)
- Optional: a Slack webhook for notifications
Step 1: Set Up the Trigger in n8n
Open n8n and create a new workflow. Add a trigger node that matches your process:
- CRM trigger: Use the HubSpot, Pipedrive, or Airtable node and listen for a deal-stage change to "Closed Won".
- Webhook trigger: If you use a custom form or another tool, use the Webhook node and point your form submission to the generated URL.
- Schedule trigger: Useful if you process contracts in daily batches from a spreadsheet.
For most sales teams, the CRM trigger is the cleanest option because the workflow fires the moment a rep marks a deal as won.
Step 2: Pull and Map Client Data
Once the trigger fires, add an HTTP Request node or the dedicated CRM node to fetch the full contact record. Map the following fields into n8n variables:
- Client full name
- Company name
- Email address
- Deal value and start date
- Any custom fields relevant to your contract
Use an n8n Set node to rename and clean up the field names before passing them downstream. This keeps the later steps readable.
Step 3: Send the Contract via airSlate
This is the core of the automation. airSlate exposes a REST API that lets you:
- Create a new document flow from an existing template
- Pre-fill template fields with your CRM data
- Add a recipient and define signature roles
- Send the document immediately
In n8n, add an HTTP Request node and configure it as follows:
- Method: POST
- URL:
https://api.airslate.com/v1/organizations/{org_id}/flows/{flow_id}/documents - Authentication: Bearer token from your airSlate API key
- Body: JSON with
recipient_email,recipient_name, and any field values to pre-fill
Map the client email and name from the Set node you built in Step 2 into the JSON body. When you click Execute Node, airSlate creates the flow, pre-fills the contract, and sends the signing link to your client automatically.
Tip: Use airSlate Bots for Conditional Logic
Inside airSlate, you can attach no-code bots to your document flow. For example, a Reminder Bot can send a follow-up email after 48 hours if the client has not signed yet — without any additional n8n steps.
Step 4: Handle the Signature Webhook
When the client signs the contract, airSlate fires a webhook. In n8n, add a second workflow (or a second branch) with a Webhook trigger that listens for the airSlate completion event.
The payload includes the document status, the signer's name, and a link to the signed PDF. Use this to:
- Update the deal stage in your CRM to "Contract Signed"
- Send a Slack message to the account owner
- Store the signed PDF link in a Google Sheet or Notion database
- Trigger an onboarding workflow for the new client
Step 5: Test the Full Flow End to End
Before going live, run the workflow in test mode:
- Create a test deal in your CRM and mark it as won.
- Check that n8n fires the trigger and maps the data correctly.
- Verify that airSlate receives the API call and sends the contract to a test email address.
- Sign the test document and confirm the completion webhook reaches n8n.
- Check that the CRM record and Slack notification update as expected.
The entire test cycle typically takes five to ten minutes. Once it passes, activate the workflow and it runs automatically from that point on.
Time Saved: A Quick Calculation
A typical manual contract process takes between 15 and 30 minutes per deal: drafting, attaching, sending, following up, and updating the CRM. If your team closes 20 deals a month, that is up to 10 hours of admin work. This workflow reduces that to near zero after the initial 20-minute setup.
Common Errors and How to Fix Them
- 401 Unauthorized from airSlate: Your Bearer token has expired or was copied with extra whitespace. Regenerate it in the airSlate developer portal.
- Template fields not pre-filling: Check that the field slugs in your JSON body exactly match the variable names defined in your airSlate template.
- Webhook not firing: Make sure your n8n instance is publicly accessible. If you are self-hosting behind a firewall, use a reverse proxy or ngrok for testing.
- Duplicate contracts sent: Add a Check node or a simple flag in your CRM to ensure the workflow does not trigger twice for the same deal.
Extending the Workflow
Once the core flow works, you can add more steps without rebuilding anything:
- Generate a PDF invoice automatically after the contract is signed.
- Create a project in Asana or ClickUp for the new client.
- Add the client to an onboarding email sequence in your marketing tool.
- Log the signed contract to a secure Google Drive folder with a timestamped filename.
Because n8n connects to 400+ services, each extension is just one more node in the same canvas.
If you want to stop processing contracts by hand and get this workflow running today, you can set it up via n8n — including open-source workflow automation with 400+ integrations and a free self-hosting option — to have every signed contract handled automatically from the moment a deal closes.