Resources · Make integration

iCount Make integrationAutomate iCount with Make.

Can iCount keep up with the rest of your tools without retyping? The iCount Make integration gives you 20 modules: 18 actions and 2 searches across expenses, inventory, documents, clients, CRM and time punches. This guide shows how to link your account and build a first working scenario.

Try the iCount integration on MakeSee the 20 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the iCount Make integration do for you?

The iCount Make integration lets Make read and write data in your iCount account, with no code. You build a scenario, the automation made of bricks called modules, and each iCount module handles one job: record an expense, adjust stock, issue a document, update a client, log a punch.

Sales paperwork without copy and paste. When a deal closes in your CRM or a form comes in, Crete/Update a Client makes sure the customer exists in iCount, then Create a Document issues the paperwork from the same data. Search Documents lets a later step look up what was already issued.

Stock that follows your sales. An order in your online store can feed Reduce a Quantity to Stock, and a delivery note from a supplier can feed Add a Quantity to Stock. Create an Item keeps the catalog in step when a new product appears elsewhere.

Hours and leads captured where they happen. Punch In and Punch Out let a button, a chat command or a calendar event clock a team member, while Create a Lead, Create a Task and Create an Event push prospects and follow-ups into the iCount CRM.

One thing to know before you start: iCount has no trigger in Make, so a scenario never starts from iCount itself. It starts from another app or from a schedule, and the iCount modules do the work after that. When a module is missing, Make an API Call reaches the rest of the iCount API. If you are weighing the two platforms, read n8n vs Make; for plans and operation counts, see Make pricing; and if a run fails, Make troubleshooting walks through the usual fixes.

Connect

How do you connect iCount to Make?

  1. 01

    Find your iCount credentials

    Log in to iCount and click your profile icon in the top-right corner. It shows Company followed by your company name and User followed by your username. Copy both. The email iCount sent after your registration holds them too.

  2. 02

    Open the connection window in Make

    Add any iCount module to your scenario and click Create a connection. A connection is your iCount account linked to Make once, then reused by every iCount module. Give it a clear name in Connection name if you like.

  3. 03

    Fill in the three fields and save

    Paste the username in Username, the company name in Company Identifier, and type your iCount password in Password. Click Save, then authenticate and confirm access if iCount asks for it.

First scenario

Your first scenario with iCount

GoalWhen a new customer comes in from another app, Make updates the client in iCount and issues a document for them.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. The first module comes from the app where your customers arrive, such as your form tool or store, since iCount has no trigger.

  2. 02

    Add Crete/Update a Client

    Click the + to the right of the first module, search for iCount and pick Crete/Update a Client. Create your connection, then map the customer data from the previous module into the fields.

  3. 03

    Add Create a Document

    Click the + again and choose Create a Document. Map the client returned by the previous module so the document lands on the right customer record in iCount.

  4. 04

    Test with Run once

    Click Run once and send one test customer through the first app. Open each module's output to read the bundle, the single item it received, and confirm the document in iCount.

  5. 05

    Schedule and switch on

    On the first module, set the schedule, every 15 minutes by default, or keep it instant if that app supports it. Then switch the scenario on so it runs without you.

Modules

What each iCount module does

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

Expenses

1 module
iCount1

Add an Expense

ActionIn the docs only

Records a new expense in iCount from data another app already holds, so receipts and supplier bills stop waiting for manual entry.

When to use it
a receipt is scanned, a card payment is logged or an expense form is submitted, and you want it in your books at once.
Watch out
each run records one more expense, so a test repeated with Run once leaves copies to clean up.

Inventory

5 modules
iCount2

Create an Item (Inventory)

ActionIn the docs only

Adds a new product to your iCount inventory, which keeps your catalog aligned with the place where products are first defined.

When to use it
a product is published in your store or added to a spreadsheet and should exist in iCount before the first sale.
Watch out
run Update an Item for a product that already exists, or you end up with two entries for the same thing.
iCount3

