Make.com envelope signing with Atlas

Make (formerly Integromat) scenarios connect CRMs, storage, and chat tools with visual modules. Atlas fits as an HTTP module pair: create envelope, then react to webhook or poll status.

> Share: "Make scenarios trigger Atlas create. Review URL keeps legal in the loop."

Scenario overview

Watch CRM deal / new file in Drive
  → HTTP POST create envelope
  → Router on HTTP status 200
  → Slack module posts review_url
  → Webhook module catches envelope.signed
  → CRM update + file upload

Make's strength is branching and data stores. Store envelope_id in a Make Data Store keyed by deal ID for idempotent replays.

HTTP module: create

{
  "document_url": "{{1.fileUrl}}",
  "webhook_url": "https://hook.eu1.make.com/xxxxxxxx",
  "metadata": {
    "client_reference_id": "make-deal-{{1.dealId}}",
    "external_id": "{{1.dealId}}"
  },
  "parties": [
    {
      "email": "{{1.email}}",
      "name": "{{1.name}}",
      "role": "Customer"
    }
  ]
}

Add custom header Idempotency-Key with a hash of deal ID to survive Make automatic retries.

Webhook module: Atlas events

Create a Custom webhook in Make. Paste the URL into Atlas webhook_url at create.

Add a JSON parser module, then a Router on {{body.event}}:

Verify X-Atlas-Signature in a Make Code module if the scenario is production-critical. See Webhooks and debugging.

Google Drive file path

When the trigger is a new PDF in Drive:

1. Google Drive > Download a file
2. HTTP > multipart upload to Atlas (some teams use an intermediate Cloudflare Worker for multipart if Make binary handling is finicky)
3. Alternative: upload to a public signed URL bucket, pass document_url

PDF and DOCX both work on create.

Template path for repeat docs

After the first NDA is approved in Atlas, save a template. Replace the create module with HTTP POST to /api/templates/{id}/send and map Make variables to prefill keys from get_template.

Template sends still cost one credit at dispatch.

Operations limits

Make operations consume per module run. Model cost as:

• Trigger + create + notify + webhook handler + CRM update = five operations minimum per contract
• Compare to Atlas $1 per send credit

For high volume, n8n self-host or a single Vercel function often wins on total cost.

Data store pattern for replays

When Make replays a scenario after an HTTP timeout, you risk duplicate envelopes without idempotency. Write dealId → envelope_id into a Make Data Store on successful create. Subsequent runs read the store first and skip create if a row exists.

Pair that with Atlas Idempotency-Key: make-{{dealId}} header so server-side dedupe matches client-side guards.

Observability

Enable Make execution history webhooks to your logging stack. Include Atlas HTTP status and response body snippet (redact tokens). Support tickets move faster when ops can see whether create failed on 402 credits versus 409 fields pending.

Multi-module PDF handling

When PDFs start in Gmail or Dropbox modules, confirm the download URL is HTTPS and reachable from Atlas egress. Temporary links that expire in 15 minutes fail create with 400. Copy to durable storage first if vendor links are short-lived.

Scenario templates

Make sells scenario templates for CRM plus HTTP patterns. Replace generic HTTP examples with Atlas payloads from this guide. Save org template with Idempotency-Key header prefilled.

Error routes

Add an error handler route on HTTP modules:

FAQ

Official Make app? No marketplace connector. HTTP modules are the integration surface.

Can Make call Send automatically? Not recommended for ad-hoc PDFs. Human Send on review is the default trust model. Templates can auto-send when policy allows.

EU data residency? Make EU zone + Atlas US hosting is typical. Confirm counsel guidance on where PDFs rest.

Agents vs Make? Use Atlas MCP when the user works in Claude. Use Make when ops automates CRM stages without chat.

Multi-signer? Pass ordered parties array. Atlas handles sequential promotion.

Related

• n8n Atlas e-sign
• Zapier e-sign integration
• E-signature API

Extended FAQ

Make Cloud vs self-host? Both work. Ensure outbound HTTPS to atlaswork.ai is allowed.

Can scenarios call MCP? No. HTTP modules only for Make scenarios.

Handling partial failures? Use rollback routes to mark CRM record error state with Atlas response body snippet.

Enterprise Make SSO? Atlas API key still lives in scenario connection, not end-user SSO.

Bulk import? Iterator module with Idempotency-Key per row prevents duplicate envelopes on replay.

API reference

Full route list and request schemas live at /dev. Start with E-signature API for the mental model, then use this guide for copy-paste examples.