Resources · Make integration

GetAccept Make integrationAutomate GetAccept with Make.

What if every signed GetAccept deal filed itself? The GetAccept Make integration gives you 14 modules, 4 of them instant triggers, to create, track and fetch documents without code. This guide connects your account and walks you through a first scenario.

Try the GetAccept integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the GetAccept Make integration do for you?

The GetAccept Make integration links your GetAccept account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, creates or fetches something. GetAccept tells Make the moment a document is created, sent, reviewed or signed, and Make can create documents, contacts and uploads for you.

Proposals that write themselves. When a deal reaches the right stage in your CRM, Create a Contact adds the buyer to GetAccept and Create a Document from Template builds the proposal from your approved template, so sales reps stop copying names by hand.

A clean archive of signed contracts. Watch Documents Signed fires as soon as a document is signed. Get Document Details and Download a Document then hand the final file to your storage or accounting tool.

Follow-ups that start on time. Watch Documents Reviewed tells you a prospect reviewed the proposal, which is the moment to alert the account owner. List Document Recipients shows who else is on the document.

Know the limits before you start: the Make documentation says the modules need a paid GetAccept account, and it lists no other restriction. Anything the 14 modules leave out goes through Make an API Call. GetAccept may also be reachable from n8n; the n8n vs Make comparison lays out the criteria, the Make pricing guide covers plans, and Make training helps if scenarios are new to you.

Connect

How do you connect GetAccept to Make?

  1. 01

    Add a GetAccept module

    In your scenario, add any GetAccept module and click Create a connection. A connection is your GetAccept account linked to Make once, then reused by every GetAccept module. With an instant trigger, click Create a webhook first, then Create a connection.

  2. 02

    Enter your GetAccept login

    Type the email and password you use for GetAccept in the Email and Password fields. You can also fill Connection name with something clear, such as the team that owns the account.

  3. 03

    Pick the entity and save

    If your account manages several entities, put the one you need in Entity ID; left empty, Make uses your default entity. Click Save, then confirm access if GetAccept asks for it.

First scenario

Your first scenario: from a new deal to a ready proposal

GoalWhen a deal moves forward in your CRM, Make adds the buyer to GetAccept and builds the proposal from your template.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the module of the tool where your deals live, the CRM or form that starts everything.

  2. 02

    Add Create a Contact

    Click the + on the right, search GetAccept and choose Create a Contact. Link your account with Create a connection, then map the buyer's name and email from the first module.

  3. 03

    Build the document

    Add Create a Document from Template after it. Choose the template ID of your standard proposal and map the contact data from the previous modules into the fields Make shows.

  4. 04

    Test with Run once

    Click Run once and create a test deal. Each module shows the bundles it received, a bundle being one item passed along, here one deal and one contact. Check the draft in GetAccept.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. Each module run counts as one operation, the unit Make counts on your plan.

Triggers

What starts a GetAccept scenario?

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

GetAccept1Watch Documents Created

Watch Documents Created

Instant trigger

In Make“Triggers when a new document has been created.”

Gives your scenario a starting point every time someone in your team creates a new document in GetAccept, whether it will be sent later or not. You get the document as a bundle, ready to log or pass on to the next module.

How it fires
instant, GetAccept calls Make through a webhook as soon as the document exists.
When to use it
to record each new proposal in a pipeline sheet or tell a manager that a draft needs a look before it goes out.
Watch out
a created document is not a sent one, so pick Watch Documents Sent if the customer must already have it.
GetAccept2Watch Documents Sent

Watch Documents Sent

Instant trigger

In Make“Triggers when a document has been sent.”

Lets Make react when a document actually leaves GetAccept toward its recipients. The sent document arrives as a bundle, which means the next modules can update a deal stage or start a reminder sequence with real data.

How it fires
instant, GetAccept calls Make through a webhook the moment the document is sent.
When to use it
to move the deal to a stage like proposal sent in your CRM without asking reps to do it.
Watch out
the trigger hands over the document, not its recipients; add List Document Recipients to see who got it.
GetAccept3Watch Documents Reviewed

Watch Documents Reviewed

Instant trigger

In Make“Triggers when a document has been reviewed.”

Tells you a recipient has reviewed the document, a clear sign the buyer has looked at your offer. Your scenario receives the document as a bundle and can alert the right person while the proposal is still fresh in the buyer's mind.

How it fires
instant, GetAccept notifies Make through a webhook as soon as the review happens.
When to use it
to ping the account owner in a chat channel so the follow-up call happens while interest is high.
Watch out
review does not mean agreement; keep contract steps for Watch Documents Signed.
GetAccept4Watch Documents Signed

Watch Documents Signed

Instant trigger

In Make“Triggers when a document has been signed.”

Hands your scenario the signed document right after signature, the event that closes the deal. From here Make can fetch details, download the file and tell finance, onboarding or delivery that the deal is closed.

How it fires
instant, GetAccept calls Make through a webhook as soon as the document is signed.
When to use it
to archive the signed contract and open an onboarding task in the same run.
Watch out
the trigger gives you the document, not the file itself; add Download a Document to get the file.
Modules

What can Make do in GetAccept?

GetAccept gives you 10 modules in 4 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Files

1 module
GetAccept1

Upload a File

Action

In Make“Uploads a file to be used for document creation.”

Sends a file from another tool into GetAccept so it can become the base of a new document. Your contract generated elsewhere, a PDF from a drive for instance, lands in GetAccept without a manual upload.

When to use it
when the document content is produced outside GetAccept and you only need it sent and signed there.
Watch out
the upload alone sends nothing; follow it with Create a Document.

Documents

