Integration · Make + Zignature

Visual automation
for document signing.

Build powerful document signing workflows in Make's visual scenario builder. Trigger sends from any app, route signing events to CRMs, spreadsheets, or databases — no code, just drag and drop.

Connect Make Free → Book a Demo
Make
+
Zignature
1,500+ apps
All apps Make connects to
Visual builder
Drag-and-drop scenario editor
Routers + filters
Conditional logic, no code
Real-time
Instant webhook processing
Key Features

Everything You Need

Built-in features that save time and close deals faster.

Drag-and-Drop Document Signing Scenarios in Make

Add the Zignature module to any Make scenario. Connect it visually to triggers from your CRM, form tool, database, or calendar. Map fields with Make's intuitive data mapper — no JSON, no code. Complex multi-branch workflows in minutes.

  • Native Make module — Zignature appears in the Make module catalogue — search, drag, drop, configure.
  • Visual field mapping — Map data from any trigger to Zignature document fields using Make's visual mapper.
  • Any trigger — Works with any Make-supported trigger — webhooks, CRM events, database changes, form submissions.

Drag-and-Drop Document Signing Scenarios in Make

Add the Zignature module to any Make scenario. Connect it visually to triggers from your CRM, form tool, database, or calendar. Ma...

Included on all plans

Conditional Routing Based on Document Content and Signing Events

Use Make's Router module to split your scenario based on Zignature events or field values. Route completed contracts to one path, declined documents to another. Add filters to only process documents matching specific criteria.

  • Router branches — Split scenarios based on document status, signer details, or any field value.
  • Filters — Only continue the scenario when documents match conditions you define.
  • Aggregators — Collect multiple signing events and process them together in a single downstream action.

Conditional Routing Based on Document Content and Signing Events

Use Make's Router module to split your scenario based on Zignature events or field values. Route completed contracts to one path, ...

Included on all plans

Custom HTTP Modules and Zignature Webhook Receivers

Use Make's HTTP module with Zignature's REST API for full control over document creation, field injection, and submission management. Set up Make's webhook receiver to catch Zignature events and process them in complex, multi-stage scenarios.

  • REST API module — Call any Zignature API endpoint from Make using the HTTP module with full auth support.
  • Webhook receiver — Catch Zignature signing events in a Make webhook trigger for real-time processing.
  • Error handling — Make's built-in error handling and retry logic ensures no signing event is ever missed.

Custom HTTP Modules and Zignature Webhook Receivers

Use Make's HTTP module with Zignature's REST API for full control over document creation, field injection, and submission manageme...

Included on all plans
Use Cases

Works for Every Scenario

From simple agreements to complex multi-party workflows.

📊

Airtable Row → Contract

New Airtable record triggers a contract send with row data pre-filled.

🗄️

Database → Mass Send

New database row triggers bulk document sends to multiple recipients.

✅

Signed → Notion Update

Document completion updates a Notion database page with signer and timestamp.

🔄

Multi-step Workflows

CRM deal → document send → wait for signing → update record → notify team.

📝

Form → Agreement

Typeform or Jotform submission triggers an agreement send to the respondent.

🔗

API + Make Hybrid

Custom HTTP calls create documents, Make routes the completion event downstream.

How It Works

Up and Running in Minutes

No training required. Send your first document today.

1

Add Zignature to Make

Search for Zignature in Make's module catalogue and connect with your API key.

2

Build your scenario visually

Drag the trigger and Zignature module onto the canvas, connect them, and map fields.

3

Set up routers and filters

Add conditional logic to route signing events to different downstream paths.

4

Activate the scenario

Turn your scenario on and every trigger fires the complete document workflow.

Connect Make to Zignature Today

Free to start. No credit card. Works with your existing Make account.

Get Started Free → Book a Demo
FAQ

Frequently Asked Questions

Everything you need to know about the Make integration.

What Zignature actions are available as Make modules?
Send Document, Get Document Status, List Submissions, Get Submission PDF, and List Templates are available as native Make modules.
Can Make watch for Zignature signing events in real time?
Yes. Use Make's webhook module as the trigger — set the webhook URL in Zignature's webhook settings and Make processes every signing event in real time.
Does Make work with Zignature's API for advanced document creation?
Yes. Make's HTTP module supports Zignature's full REST API, including document creation with pre-filled fields, conditional field logic, and multi-recipient sends.
Can I use Make to send bulk documents to many recipients?
Yes. Use Make's Iterator and Aggregator modules to loop through a list of recipients from a spreadsheet, database, or CRM and send a personalised document to each.
Is there a Zapier integration as well?
Yes. Zignature also integrates with Zapier for teams that prefer Zapier's simpler interface.

Related Resources

Zapier Integration
Simpler automation for Zignature — 7,000+ app connections via Zapier.
REST API
Full REST API for custom integrations and programmatic document sending.
Airtable Integration
Trigger document sends from Airtable records via Make.

Related Resources

Zapier Integration
Related: Zapier automation integration.
E-Signatures for Operations Teams
Automate complex operations workflows with Make.
Statement of Work Signing
Automate SOW sending with Make scenarios.