Resources · Make integration

easydoc Make integrationAutomate easydoc with Make.

Can easydoc feed your other tools on its own? The easydoc Make integration gives you 10 modules: 3 triggers that watch contacts, employees and signed documents, plus 7 actions. This guide helps HR and ops teams connect the account and build a first working scenario.

Try the easydoc integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the easydoc Make integration do for you?

The easydoc Make integration links your easydoc account to Make, a no-code tool where you chain apps together. You build a scenario, meaning the automation itself, out of modules: each module is one brick, such as a trigger that starts things or an action that does something in easydoc.

Paperwork that moves on by itself. Put Watch Signed Documents at the start of a scenario, then Get Information About a Document to read the file that just came back. From there, the details can go to any other app you use in Make.

A new hire set up once, not three times. Watch Created Employees notices each new employee record in easydoc, and Get Information About an Employee pulls the full profile so the next module can reuse it elsewhere.

Contacts that land in easydoc without retyping. When a person already exists in another tool, Create Contact adds them to easydoc, and Create a Form to Fill Out prepares the form they need to complete.

Be aware of one gap: Make's own documentation for easydoc is short, and Make says so openly. Plan to test each module with real data before you rely on it. For anything the 7 actions do not cover, Make an API Call reaches the rest of the easydoc API with the same connection. To go further, the Make training walks through the editor, and n8n vs Make helps if you are still choosing a tool.

Connect

How do you connect easydoc to Make?

  1. 01

    Add an easydoc module

    In a scenario, click the +, search for easydoc and pick any of its modules. Then click Create a connection. A connection is your easydoc account linked to Make once, and every easydoc module reuses it afterward.

  2. 02

    Name it and authorize

    Give the connection a name if you like, which helps when a team shares several accounts. Next, either approve Make on the easydoc page that opens, or paste the key easydoc gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. Back in the module, the connection now shows up in the list. If the module can read your data, Make fills its drop-down menus, which is a quick sign that the link works.

First scenario

Your first scenario: follow up on signed documents

GoalWhen a document is signed in easydoc, Make reads its details so the next step can use them.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the canvas. That empty circle becomes your first module.

  2. 02

    Place the trigger

    Search for easydoc, choose Watch Signed Documents and pick your connection. Fill in what the module asks for; Make lists what it can read once the connection exists.

  3. 03

    Add the document lookup

    Click the + on the right of the trigger and add Get Information About a Document. Map the document from the trigger into it, so it reads the file that was just signed.

  4. 04

    Test with Run once

    Sign a test document in easydoc, then click Run once. Open the bubbles above each module to see the bundles, the items passed from one module to the next.

  5. 05

    Schedule and switch on

    Click the clock on the first module. A new scenario checks every 15 minutes by default, and 15 minutes is also the shortest gap on the Free plan. Then turn the scenario on.

Triggers

What can start an easydoc scenario?

3 modules start a scenario when something happens in easydoc. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by easydoc as soon as it happens.

easydoc1Watch Created Contacts

Watch Created Contacts

triggerIn the docs only

Your scenario gets each contact newly added in easydoc, one bundle per person, so another app can receive that person without anyone copying the details by hand. Make lists this module in its documentation without a description, so its exact output is only visible once you test it.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
whenever a contact created in easydoc should also exist in a CRM, a mailing tool or a shared sheet.
Watch out
click Run once after adding a test contact and read the bundle before mapping anything further.
easydoc2Watch Created Employees

Watch Created Employees

triggerIn the docs only

This trigger hands you every new employee record from easydoc, which makes it the natural starting point for onboarding work spread across several tools. Unlike the contacts trigger, it follows the staff side of easydoc, not outside people.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
HR creates the employee in easydoc and the IT, payroll or chat tools should hear about it without a separate request.
Watch out
on the Free plan the shortest gap between checks is 15 minutes, so an arrival is never picked up the second it is saved.
easydoc3Watch Signed Documents

Watch Signed Documents

triggerIn the docs only

You learn about each document that comes back signed, which closes the loop on a contract or an HR form without anyone refreshing easydoc. Pick it when a signature is the moment someone else needs to act.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
a signed contract should alert the account owner, or a signed HR form should be filed in another tool.
Watch out
pair it with Get Information About a Document when the next step needs more than what the trigger itself returns.
Modules

What can Make do inside easydoc?

easydoc gives you 7 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

easydoc1

Create Contact

ActionIn the docs only

Adds a person to easydoc from data that already lives in another app, so the contact list stays complete without manual entry. It is the mirror of Watch Created Contacts: one reads new contacts, this one writes them.

