Resources · Make integration

Deskera Make integrationAutomate Deskera with Make.

What if every new deal in Deskera CRM started the paperwork for you? The Deskera Make integration gives you 15 modules: 2 instant triggers and 13 actions. This guide is for sales and finance teams on Deskera, and it walks you from the connection to a first working scenario.

Try the Deskera integration on MakeSee the 15 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Deskera Make integration automate?

The Deskera Make integration links your Deskera account to Make, a no-code tool where you build a scenario, meaning an automation made of a chain of modules. Each module is one brick: a trigger that starts the flow, or an action that creates something in Deskera. Deskera tells Make the moment a CRM contact or deal appears, and Make creates records on the other side.

A quotation ready as soon as the deal exists. Pair New CRM Deal Event with Create a Quotation, and the sales rep who logs an opportunity finds a draft quote waiting, built from the deal data Make passes along.

Suppliers and staff added from the tools where they already live. A purchase form, a signed contract or an onboarding spreadsheet in another app can feed Create a Bill, Create a Purchase, Create an Employee or Create a Contractor, so nobody types the same details twice into Deskera.

One contact, visible to sales and accounting. When New CRM Contact Event fires, Create a Contact can copy that person into the books, so the invoice team never hunts for an address.

What the catalog does not offer: there is no search module and no module that updates or deletes a record, and Make's own documentation for Deskera is marked as limited. For anything missing, the Make an API Call module reaches the Deskera API with the same connection. Deskera often has an n8n node too; the n8n vs Make comparison lays out how the two tools differ. Before you pick a plan, read Make pricing, and if you would rather learn the editor properly, Make training starts from the basics.

Connect

How do you connect your Deskera account to Make?

  1. 01

    Add a Deskera module

    Inside a scenario, click the +, type Deskera and pick any of its modules. The field for the connection appears first: that is your Deskera account linked to Make once, then reused by every Deskera module.

  2. 02

    Create the connection

    Click Create a connection and, if you like, give it a name that says which Deskera company it points to. A clear name saves confusion later when several people share the same Make organization.

  3. 03

    Authorize Make and save

    Make opens the Deskera page where you approve access, or asks for the key Deskera gives you. Confirm, click Save, and the connection is ready for every other Deskera module in your scenarios.

First scenario

Your first scenario: a quotation for every new Deskera deal

GoalWhen a deal is added in Deskera CRM, Make creates a matching quotation in Deskera.

  1. 01

    Create the scenario

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

  2. 02

    Pick the deal trigger

    Search for Deskera, choose New CRM Deal Event and select your connection, or click Create a connection if this is your first Deskera module.

  3. 03

    Add the quotation

    Click the + to the right of the trigger and add Create a Quotation. Map the deal data from the trigger into the fields Make shows once the connection exists.

  4. 04

    Test with Run once

    Click Run once, then add a test deal in Deskera CRM. Open the bubble above each module to read the bundle it received, meaning the single deal that flowed through.

  5. 05

    Switch it on

    When the quotation looks right, turn the scenario on. Because the trigger is instant, Deskera calls Make as each deal arrives, so there is no polling interval to tune here.

Triggers

What can start a Deskera scenario?

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

Deskera1New CRM Contact Event

New CRM Contact Event

Instant trigger

In Make“Triggers when a new contact is added to CRM.”

This trigger hands your scenario each person as soon as they land in Deskera CRM, so follow-up work begins without anyone exporting a list. Every new contact becomes one bundle for the modules that come next.

How it fires
instant: Deskera calls Make through a webhook as soon as the contact is added, instead of Make checking on a schedule.
When to use it
a lead captured by your sales team should also exist in accounting, or needs a welcome message sent from another app.
Watch out
it reacts to contacts in CRM only; for CRM+ records, test with Run once first to see what reaches Make.
Deskera2New CRM Deal Event

New CRM Deal Event

Instant trigger

In Make“Triggers when a new deal is added to CRM.”

