FlowRunner
PricingContact
Theme
Start Free

iCount

Accounting

iCount is the Israeli cloud accounting and invoicing system. Agents manage clients and their balances, create, cancel, and email documents, send pay now links, log and scan expenses, and react to new activity in real time.

1 trigger 57 actions API key available
iCount website Platform Documentation Capability data verified 2026-08-24
An order settles in the storefront and reaches the agent
Get Client resolves the buyer on your own customer identifier rather than on a name
The agent reads the lines and the payment detail from the order
Get VAT Rate returns the rate that applied on the document's own date
Create Document issues the document with its payment detail in a single call
The document is delivered to the customer and the day's issues are summarized for finance
The finance owner decides on anything the agent proposed canceling, because a cancellation can refund a card

What This Integration Enables

iCount is the Israeli cloud accounting and invoicing system, and one property of the market it serves defines what an agent may and may not do here. Once a tax document is issued it stands: it cannot be edited and it cannot be deleted. The correction is Cancel Document, which writes a reversing document, and both stay on the record. Everything an agent does with documents in this connector is shaped by that, and it is a better foundation than it sounds, because it makes the boundary between reversible and irreversible unusually clear rather than leaving it to a policy nobody wrote down.

FlowRunner agents work the whole cycle inside that boundary. They maintain clients as a true upsert matched on your own identifier, the tax number, or the email address, read balances, ledgers, and open documents, issue documents with their payment detail in a single call, deliver them by email or message, produce a self-service payment link with an expiry, file expenses through the platform's own reading of a scanned document, maintain suppliers and inventory, and pull the account's reports. Two API behaviors are handled for you rather than left as traps: iCount answers a successful HTTP status for a failed call and reports the problem in the body, and an unknown method answers with an HTML page, and the connector reads both and raises so a flow fails visibly. A document is addressed by its type code and number rather than by a global identifier, so List Document Types is the first call in almost any document flow. The decisions that move money rather than records are where FlowRunner's human-in-the-loop design puts a person.

Without FlowRunner

Identifiers stored twice Every system that talks to the books has to remember the accounting system's own numbers
Receipts issued in two steps The invoice is created, then somebody records the payment against it separately
Corrections attempted as edits A wrong document is fixed by trying to change it, and the fix is discovered to be unavailable

With FlowRunner

Identifiers stay yours Clients and documents are found by your own customer identifier, VAT number, or email
Payment travels with the document The document and its cash, card, cheque, or transfer detail are issued in one call
Corrections issued as documents A reversing document is drafted with its reasoning, and a person approves before it is issued

Use Case Scenarios

  • One call, one document, one payment

    An order settles in Shopify or a charge captures in Stripe. The agent resolves the buyer with Create Or Update Client, which is a genuine upsert: iCount matches on the client identifier, your own customer identifier, or the tax number, and creates only when none of them matches. Setting your identifier at creation means no flow afterwards has to store iCount's numbering. Create Document then issues the document and carries the payment detail with it, whether that is cash, cheques, a bank transfer, a card, or a payment provider, and links it to the invoice it settles. Get VAT Rate is called with the document's own date rather than today's, because the rate that applies is the one that applied then. Delivery happens in the same call, with the document emailed or messaged as it is created. Where the customer still has to pay, Get Pay Now Link produces a self-service payment page with an optional click limit and expiry instead of a bank detail pasted into an email.

  • Supplier paper, read and filed with its certificate checked

    Supplier invoices arrive as images. Scan Expense Document lets iCount read the supplier, number, date, and amount off the file, and Create Expense files the result with the scan attached, which is what makes the expense auditable rather than merely recorded. The agent reconciles the parsed amount against the purchase order and files what matches. One check happens before any payment is scheduled: the supplier record carries a withholding percentage and a validity date, so an expired certificate is a fact the agent can see rather than something discovered at payment time. Suppliers with an expired or missing certificate are listed for the finance owner in Slack ahead of the payment run, with the last date each one was valid.

  • Duplicates, and the merge that cannot be undone

    Client records duplicate, especially where a business trades under two names. A weekly sweep searches clients on tax number, email, and name, and assembles each candidate pair with the evidence that matters: Get Client Balance for both, Get Client Open Documents for both, and Get Client Ledger for the longer history. It posts the comparison to the finance owner and stops. Merge Clients is irreversible: every document and activity moves and the source profile is deleted, and there is no unmerge. The person names the survivor, the agent runs the merge, and the outcome appends to a tracking sheet in Google Sheets so the pattern of where duplicates come from is visible over time. Delete Client usually refuses a client that has documents, which is the platform protecting history rather than an obstacle.

Human-in-Loop Highlight

Cancel Document looks like bookkeeping and is not always only bookkeeping. Because an issued Israeli tax document cannot be edited or deleted, canceling is the correct and expected way to fix one, and on its own it writes a reversing document that leaves both on the record. But the same call carries a credit card refund option, and when the original document was paid by card, setting it moves real money back to the customer's card. That is a financial movement wearing the clothes of a correction, and an agent processing a queue of disputed invoices will meet both cases in the same batch. So the disputes agent drafts and stops. It posts: "Invoice receipt 4471 for Levi Trading, 8,900 ILS, paid by card on 12 August. The customer disputes two lines totaling 1,420 ILS. Canceling issues a reversing document. Canceling with the refund option also returns 8,900 ILS to their card, which is more than the disputed amount. Cancel without refund and issue a corrected document, cancel with refund, or hold?" A person answers in one message. Issuing documents, reading ledgers, matching payments, and drafting the reversal were all the agent's work. Deciding that money leaves the account was not.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

57 actions

Account