7 modules
GetAccept2

Search Documents

Search

In Make“Searches for documents or lists them all.”

Finds documents in your GetAccept account, or lists every one of them, so a scenario can work on a set rather than a single file. Each match comes out as its own bundle.

When to use it
to build a report of open proposals or to find a document when you only know part of its details.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per result.
GetAccept3

List Document Recipients

Search

In Make“Gets a list of all recipients of a document specified by ID.”

Shows everyone attached to a given document, one bundle per recipient, so you know exactly who received a proposal. You pass the document ID, often straight from a trigger.

When to use it
after Watch Documents Signed, to add every signer to your CRM or send each one a welcome email.
Watch out
several recipients mean several bundles, and the modules that follow run for each of them.
GetAccept4

Get Document Details

Action

In Make“Retrieves a single document specified by ID.”

Pulls the full record of one document from its ID, which gives later modules more to work with than a trigger bundle alone. It reads the document and changes nothing in GetAccept.

When to use it
when a scenario started by another app holds a document ID and you need the matching information before updating a deal.
Watch out
it needs a valid ID; map it from a trigger or a search instead of typing it.
GetAccept5

Download a Document

Action

In Make“Downloads a document specified by ID.”

Turns a GetAccept document into a file inside your scenario, so you can save it, attach it to an email or push it to accounting. It is the step that gets the signed contract out of GetAccept.

When to use it
right after Watch Documents Signed, to keep a copy of every contract in your own storage.
Watch out
on the Free plan, Make handles files up to 5 MB, so large documents need a paid plan.
GetAccept6

Create a Document

Action

In Make“Creates a new document.”

Creates a brand new GetAccept document from your scenario, ready for recipients, without opening GetAccept. Paired with Upload a File, it turns a file made in another tool into something your buyer can sign.

When to use it
for one-off documents whose content does not come from a saved template.
Watch out
if your team reuses a standard layout, Create a Document from Template saves the setup.
GetAccept7

Create a Document from Template

Action

In Make“Creates a document by the specified template ID.”

Builds a document from one of your GetAccept templates, picked by its template ID, so every proposal keeps the approved wording and layout. The scenario fills in the deal while the template keeps legal happy.

When to use it
when the same proposal or agreement goes out for many deals and only the customer data changes.
Watch out
the template must already exist in GetAccept; Make does not create it.
GetAccept8

Delete a Document

Action

In Make“Deletes a document specified by ID.”

Removes a document from GetAccept by its ID, which keeps the account tidy when drafts or tests pile up. It is the only module here that destroys data.

When to use it
to clean out test documents created while you were building a scenario, or drafts for deals that were lost.
Watch out
treat a deletion as final: place a filter before it and test with Run once.

Contacts

1 module
GetAccept9

Create a Contact

Action

In Make“Creates a new contact.”

Adds a person to your GetAccept contacts from data held in another app, so reps find the buyer ready when they prepare a document. It removes the copy and paste between CRM and GetAccept.

When to use it
when a lead becomes a real opportunity in your CRM, before any proposal is created.
Watch out
the documentation says nothing about duplicates, so test with Run once on a contact that already exists before you switch on.

Other

1 module
GetAccept10

Make an API Call

Action

In Make“Performs an arbitary authorized API call.”

Reaches any endpoint of the GetAccept API from your scenario, with the same connection as the other modules. It covers what the ready-made modules leave out, and you need no new credentials.

When to use it
when you need a GetAccept action that has no dedicated module, and you have the API documentation open.
Watch out
you write the request yourself, so check the endpoint and method before running it on real data.
Need help

Need help automating GetAccept with Make?

A person reads every message.

FAQ

GetAccept and Make: frequent questions

01Is the GetAccept Make integration free?
Yes, on the Make side. GetAccept is a standard app, so it works on the Free plan, which allows 2 active scenarios, runs of up to 5 minutes, files up to 5 MB and scheduled runs no closer than 15 minutes apart. Paid plans lower that interval to 1 minute and remove the active scenario cap. On the GetAccept side, the Make documentation says the modules need a paid GetAccept account, so budget for that subscription.
02What is needed to connect GetAccept to Make?
A paid GetAccept account and its login. In the module, click Create a connection, type your GetAccept email and password, and save. With an instant trigger, click Create a webhook before creating the connection. If your account manages several entities, fill Entity ID with the one you want; left empty, Make picks your default entity. Confirm access if GetAccept prompts you, and the connection is then reused by every GetAccept module.
03Do GetAccept triggers in Make react in real time?
Yes. All 4 GetAccept triggers are instant: GetAccept calls Make through a webhook as soon as a document is created, sent, reviewed or signed, and the scenario runs right away. There is no polling interval to wait for, unlike scheduled triggers that Make checks on the scenario's schedule, every 15 minutes by default. When you test, click Run once and then act in GetAccept, so the webhook has an event to send.
04What if a GetAccept module is missing in Make?
Use Make an API Call. It calls any endpoint of the GetAccept API with the connection you already set up, so you can cover actions the 14 modules do not list. Keep the GetAccept API documentation at hand to pick the right endpoint. The Make documentation lists no numeric limit for GetAccept modules, so the usual constraints are those of your Make plan, such as file size and run duration.
05Should you use Make or n8n for GetAccept?
It depends on what you need to automate. In Make, GetAccept comes with 14 modules, including 4 instant triggers for created, sent, reviewed and signed documents, plus Make an API Call for the rest, and it runs on the Free plan. GetAccept may also be available in n8n. Compare the exact events and actions each tool offers for your use case and pick the one where your team already builds its automations.
Same platform

Other docs you might need on this stack.

Browse all integrations