With this trigger, a fresh opportunity in Deskera CRM becomes the starting signal for quotes, alerts or reporting elsewhere. Make receives the deal details and passes them to the next module as one bundle.

How it fires
instant: Deskera notifies Make through a webhook as soon as the deal is created, with no polling interval involved.
When to use it
your team wants a quotation drafted, or a manager notified in chat, the moment a rep opens a deal.
Watch out
it watches creation only, so a deal that changes stage later will not start the scenario again.
Modules

What can Make do in Deskera?

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

Deskera1

Create a Bill

Action

In Make“Creates a new bill on Deskera.”

Records a supplier bill in Deskera from data that arrives elsewhere, so payables stay complete without retyping each invoice you receive.

When to use it
a supplier invoice lands through a form, an email parser or a procurement tool, and finance wants it in Deskera right away.
Watch out
the catalog has no search module for Deskera, so nothing stops the same bill from being created twice if the source sends it twice.
Deskera2

Create a Contact

Action

In Make“Creates a new contact on Deskera.”

Adds a contact to Deskera. The CRM and CRM+ contact modules further down are separate modules, so this one most likely writes outside the CRM: check where it lands.

When to use it
a new CRM contact or a signed order should become a billable customer without someone copying the address by hand.
Watch out
because this module and the CRM ones write to different places, pick the one that matches where your team actually looks for the person.
Deskera3

Create a Contractor

Action

In Make“Creates a contractor to People on Deskera.”

Places a freelancer or contractor in the People area of Deskera, which keeps your external workforce next to your employees instead of in a separate sheet.

When to use it
a contractor signs through an e-signature tool or fills an onboarding form, and HR wants the profile ready in Deskera.
Watch out
for salaried staff choose Create an Employee instead; the two modules feed different records in People.
Deskera4

Create a CRM Contact

Action

In Make“Creates a contact in CRM.”

Drops a new lead or prospect straight into Deskera CRM, so your sales pipeline fills itself from the channels where people first reach you.

When to use it
someone submits a website form, books a demo or joins a webinar, and the sales team should see them in CRM.
Watch out
if your account runs on CRM+, this module is the wrong door; use Create a CRM+ Contact so the lead appears where your team works.
Deskera5

Create a CRM+ Contact

Action

In Make“Create a contact in CRM+”

Built for teams on Deskera CRM+, it creates the contact in that product, which keeps new leads visible to reps who never open the classic CRM.

When to use it
your company moved to CRM+ and leads come from forms, chat tools or event sign-ups.
Watch out
Make's documentation does not explain the difference between CRM and CRM+, so run the module once and check in Deskera where the contact shows up.
Deskera6

Create A Deal

Action

In Make“Creates a deal in CRM.”

Opens an opportunity in Deskera CRM for you, which turns a signal from another tool into something a rep can actually follow up and close.

When to use it
a prospect requests a quote on your site, or a lead reaches a certain score in your marketing tool.
Watch out
if the same scenario also uses New CRM Deal Event as its trigger, the deal it creates can fire the trigger again and start a loop.
Deskera7

Create an Account

Action

In Make“Create a new account on Deskera.”

Adds an account to Deskera from a scenario, so the structure your team relies on grows with the records created in your other tools.

When to use it
a new record in another tool should get a matching account in Deskera without an admin creating it manually.
Watch out
the documentation for this module is thin, so run it once on a test record and check in Deskera which kind of account it produced.
Deskera8

Create an Employee

Action

In Make“Creates an employee to People on Deskera.”

Registers a new hire in the People area of Deskera, which means onboarding starts from the HR tool or form where the offer was accepted.

When to use it
a candidate is marked hired in your recruiting app and should appear in Deskera before the first day.
Watch out
employee data is sensitive; keep this scenario on a connection owned by HR, and test it with a dummy profile before real hires flow through.
Deskera9

Create a Product

Action

In Make“Creates a new product on Deskera.”

Adds an item to your Deskera catalog, so the product exists before anyone tries to quote, buy or invoice it.