When to use it
a lead signs up on a web form and needs to exist in easydoc before any document goes out.
Watch out
nothing in the documentation mentions a duplicate check, so test what happens when the same person arrives twice.
easydoc2

Create a Form to Fill Out

ActionIn the docs only

Prepares an easydoc form for someone to complete, straight from your scenario, instead of setting it up by hand each time a request arrives. Of the 7 actions, it is the one that starts new paperwork rather than recording people.

When to use it
right after Create Contact or Create an Employee, so the new person immediately has the form that belongs to their file.
Watch out
run it once on a test contact first and check the result inside easydoc.
easydoc3

Create an Employee

ActionIn the docs only

Registers a new employee in easydoc from another source, such as a recruiting tool or a hiring sheet, which saves HR a second round of typing. Choose it over Create Contact when the person joins the staff side of easydoc.

When to use it
a candidate is marked as hired somewhere else and should appear in easydoc on the same move.
Watch out
if Watch Created Employees also runs, the employee this module creates will start that other scenario too.
easydoc4

Get Information About a Document

ActionIn the docs only

Reads one easydoc document and returns its details to the scenario, so later modules can use them in a message, a table or a file. It works on a single document you point it to, usually one mapped from a trigger.

When to use it
after Watch Signed Documents, to collect what the next app needs about that signed file.
Watch out
since the documentation lists no fields, Run once is the only reliable way to see what it returns.
easydoc5

Get Information About an Employee

ActionIn the docs only

Pulls the easydoc record of one employee so the rest of the scenario can reuse it, for example to build an account in another tool. You give it the employee to read, most often straight from Watch Created Employees.

When to use it
an onboarding scenario needs the full profile rather than the short version a trigger may pass along.
Watch out
each lookup counts as an operation, one run of one module, on your Make plan.
easydoc6

Get Information About the Contact

ActionIn the docs only

Returns the easydoc details of a single contact, which is handy when a scenario only knows who the person is but not everything about them. It reads outside people, where the employee lookup reads staff.

When to use it
a signed document points to a contact and the follow-up email needs that person's details from easydoc.
Watch out
map the contact from an earlier module rather than typing it, or the scenario will read the same person every time.
easydoc7

Make an API Call

ActionIn the docs only

Opens the rest of the easydoc API to your scenario, with the connection you already set up, for whatever the other 6 actions do not handle. It is the fallback when a listed module is missing a feature you need.

When to use it
you know which easydoc endpoint does the job and no ready-made module offers it.
Watch out
you will need the easydoc API reference, since Make's own documentation for this app stays brief.
Need help

Need help automating easydoc with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the easydoc Make integration free?
Yes, easydoc is a standard app in Make, so its modules work on the Free plan. That plan has limits worth knowing: 2 active scenarios, at least 15 minutes between scheduled runs, 5 minutes of run time per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the gap between runs to 1 minute and remove the cap on active scenarios. Your easydoc subscription is a separate matter that Make does not cover.
02What do you need to connect easydoc to Make?
An easydoc account and a Make account are enough to start. Make's documentation lists no specific prerequisite for easydoc. The connection follows Make's usual steps: add an easydoc module, click Create a connection, optionally name it, then either approve Make on the easydoc page or paste the key easydoc provides, and click Save. After that, every easydoc module in any scenario can reuse the same connection, so the setup happens only once per account.
03Do easydoc triggers in Make fire instantly?
No. Make's documentation names the 3 easydoc triggers without detail, but as Watch modules they work as scheduled triggers (check the clock badge when you add one): Make checks easydoc on the scenario's schedule instead of easydoc calling Make the moment something happens. A new scenario checks every 15 minutes by default. On the Free plan that is also the shortest possible gap, while paid plans allow checks every minute. Keep this delay in mind before promising a colleague an immediate reaction.
04What if an easydoc module is missing in Make?
Use Make an API Call. It reaches any endpoint of the easydoc API from inside your scenario, with the connection you already created, so you are not limited to the 10 listed modules. The trade-off is that you need the easydoc API reference to know what to send. Make also states that its easydoc documentation is limited because little public information exists about the app, so testing each module with Run once remains the safest way to check what it returns.
05Should you use Make or n8n for easydoc?
It depends on what you already use. In Make, easydoc comes with 10 modules: 3 scheduled triggers covering contacts, employees and signed documents, 6 ready-made actions and Make an API Call for the rest. If those cover your case and your team already builds scenarios in Make, staying there keeps everything in one place. If your automations live in n8n, check whether its easydoc support covers the same steps before moving anything. Compare on the modules you actually need, not on the tool's name.
Same platform

Other docs you might need on this stack.

Browse all integrations