Automate eSignatures across 3,500+ apps with Make.
Send contracts straight from your CRM, forms, and spreadsheets, then update the deal and send the invoice the moment everyone signs.
- Sends from your Inkly templates
- Signers' answers flow into your next module
- No per-document fees
When a deal closes
Instant- 1HubSpotWatch deals
2InklySend a document from a template
- 3SlackCreate a message
When everyone has signed
Instant1InklyWatch completed documents
- 2HubSpotUpdate a deal
- 3QuickBooksCreate an invoice
Your CRM, sheets, and storage, all talking to Inkly.
Make connects Inkly to 3,500+ apps. Start a document from a won deal, a new row, a payment, or a booked call, then send the signed copy wherever your team keeps its records.
See every module on Inkly's Make page
Every send, for a fraction of what other eSignature APIs charge.
$15 a month covers 250 sends from your scenarios, or 1,000 on the $40 plan. The same 250 documents cost $178 through SignWell's API, $187.50 through BoldSign's, and $275 through Dropbox Sign's.
Each document a scenario sends counts once, however many signers it has. Triggers like Watch completed documents, and signed PDF downloads, never count, so scenarios that file signed copies or update your CRM run as often as you need. There are no per-document fees: if you reach your allowance, sends pause until the 1st instead of running up a bill. Documents you send from Inkly itself stay unlimited.
Make bills its own plan separately. Compare API prices
This month's scenarios
API documents
Send the agreement250 runs250
File the signed PDF250 runs0
Post in #sales250 runs0
Used this month
250
Inkly
$15
a month for 250
SignWell API
$178
a month for 250
BoldSign API
$187.50
a month for 250
Dropbox Sign API
$275
a month for 250
Send from any scenario. Start one the moment it's signed.
Send a document from any scenario.
Pick a template, then add a recipient for each role and a value for each prefilled field. Make lists the template's own roles and fields, so you map data from any earlier module.
- A Unique ID sends once, even if a scenario reruns
- Automatic reminders on days 3, 6, and 10
- Or Create a draft from a template to check it first
Start a scenario the moment it's signed.
Watch sent documents, Watch signatures, and Watch completed documents reach Make instantly, so the next module runs straight away instead of on a schedule.
- Every value signers filled in
- The signed PDF as a file, one module later
- Your Unique ID, to update the right deal or row
Scenarios to start with.
Most teams begin with one scenario that sends and one that follows up once it's signed. These six cover the jobs people ask about most, and each takes a few minutes to build.
- Send an Inkly template when a HubSpot deal is wonBuild it in Make
- Send an Inkly template for each new Google Sheets rowBuild it in Make
- Save signed PDFs from Inkly to Google DriveBuild it in Make
- Update an Airtable record when an Inkly document is completedBuild it in Make
- Post in Slack when a signer signs an Inkly documentBuild it in Make
- Send a service agreement when a Stripe payment succeedsBuild it in Make
Connect Inkly to Make in three quick steps.
The step-by-step guide walks through a first scenario, and Inkly on Make lists every module.
1Create an API key in Inkly, under Account, API. Read and send lets your scenarios send.
2In a scenario, add a module, search for Inkly, and pick a trigger or an action.
3Click Create a connection and paste the key. Make shows your workspace's name on the connection.
Make, Zapier, n8n, or the API?
All four come with Pro and Teams and share the same monthly API documents, so pick by how you like to work. Make suits scenarios that branch, filter, or loop.
Make
This pageVisual scenarios with branches, filters, and routers, built without code.
- Instant triggers
- API call module
- Pro and Teams
Zapier
The most apps. Build a straight-line Zap in minutes from the apps you already use.
- 9,000+ apps
- Instant triggers
- Pro and Teams
n8n
Workflows you host yourself, or that hand work to an n8n AI Agent.
- Verified node
- Cloud or self-hosted
- Pro and Teams
Inkly API
Your own software, with signing links and one-off PDFs as well as templates.
- REST and webhooks
- Send any PDF
- Pro and Teams
Compare them on the integrations page, or see Zapier, n8n, and the API.
Questions about Make and Inkly.
Plans, speed, signed PDFs, and what Make keeps.
See the full plan breakdown →Send your first document
from Make.
Create an API key, add Inkly to a scenario, and send from a template you already use.