Update an Item (Inventory)

ActionIn the docs only

Changes the details of a product already in your iCount inventory, so a correction made elsewhere reaches your accounting side too.

When to use it
a product record is corrected in the tool your team edits first.
Watch out
this module edits a known item; it does not change stock levels, which have their own two modules below.
iCount4

Delete Items (Inventory)

ActionIn the docs only

Removes products from your iCount inventory, which helps when discontinued lines should vanish from the catalog automatically.

When to use it
a product is archived in your store or flagged as discontinued in a sheet.
Watch out
check which items you point it to, and test it on a dummy item with Run once before letting a schedule run it.
iCount5

Add a Quantity to Stock (Inventory)

ActionIn the docs only

Raises the stock count of an item in iCount, so incoming goods show up without anyone opening the inventory screen.

When to use it
a supplier delivery is confirmed, a return is received or a production batch is marked done.
Watch out
it adds on top of the current count; running the same delivery twice counts it twice, so filter out bundles already handled.
iCount6

Reduce a Quantity to Stock (Inventory)

ActionIn the docs only

Lowers the stock count of an item in iCount, keeping inventory honest as sales happen in other channels.

When to use it
an order is paid in your online store or a marketplace, and the sold quantity should leave your iCount stock.
Watch out
an order with several lines needs one run per line, so place an iterator from Make before this module.

Docs

4 modules
iCount7

Get a Document

ActionIn the docs only

Fetches one iCount document you already know, so the next modules can reuse its content instead of asking someone to look it up.

When to use it
another app stores the reference of an invoice and you need its details to send a reminder or update a record.
Watch out
you need to know which document you want; if you only have clues, start with Search Documents.
iCount8

Search Documents

SearchIn the docs only

Looks through your iCount documents and returns the matches, which lets a scenario check what was already issued before acting.

When to use it
you want to avoid issuing the same document twice, or to gather documents for a report in a spreadsheet.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per result.
iCount9

Create a Document

ActionIn the docs only

Issues a new document in iCount from data collected elsewhere, the step that turns a sale or a signed deal into paperwork.

When to use it
an order is paid, a quote is accepted or a booking is confirmed in another tool.
Watch out
pair it with Crete/Update a Client first, so the document is attached to a customer who really exists in iCount.
iCount10

Cancel a Document

ActionIn the docs only

Cancels an existing iCount document, so a refund or a cancelled order elsewhere is reflected in your records without manual work.

When to use it
an order is refunded in your store or a booking is called off in your scheduling tool.
Watch out
the module acts on the document you point it to, so find the exact document with Search Documents or Get a Document before cancelling anything.

Clients

3 modules
iCount11

Search Clients

SearchIn the docs only

Finds customers in your iCount client list and hands the matches to the next modules, handy for checking before you create anything.

When to use it
a new contact arrives by email or form, and you want to know whether iCount already knows them.
Watch out
no match means no bundle, so the following modules simply do not run, and nothing warns you about it.
iCount12

Crete/Update a Client

ActionIn the docs only

Creates a customer in iCount or updates one that is already there, so your client file stays current from a single module. Make spells its name with a typo, search for it as shown.

When to use it
a customer signs up, changes an address in your store or is won in your CRM.
Watch out
map the same identifying data every time so an update does not turn into a second client.
iCount13

Get a Client Info

ActionIn the docs only

Reads the details of one iCount client, so another app can reuse them without anyone copying fields by hand.

When to use it
a support ticket or a shipment needs the customer data kept in iCount.
Watch out
it reads a single known client; when you only have a name or an email to go on, run Search Clients before it.

CRM

3 modules
iCount14

Create a Lead

ActionIn the docs only

Adds a prospect to the iCount CRM, so interest captured on your site or in a chat is not lost in an inbox.

When to use it
a contact form, a webinar sign-up or an ad form delivers a new prospect.
Watch out
leads and clients are separate modules; once the prospect buys, use Crete/Update a Client to turn them into a customer record.
iCount15

