- Home
- Resources
- Integrations
- Deskera
Deskera Zapier integrationAutomate Deskera with Zapier.
The Deskera Zapier integration gives you 6 triggers and 12 actions, and no search. Every trigger is instant, so a Zap on the free plan starts just as fast as on a paid one. Read on 1 October 2026, app version DeskeraCLIAPI@1.10.10.
Verified Trustpilot reviews · AI, automation & growth agency
What the Deskera Zapier integration actually does for you
The Deskera Zapier integration links your Deskera account to Zapier so that something happening in Deskera (a contact, a deal, a product) starts an automation, and so that other steps can write into Deskera for you: contacts, deals, quotes, orders, invoices, bills, accounts and products.
Three uses that fit what it exposes. A sales team and a finance team that see the same customer: New CRM+ Contact fires, and Create a New Contact opens the matching record on the books side. A deal that lands in the pipeline from somewhere else: Create a New Deal in CRM drops it into the right pipeline and stage, and Update an Existing Deal in CRM moves it later. A catalogue kept in one place: New Product fires on each product you add, so anything downstream learns about it at once.
Here is what Zapier does not do for this app. There is no search step, so a Zap cannot look up an existing Deskera contact or deal before writing. Nothing gets edited apart from CRM deals, and nothing gets deleted. And the sales documents (quotation, order, sales invoice, bill) ask for a long list of mandatory fields, so they suit a Zap fed by an app that already holds line items and addresses.
If you would rather compare tools before you commit, the Deskera Make integration page covers the same app on Make, and our Zapier review looks at the platform as a whole.
Zapier words in one minute
Seven terms, and you will read the rest of this page without a dictionary.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for that event.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you in an app.
- Task
- The unit Zapier bills you for: one action your Zap completes successfully. Your plan's allowance is a count of these.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is pushed by the app the moment the event happens. All six Deskera triggers are instant.
- Filter
- A step that lets the Zap continue only when what arrived meets a condition you set, and stops it quietly otherwise.
- Search step
- A step that looks up an item that already exists in an app so later steps can reuse it. Deskera offers none on Zapier.
What it really costs to run Deskera on Zapier
Deskera is not a premium app, so it works on the free plan. The bill is counted in tasks, and only finished actions count.
- Free plan100 tasks a month, unlimited Zaps, two steps per Zap
- Premium appNo, Deskera runs on the free plan
- Deskera triggers6 instant, 0 polling
The trigger never costs a task, and neither does Zapier waiting for new data. Each action that succeeds is one task, counted separately: a Zap with three actions uses three times what a one-action Zap uses. An action that fails is not counted. The free plan stops at two steps, one trigger and one action. Add a second action or a filter and you have a multi-step Zap, which needs a paid plan. The interval grid below only concerns polling triggers, so it never slows a Deskera Zap down.
Connect your Deskera account in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is your Deskera account linked once, then reused by every step that talks to Deskera.
- 02
Find Deskera and confirm
Type Deskera in the search box of the dialog, pick it from the list, then click Add connection. You need a Deskera account to sign in to, nothing more at this stage.
- 03
Sign in and grant access
Log in to Deskera in the tab that opens and allow Zapier to reach the account. If the Zap will touch records you do not own, make sure your user has read or write rights on them first.
Your first Zap: accounting contacts that show up in the CRM with a deal
GoalEach new contact created on the books side of Deskera also appears in the classic Deskera CRM, with a deal already open in the pipeline and stage you choose.
- 01
Build: pick the trigger
Start a new Zap in the editor, choose Deskera as the app and New Contact as the event, then select the Deskera connection you just created.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent contacts of your account, so you map fields on a real record instead of a blank one.
- 03
Add the CRM contact
Click the plus icon and choose Deskera with Create a New Contact in CRM. Two fields are mandatory, Name and Type: map the name from the contact the test brought back and set the type once.
- 04
Open the deal
Add a second Deskera action, Create a New Deal in CRM. Name, Pipeline, Stage and Closing Date are mandatory: pick the pipeline and the first stage once. This second action makes the Zap multi-step, so it needs a paid plan.
- 05
Test, then Publish
Test both actions and open Deskera CRM to check the contact and the deal really arrived. Then click Publish to switch the Zap on. On the free plan, keep only the first action: two steps.
Deskera triggers on Zapier
6 events start a Zap when something happens in Deskera, and 6 of them are instant: the app calls Zapier straight away, whatever your plan.
New CRM+ Contact
Instant triggerIn Zapier“Triggers when a New Contact is Created in CRM+.”
Starts your Zap each time someone adds a contact in the CRM+ module of Deskera, so the person can travel to the rest of your tools without retyping.
New CRM+ Deal
Instant triggerIn Zapier“Triggers when a New Deal is Created in CRM+.”
Reacts to each deal that appears in Deskera CRM+, which makes it the natural start for anything that should happen once an opportunity exists.
New Contact
Instant triggerIn Zapier“Triggers when a New Contact is Created.”
Fires on contacts created in the accounting side of Deskera, the records that carry codes, currency and payment terms.
New CRM Contact
Instant triggerIn Zapier“Triggers when a New Contact is Created in CRM.”
Picks up every contact added in the classic Deskera CRM module, distinct from CRM+ and from accounting contacts.
New CRM Deal
Instant triggerIn Zapier“Triggers when a New Deal is Created in CRM.”
Launches the Zap when a deal is opened in the classic CRM module of Deskera, ahead of any work on pricing or delivery.
New Product
Instant triggerIn Zapier“Triggers when a New Product is Created.”
Goes off when someone adds a product to Deskera, which keeps every other step in the loop on your catalogue without a manual export.
Deskera actions on Zapier
Deskera gives you 12 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create a New Account
ActionIn Zapier“Creates a new Account on a specified action”
Adds an account to your chart of accounts in Deskera, with its code, group, tax code, currency and status.
Create a New Bill
ActionIn Zapier“Creates a new Bill on a specified action”
Enters a supplier bill in Deskera, the purchase side of your books, with products, taxes, totals and due date.
Create a New Contact
ActionIn Zapier“Creates a new Contact on a specified action”
Opens a full accounting contact in Deskera: billing and shipping addresses, currency, payment terms, and whether it is a customer or a vendor.
ACC30001 and ACC40001), so have your own codes ready before mapping.Create a New Contact in CRM+
ActionIn Zapier“Creates a new Contact in CRM+ on a specified action”
Adds a person to the CRM+ module of Deskera, so the sales team works from one list.
Create a New Contact in CRM
ActionIn Zapier“Creates a new Contact in CRM on a specified action”
Opens a contact in the classic CRM of Deskera from data another step carried, with only two mandatory fields.
Create a New Deal in CRM
ActionIn Zapier“Creates a new Deal in CRM on a specified action”
Places a deal straight into a pipeline and a stage of the classic CRM, with a closing date already set.
Create a New Sales Invoice
ActionIn Zapier“Creates a new Sales Invoice on a specified action”
Issues a sales invoice in Deskera with its line items, discount, tax, due amount and invoice dates.
Create a New Sales Invoice - Shopify Integration
ActionIn Zapier“Creates a new Sales Invoice on a specified action”
A sales invoice variant shaped around a Shopify order: order ID, line items, taxes, discounts and the billing and shipping location.
Create a New Order
ActionIn Zapier“Creates a new Order on a specified action”
Records a sales order in Deskera with delivery date, due date, addresses, currency and total amount.
Create New Product
ActionIn Zapier“Creates a new Product on a specified action”
Registers a product in Deskera together with the purchase, sales, inventory and cost of goods sold accounts it books to.
Create a New Quotation
ActionIn Zapier“Creates a new Quotation on a specified action”
Drafts a quotation in Deskera with the customer, addresses, dates, product lines and totals already filled in.
Update an Existing Deal in CRM
ActionIn Zapier“Updates an Existing Deal in CRM on a specified action”
Changes a deal that already exists in the classic CRM, for instance its stage or closing date, instead of creating a duplicate.
When a Deskera Zap breaks
Zapier links no help article to Deskera and lists no rate limit for it. What breaks is the general behaviour of Zaps.
Four cases cover what you will meet. None is specific to Deskera, and each one is avoidable once you know it. When something still goes wrong, our Zapier troubleshooting guide is the next stop.
Old records never come through
A Zap only reacts to what happens after you publish it. Contacts and deals created before that stay where they are; moving the backlog is a separate job.The Zap that sets itself off
New Product plus Create New Product on the same account is a loop: each run creates a product, which fires the trigger again and drains your tasks fast.A bulk import gets held back
Importing hundreds of contacts at once can send a huge batch to the trigger. Zapier's flood protection may then hold those runs back.The filter that never runs
On the free plan a Zap stops at one trigger and one action. Add a filter or a second action and it becomes multi-step, so it will not run without a paid plan.
Need help automating Deskera with Zapier?
A person reads every message.



