Resources · Make integration

Digiclose Make integrationAutomate Digiclose with Make.

What should happen in your other tools the moment a Digiclose offer is accepted? The Digiclose Make integration answers that with 25 ready modules: 8 triggers, 9 actions and 8 searches. This page shows how to link your account, build a first scenario and pick the right module.

Try the Digiclose integration on MakeSee the 25 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Digiclose Make integration let you automate?

The Digiclose Make integration links your Digiclose CRM to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules. Each module is one brick, such as a trigger that watches Digiclose or an action that writes to it, so offers, contacts and tasks can move to other apps without copy and paste.

A yes that sets delivery in motion. Watch Accepted Offer notices when a prospect accepts an offer, and Create a Task hands the next step to the right person. A consulting firm, for example, can open the kickoff task as soon as the client agrees, instead of waiting for someone to read their inbox.

Tags that act as switches. With Watch Tag Added To Contact, putting a tag on a contact becomes an instruction: send the person to a newsletter tool, alert a colleague, or log them in a sheet. Remove Tags from a Contact closes the loop when the situation changes.

A CRM fed from the outside. Leads collected by a form or an event app can land in Digiclose through Create a Contact or Update a Contact, then receive their tags with Add Tags to a Contact, so the pipeline starts clean.

Know the limits before you start. Make's documentation for Digiclose is limited: the modules are listed by name, with no description and no connection guide, so you learn each one by testing it. For anything the 25 modules skip, Make an API Call reaches the rest of the Digiclose API with the same connection. If you are still choosing a platform, the n8n vs Make comparison sets out the criteria, the Make training covers the editor from scratch, and Make troubleshooting helps when a run fails.

Connect

How do you connect Digiclose to Make?

  1. 01

    Add a Digiclose module

    Open a scenario, click the +, search for Digiclose and pick any module, a trigger or an action. Make then asks for a connection, which is your Digiclose account linked once and reused by every Digiclose module. Click Create a connection.

  2. 02

    Name it and authorize Make

    Give the connection a name if you run several Digiclose accounts, so you can tell them apart later. Then follow what Make shows: either an authorization page from Digiclose, or a field where you paste the key your Digiclose account gives you.

  3. 03

    Save and check the fields

    Click Save. Back in the module, Make can now read your account, so the fields fill with choices it pulls from Digiclose. If the lists stay empty, the connection did not go through and needs to be recreated.

First scenario

Your first scenario: turn an accepted offer into a task

GoalWhen an offer is accepted in Digiclose, Make creates a task so the team knows who handles the next step.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + in the middle of the editor to place the first module.

  2. 02

    Add Watch Accepted Offer

    Search for Digiclose, choose Watch Accepted Offer and select your connection, or create it with Create a connection. Fill the fields the module shows.

  3. 03

    Add Create a Task

    Click the + on the right of the trigger and pick Create a Task. Map data from the accepted offer into the task, so the person assigned sees which deal it is about.

  4. 04

    Test with Run once

    Accept a test offer in Digiclose, then click Run once. Open the bubble above each module to read the bundles it received and confirm the task appeared in Digiclose.

  5. 05

    Schedule and switch it on

    On the first module, open the clock: a new scenario checks every 15 minutes by default. Keep or change that interval, then switch the scenario on so it keeps running without you.

Triggers

Which Digiclose triggers can start a scenario?

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

Digiclose1Watch Accepted Offer

Watch Accepted Offer

triggerIn the docs only

This trigger starts your scenario each time a Digiclose offer comes back accepted, so the work that follows a yes can begin without anyone retyping the deal. Each accepted offer reaches Make as one bundle, the item handed from one module to the next.

How it fires
scheduled. Make checks Digiclose on the scenario's schedule, every 15 minutes by default, so an acceptance shows up at the next check rather than the second it happens.
When to use it
a signed offer should open an onboarding task or record a transaction for the delivery team.
Digiclose2Watch Changed Contacts