3
  • Get Account Info Returns the authenticated account. A token inherits its user's permissions exactly, so this is how a flow confirms what it is allowed to do.
  • Get Company Info Reads the company's details as they will print on documents.
  • List Company Bank Accounts Lists the company's own bank accounts, which is what a payment instruction references.

Clients

11
  • List Clients Lists clients, searchable by your own customer identifier, tax number, or email address.
  • Get Client Retrieves one client, found by any of the same identifiers.
  • Create Or Update Client A true upsert. iCount matches on the client identifier, your own customer identifier, or the tax number, and creates only when none of them matches.
  • Delete Client Removes a client. Usually refused for a client that has documents, which protects the history behind them.
  • Merge Clients Merges one client into another. Every document and activity moves and the source profile is deleted, and there is no unmerge.
  • Get Client Balance Returns what a client owes. The number behind a chase or a credit decision.
  • Get Client Ledger Returns the client's transaction history.
  • Get Client Open Documents Lists a client's unsettled documents. The evidence a receipt needs before it can settle anything.
  • List Client Types Lists the client type codes the account uses.
  • Get Client Custom Fields Reads the custom fields defined on client records, so a flow writes fields that exist.
  • Add Client Contact Adds a contact person to a client.

Documents

14
  • Search Documents Finds documents by type, date, client, or your own identifiers. The entry point to almost every document flow.
  • Get Document Retrieves one document, addressed by its type code and number, because there is no global document identifier.
  • Create Document Issues a document and carries its payment detail in the same call, covering cash, cheques, bank transfers, cards, and payment providers, with delivery by email or message as it is created.
  • Cancel Document Issues a reversing document, which is how an issued tax document is corrected. The credit card refund option on this call moves real money back to the customer, which is why this page's human gate sits here.
  • Close Document Marks a document settled without changing the document itself. Naming the base documents also closes them and updates their remaining amounts, which is how a receipt settles an invoice.
  • Reopen Document Returns a closed document to open. The settled flag moves, the document does not.
  • Email Document Emails an issued document to the client.
  • Send Document SMS Sends the document to the client by text message.
  • Get Document URL Returns a link to the document for use in a message or a record.
  • Get Pay Now Link Produces a self-service payment page for a document, with an optional click limit and expiry.
  • Download Document PDF Fetches the document as a file into FlowRunner file storage.
  • List Document Types Lists the type codes and what each type supports, covering tax, items, payments, due dates, and discounts. The only place those codes are published, and the first call in a document flow.
  • Get Next Document Numbers Returns the next number in each sequence, so a flow can reference a document before it exists.
  • List Payment Methods Lists the payment methods the account accepts.

Expenses

8
  • Search Expenses Finds recorded expenses by supplier, date, or type.
  • Get Expense Retrieves one expense with its detail and attached scan.
  • Create Expense Files an expense, taking the scanned document alongside the fields, which is what makes it auditable.
  • Update Expense Corrects a recorded expense.
  • Delete Expense Removes an expense record.
  • Scan Expense Document Sends an image for reading, returning the supplier, number, date, and amount from the file.
  • List Expense Types Lists the expense type codes the account uses.
  • List Expense Document Types Lists the document types an expense can reference.

Suppliers

4
  • List Suppliers Lists suppliers, including the withholding percentage and validity date held on each record.
  • Create Supplier Creates a supplier record.
  • Update Supplier Updates a supplier, including the withholding certificate details a payment run reads.
  • Delete Supplier Removes a supplier record.

Inventory

9
  • Search Inventory Items Finds stock items by code, name, or warehouse.
  • Get Inventory Item Retrieves one item, including whether its unit price is held inclusive of tax.
  • Create Inventory Item Adds an item to the catalog.
  • Update Inventory Item Updates an item. Setting stock here writes an absolute level, which is a correction rather than a movement.
  • Delete Inventory Item Removes an item from the catalog.
  • Adjust Inventory Stock Adds or removes a quantity, which records a movement rather than overwriting a level.
  • Move Inventory Item Moves stock between warehouses.
  • List Warehouses Lists the warehouses stock is held in.
  • Get Inventory Summary Returns stock levels across the catalog. The read behind a reorder decision.

Reports

1
  • Get Report Runs one of the account's reports. The tax and income reports take month ranges while the others take dates, and the connector sends whichever the chosen report expects.

Reference

3
  • Get Reference List Reads any of the account's reference lists in one operation, covering the code sets documents and records have to reference.
  • Get VAT Rate Returns the rate that applied on a given date, which is the rate a back-dated document needs rather than today's.
  • Get Currency Rate Returns the exchange rate for a currency and date.

Webhooks

4
  • List Webhook Actions Lists the action names this account supports. The list is per account, so this is the call that says what can be subscribed to.
  • List Webhooks Lists the webhooks registered on the account.
  • Create Webhook Registers a webhook against an endpoint of your choosing, separate from the trigger below.
  • Delete Webhook Removes a registered webhook.

Triggers

1 triggers

Event Triggers

1
  • On iCount Event Fires on an iCount webhook action you name. Because the platform publishes neither the list of action names nor the delivery shape except through an authenticated call, the trigger cannot tell one delivery from another by reading it. Each trigger instead registers its own callback URL carrying its identifier, and the match is made on that, which is reliable regardless of what iCount sends. Run List Webhook Actions first to see which action names your account supports, which is why the action is entered as text rather than picked from a list.

Frequently Asked Questions

What can FlowRunner do with iCount?

FlowRunner agents can run Get Account Info, Get Company Info, and List Company Bank Accounts in iCount, plus 54 more actions.

Does connecting iCount to FlowRunner require OAuth?

No. iCount connects to FlowRunner with an API key, no OAuth flow required.

Can iCount trigger a FlowRunner workflow automatically?

Yes. iCount supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with iCount

Free plan, no card required. Connect in minutes.