Create a Task

ActionIn the docs only

Puts a to-do in the iCount CRM, so follow-ups appear where your team already works instead of in a separate list.

When to use it
a lead is created, a quote goes unanswered in your email tool or a document is cancelled and someone must call the customer.
Watch out
one task per run; chain it right after Create a Lead so every prospect gets a follow-up.
iCount16

Create an Event

ActionIn the docs only

Places an event in the iCount CRM, which keeps meetings booked in other tools visible next to the client history.

When to use it
a meeting is booked through your scheduling tool or accepted in your calendar.
Watch out
this module only creates; a meeting moved in the source app will not move the event already placed in iCount.

Punchio

3 modules
iCount17

Punch In

ActionIn the docs only

Clocks a team member in on the iCount Punchio time clock, which removes the need to open iCount at the start of a shift.

When to use it
someone taps a button on their phone, sends a command in your team chat or checks in on site.
Watch out
check with Get a Status (Punch) first, so a double tap does not clock the same person in twice.
iCount18

Punch Out

ActionIn the docs only

Clocks a team member out on Punchio, closing the shift that Punch In opened so hours add up correctly.

When to use it
the same button, chat command or check-out that started the day ends it.
Watch out
a punch out without a matching punch in makes no sense; read the status first and route the scenario based on it.
iCount19

Get a Status (Punch)

ActionIn the docs only

Tells you whether a team member is currently punched in or out, the check that keeps your time tracking clean.

When to use it
a single button should toggle a shift, and the scenario must decide between Punch In and Punch Out.
Watch out
make the next step depend on the status it returns, or both punch modules will run one after the other.

Other

1 module
iCount20

Make an API Call

ActionIn the docs only

Calls any endpoint of the iCount API with your existing connection, which covers what the listed modules leave out.

When to use it
you need an iCount feature with no dedicated module in Make, and the iCount API offers it.
Watch out
you write the request yourself, so keep the iCount API documentation open and test with Run once before going live.
Need help

Need help automating iCount with Make?

A person reads every message.

FAQ

Questions about the iCount Make integration

01Is the iCount Make integration free?
Yes on the Make side: iCount is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs no more often than every 15 minutes, and caps each run at 5 minutes. Paid plans lower the interval to 1 minute and lift the scenario limit. Every module run on one bundle counts as one operation on your plan. The iCount side is different: Make needs a paid iCount account or an iCount free trial to connect.
02What do you need to connect iCount to Make?
You need a paid iCount account or a free trial, plus three pieces of information: your username, your company identifier and your password. The username and company name appear when you click your profile icon in the top-right corner of iCount, and they are also in the email iCount sent after you registered. In Make, click Create a connection on any iCount module, fill in Username, Company Identifier and Password, then click Save and confirm access if prompted.
03Can iCount start a Make scenario in real time?
No. iCount has no trigger module in Make, scheduled or instant, so a scenario cannot start from something that happens inside iCount. Start it from another app instead: a form, a store or a CRM, with an instant trigger when that app offers one. You can also start it on a schedule set on the first module, every 15 minutes by default, or once a minute at best on a paid plan, and let Search Documents or Search Clients pick up the data to process.
04What if an iCount module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the iCount API with the connection you already set up, so you are not limited to the 18 actions and 2 searches in the list. You write the request yourself from the iCount API documentation, and it is worth testing with Run once before you schedule it. The Make documentation for iCount gives no figures on limits, so there is no documented cap to plan around.
05Make or n8n for iCount?
It depends on the tool you already use. In Make, iCount comes with 20 ready modules covering expenses, inventory, documents, clients, CRM and Punchio time tracking, and it runs from the Free plan. Apps listed in Make often have an n8n node as well, so check the n8n side for iCount before choosing. The fair test is the same on both: can the modules you need do the job, and can the missing part be covered by an API call.
Same platform

Other docs you might need on this stack.

Browse all integrations