Watch Changed Contacts

triggerIn the docs only

Keeping a second tool in line with your CRM gets easier here: the module picks up Digiclose contacts that were edited and passes each one down the scenario, so the copy elsewhere reflects the latest version without a manual export.

How it fires
scheduled. Make asks Digiclose for changed contacts on the scenario's schedule, and nothing moves between two checks.
When to use it
a newsletter platform or a shared sheet has to hold the same contact data as Digiclose.
Watch out
if a later module edits the same contact in Digiclose, that edit may count as a change and send the contact through again.
Digiclose3Watch Completed Task

Watch Completed Task

triggerIn the docs only

Finished work in Digiclose can set off the next step elsewhere. Whenever a task is marked complete, this module hands it to Make, ready to feed a report, a chat message or a follow-up.

How it fires
scheduled. Make looks for newly completed tasks each time the scenario runs on its schedule, not the moment the box is ticked.
When to use it
once a discovery call task is done, the next scenario step drafts the follow-up or logs the call in a team sheet.
Watch out
a task someone forgets to close never reaches the scenario, so the automation only works as well as the team's habit of closing tasks.
Digiclose4Watch Contact Deal Phase Changed

Watch Contact Deal Phase Changed

triggerIn the docs only

Pipeline moves are often the moment another action should happen. The module tells Make whenever a contact changes deal phase in Digiclose, so a stage change can alert a manager, update a forecast sheet or open a task.

How it fires
scheduled. Make checks Digiclose for phase changes on the scenario's schedule, so the alert arrives at the next check.
When to use it
a deal reaching its closing phase should warn the person who prepares contracts.
Watch out
run List Pipelines once first to see how your pipelines are set up, then decide what each move should trigger.
Digiclose5Watch Created Task

Watch Created Task

triggerIn the docs only

New tasks created in Digiclose can show up in the tools your team already watches. The trigger picks up each fresh task and sends it through the scenario, for instance to a shared to-do board or a chat channel.

How it fires
scheduled. Make collects the tasks created since its last look, on the scenario's schedule.
When to use it
part of the team lives in another task tool and should not have to open the CRM to learn what was assigned.
Watch out
tracking both new and finished tasks means two scenarios, and the Free plan allows 2 active scenarios in total.
Digiclose6Watch Offer Seen

Watch Offer Seen

triggerIn the docs only

Timing a follow-up call is simpler with this one. As its name says, it reacts when a Digiclose offer is marked as seen, which gives the salesperson a cue that the prospect has the proposal in front of them.

How it fires
scheduled. Make checks Digiclose on the scenario's schedule, so the cue lands at the next check, not at the exact moment of viewing.
When to use it
the account owner wants a chat alert to call while the offer is still fresh in the prospect's mind.
Watch out
the documentation gives no detail on what counts as seen, so test it with Run once on an offer you open yourself.
Digiclose7Watch Tag Added To Contact

Watch Tag Added To Contact

triggerIn the docs only

Tags become commands with this trigger. Adding a tag to a Digiclose contact starts the scenario, so a salesperson can launch a whole sequence just by labeling a contact, without leaving the CRM.

How it fires
scheduled. Make checks for newly added tags on the scenario's schedule and passes each tagged contact on as a bundle.
When to use it
a tag such as webinar should push the contact to your event tool or open a task for a colleague.
Watch out
the scenario reacts to the exact tag text, so run List Tags first and copy the spelling your account uses.
Digiclose8Watch Tag Removed From Contact

Watch Tag Removed From Contact

triggerIn the docs only

Removing a label is also a signal worth catching. This trigger fires when a tag comes off a Digiclose contact, which lets another app forget the person just as cleanly as it welcomed them.

How it fires
scheduled. Make looks for removed tags each time the scenario runs on its schedule.
When to use it
a contact loses the prospect tag after signing, and should leave the prospecting list in your mailing tool.
Watch out
if another scenario adds that same tag back automatically, the two can keep undoing each other, so decide which tool owns the tag.
Modules