When to use it
a new article is published in your online store or approved in a spreadsheet, and Deskera needs it for sales and purchases.
Watch out
run this module before Create a Quotation or Create a Sales Invoice in the same scenario when those documents rely on the new item.
Deskera10

Create a Purchase

Action

In Make“Creates a new purchase on Deskera.”

Logs a purchase in Deskera from the tool where the buying decision happened, which gives finance visibility on spending as soon as it is approved.

When to use it
an approval workflow or a request form confirms an order to a supplier, and the record should reach Deskera without delay.
Watch out
a purchase is different from the bill that follows it; if you need both, chain Create a Bill later in the flow.
Deskera11

Create a Quotation

Action

In Make“Creates a new quotation on Deskera.”

Prepares a quote in Deskera for your prospect, cutting the gap between a rep's promise and the document the client actually receives.

When to use it
right after New CRM Deal Event, or when a request arrives from a form on your pricing page.
Watch out
if the quote may use an item Deskera does not know yet, add Create a Product earlier in the scenario.
Deskera12

Create a Sales Invoice

Action

In Make“Creates a new sales invoice on Deskera.”

Issues a sales invoice in Deskera from an event elsewhere, so billing follows the sale instead of waiting for someone to catch up on paperwork.

When to use it
an order is paid in your store, or a project is marked delivered in your management tool.
Watch out
this creates a real accounting document in Deskera; test on a sandbox customer with Run once before you switch the scenario on.
Deskera13

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the Deskera API with your existing connection, which covers what the ready-made actions leave out, such as updating a record, if the Deskera API allows it.

When to use it
you need to read, change or delete Deskera data and no listed module does it.
Watch out
you write the request yourself, so keep the Deskera API documentation open; Make's own guide for this app is marked as limited.
Need help

Need help automating Deskera with Make?

A person reads every message.

FAQ

Questions about the Deskera Make integration

01Is the Deskera Make integration free?
Yes, Deskera is a standard app in Make, so you can use it on the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops each run after 5 minutes and caps transfer at 512 MB. Paid plans, Core, Pro, Teams and Enterprise, lower the interval to 1 minute, remove the limit on active scenarios and allow 40 minutes per run. Make counts usage in operations, one per module per bundle. Your Deskera subscription is a separate matter.
02What do you need to connect Deskera to Make?
A Deskera account and a Make account are enough to begin, since Make's documentation lists no special prerequisite. You add a Deskera module, click Create a connection, optionally name it, authorize Make on the Deskera page or paste the key Deskera gives you, then click Save. The connection is reused by every Deskera module afterward. Because the documentation is marked as limited, check that you sign in to the right Deskera company when the authorization page opens.
03Do the Deskera triggers fire instantly?
Yes, both of them. New CRM Contact Event and New CRM Deal Event are instant triggers: Deskera calls Make through a webhook as soon as a contact or deal is added, so your scenario does not wait for a schedule. That instant behavior covers creation only. There is no Deskera trigger for updates, invoices or purchases, so a flow that starts from those needs another source, such as a trigger from a different app or Make's own scheduling on a first module.
04What if the Deskera module you need is missing?
Use Make an API Call. It calls any endpoint of the Deskera API with the connection you already set up, which is how you try an update or a deletion, since the catalog only offers creation modules and no search, provided the Deskera API allows it. You write the request yourself, so the Deskera API reference becomes your guide. Keep in mind that Make's own documentation for Deskera is flagged as limited, and test each call with Run once before relying on it.
05Should you use Make or n8n for Deskera?
It depends on the tool your team already runs. Deskera has a module set in Make, with 2 instant triggers, 13 actions and Make an API Call for the rest, and the app often exists as a node in n8n too. Compare the two catalogs against the records you need to create or read, then check which editor your team finds easier to maintain. Neither choice changes what Deskera itself allows through its API.
Same platform

Other docs you might need on this stack.

Browse all integrations