What can Make do in Digiclose?

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

Digiclose1

Add Tags to a Contact

ActionIn the docs only

Labels a Digiclose contact from the scenario, so segments stay accurate without anyone opening the CRM. Tags added here can in turn start a scenario built on Watch Tag Added To Contact.

When to use it
a lead who fills an event form should come out tagged with that event.
Watch out
run List Tags first so you reuse existing tags instead of near duplicates.
Digiclose2

Create a Contact or Update a Contact

ActionIn the docs only

Sends a person into Digiclose and, as the name says, either creates a new contact or updates one that is already there. It is the entry door for leads collected in other tools.

When to use it
a form, an event app or a chatbot captures someone who belongs in your CRM.
Watch out
the documentation does not say how an existing contact is recognized, so test with Run once on a known contact.
Digiclose3

Create a Product

ActionIn the docs only

Adds an item to your Digiclose product catalog from another source, so the products you sell in offers match the list kept elsewhere, in an online shop or a pricing sheet.

When to use it
a new service or reference is published outside the CRM and should be ready to quote.
Watch out
check List Products before creating, or every run of the scenario may add the same product again.
Digiclose4

Create a Task

ActionIn the docs only

Puts a to-do in Digiclose, assigned and ready, whenever something in the scenario calls for human follow-up. It is the action behind the first scenario on this page.

When to use it
an accepted offer, a form reply or a tag should turn into a clear next step for someone on the team.
Watch out
use List Users and List Task Categories to find the right owner and category before you map them.
Digiclose5

Create a Transaction

ActionIn the docs only

Records a transaction in Digiclose from what happened in another app, which keeps sales history in the CRM even when payment or signature happens elsewhere.

When to use it
a payment tool or an e-signature app confirms a deal and the CRM should show it too.
Watch out
the documentation lists no fields for this module, so open it in the editor and test with Run once before relying on it.
Digiclose6

Get a Product Information

ActionIn the docs only

Fetches the details of one Digiclose product so later modules can reuse them, for example in an email, a quote in another tool or a sheet row.

When to use it
you already know which product is involved and need its data further down the scenario.
Watch out
it works on a single product; to browse the catalog, List Products is the better pick.
Digiclose7

Get a User Information

ActionIn the docs only

Reads the profile of one Digiclose user, meaning a member of your own team, so you can address them correctly in a notification or route work to them.

When to use it
a notification has to reach a specific colleague and needs that person's details.
Watch out
this looks up colleagues in Digiclose, not your contacts; for customers, List Contacts is the right module.
Digiclose8

List Contact Fields

SearchIn the docs only

Shows which fields your Digiclose contacts carry, which helps before mapping data from another tool into a contact.

When to use it
you are building a sync and want to see what your account actually stores instead of guessing.
Watch out
like any search module, it can return several bundles, so Run once is the easiest way to read the full result.
Digiclose9

List Contacts

SearchIn the docs only

Pulls contacts out of Digiclose in bulk, one bundle per contact, so the scenario can process each of them in turn.

When to use it
a one-off copy of your CRM contacts into a sheet, or a check against another list.
Watch out
every contact returned is a bundle, and each following module spends one operation per bundle, which adds up on a large base.
Digiclose10

List Pipelines

SearchIn the docs only

Returns the sales pipelines set up in your Digiclose account, so you see how your sales process is organized before a scenario reacts to it.

When to use it
before building on Watch Contact Deal Phase Changed, to see which pipelines your account uses.
Watch out
a search can return zero results; if nothing comes back, check the connection has access to the pipelines.
Digiclose11

List Products

SearchIn the docs only

Brings back the products in your Digiclose catalog, which lets a scenario compare them with another list or export them.

When to use it
your shop and your CRM should offer the same items and you want to spot what is missing on one side.
Watch out
run it before Create a Product so the scenario does not create an item that already exists.
Digiclose12

List Tags

SearchIn the docs only

Returns every tag available in your Digiclose account, which is the quickest way to learn the exact spelling before a tag drives a scenario.

When to use it
you are setting up Add Tags to a Contact or a tag trigger and want to reuse what exists.
Watch out
one tag written two ways splits a segment in two, so settle on one spelling with the team.
Digiclose13

List Task Categories

SearchIn the docs only

Reads the task categories defined in Digiclose, so tasks created by Make land in the same buckets as those your team creates by hand.

When to use it
before mapping a category in Create a Task, to pick one that really exists.
Watch out
if a category is renamed in Digiclose later, go back to the scenario and check the mapping still points to it.
Digiclose14

List Teams

SearchIn the docs only

Lists the teams configured in your Digiclose account, useful when work should go to a group rather than to one person.

When to use it
a scenario routes deals or tasks by team, for instance sales on one side and customer success on the other.
Watch out
a search returns several bundles, so later modules run once per team unless you narrow the result.
Digiclose15

List Users

SearchIn the docs only

Returns the people who use your Digiclose account, the list you need when a scenario has to assign work or notify a colleague.

When to use it
you want Create a Task to go to the right salesperson rather than always the same one.
Watch out
to read one known user in detail, Get a User Information is lighter than listing everyone.
Digiclose16

Make an API Call

ActionIn the docs only

Reaches any part of the Digiclose API that the listed modules leave out, using the same connection, so a missing module does not block your idea.

When to use it
you need an operation none of the 25 modules covers, and Digiclose documents the matching endpoint.
Watch out
this module expects you to read the Digiclose API reference yourself; it is the most technical brick on the page.
Digiclose17

Remove Tags from a Contact

ActionIn the docs only

Takes tags off a Digiclose contact from inside a scenario, which keeps segments honest once a person moves on from a campaign or a stage.

When to use it
a signed deal should clear the prospect tag without anyone thinking about it.
Watch out
removing a tag can itself start a scenario built on Watch Tag Removed From Contact, so map what follows.
Need help

Need help automating Digiclose with Make?

A person reads every message.

FAQ

Digiclose and Make: frequent questions

01Is the Digiclose Make integration free?
Yes, Digiclose is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes per run and 512 MB of data transfer. Every module run counts as an operation, which is what Make measures on your plan. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. Your Digiclose subscription is a separate matter, and this page says nothing about its price.
02What do you need to connect Digiclose to Make?
A Digiclose account and a Make account. Make's documentation lists no prerequisite and no dedicated connection steps for Digiclose, so the usual Make flow applies: add a Digiclose module, click Create a connection, optionally name it, then authorize Make on the Digiclose page or paste the key Digiclose gives you, and click Save. If the fields in the module fill with your own data, the connection works. If authorization is refused, ask Digiclose support how outside tools connect to your account.
03Do Digiclose triggers in Make work in real time?
No. All 8 Digiclose triggers are scheduled: Make checks Digiclose on the scenario's schedule instead of being called the moment something happens. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan; paid plans go down to 1 minute. Since the documentation lists these triggers by name only, look at the clock badge on the module when you add it to confirm the type in your editor.
04What if a Digiclose module you need is missing in Make?
Use Make an API Call. It sends a request to any Digiclose API endpoint with the connection you already set up, so it covers what the other modules leave out. It does ask you to read the Digiclose API reference. Keep in mind that Make's documentation for Digiclose is limited, with no descriptions per module, so testing a module with Run once is often the fastest way to see what it returns before deciding it does not fit.
05Should you use Make or n8n for Digiclose?
It depends on where your automations already live. On Make, Digiclose comes with 25 ready modules, including 8 scheduled triggers and a Make an API Call module for the rest, and the whole setup happens in a visual editor. Whether n8n has a Digiclose node is not covered by this page, so check its node list before comparing. If your team already runs one of the two tools for other apps, staying there usually keeps maintenance in one place.
Same platform

Other docs you might need on this stack.

Browse all integrations