iDoklad
AccountingiDoklad is Czech and Slovak online invoicing software from Solitea. Agents manage contacts and documents, send invoices and payment reminders, record payments, pair bank statements, and maintain price list items.
What This Integration Enables
iDoklad is Czech and Slovak invoicing software from Solitea, and the thing that makes it worth automating is also the thing that makes hand written integrations fail. The rules live in the agenda, not in your code. An issued invoice needs a currency, a numbering sequence, a payment option, a partner, three dates, a description, and a serial number before iDoklad will take it, and none of those can be guessed for a particular set of books. So the API hands you a filled in template and expects you to modify it. FlowRunner agents work that way around: read the agenda's own defaults, change what the transaction actually changes, recalculate the totals, then create the document.
The same discipline applies on the money side. Agents record payments, mark documents fully paid, import bank movements, and pair those movements to the documents they settle, which is the step that turns a bank line into a payment. They maintain contacts and price list items, download PDFs and attachments, and read the server computed statistics for overdue amounts and top debtors instead of pulling every invoice to add it up locally. What they do not do is decide who gets chased. That is where FlowRunner's human-in-the-loop gate sits on this connector, and the rest of the page explains why it sits there rather than somewhere more obvious.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
Reconcile first, then chase
A weekly agent starts with Get Statistics, which computes overdue amounts and top debtors on the server rather than making the flow read the whole register. It then calls List Bank Statements for movements that have not been paired yet and matches them against open documents on amount and variable symbol. Anything that matches exactly one document goes through Pair Bank Statement, which is what actually converts a bank line into a payment. Only what survives that pass reaches a person. The point is ordering: a reminder sent to a customer whose money is already sitting unpaired in the bank is a self inflicted wound, and this sequence closes that window before anyone gets an email.
-
Storefront order to Czech invoice, built from the agenda
An order arrives from Shopify or a payment settles in Stripe. The agent calls List Contacts to resolve the buyer, creating one from Get Default Contact when the buyer is new so the contact inherits the agenda's defaults instead of a blank record. It then calls Get Default Document for the issued invoice register, replaces the partner and the lines, and calls Recount Document to see the VAT, discounts, and totals worked out before anything is saved. If the recalculated total does not agree with what the storefront charged, the flow stops rather than creating a document that will need a credit note later. When it agrees, Create Document writes the invoice and Download Document PDF stores the file for the order record.
-
A month end pack nobody assembles by hand
At period close, an agent reads Get Statistics for the invoicing summary, the overdue view, the quarterly summary, and the VAT totals, then writes each into a tab in Google Sheets and posts the headline movements into Slack. Where a figure needs backing detail, it calls List Documents with iDoklad's own filter syntax against the register in question and attaches the PDFs it downloads. The accountant opens a pack that was built from live figures rather than a fortnight old export, and the numbers on it were computed by iDoklad rather than re-added by a script.
Human-in-Loop Highlight
Send Payment Reminder is the operation on this connector that reaches a customer's inbox and cannot be recalled, and the reason it needs a person is not that dunning is scary. It is that iDoklad's ledger and iDoklad's bank movements are two different things until Pair Bank Statement runs. An invoice can be fully paid, with the money visible in List Bank Statements, and still read as overdue to anything that only looks at the document. So the sweep agent pairs everything it can match unambiguously, then stops and posts the remainder: "Eleven invoices are still open past terms. Nine have no bank movement anywhere near their amount. Two have a movement that matches the amount but carries a different variable symbol, so I did not pair them. Which of these eleven do we remind?" A person reads the two ambiguous ones, answers, and the agent sends only what was approved. The agent did the reconciliation, the arithmetic, and the drafting. The judgment about which customer relationship can absorb a chase stayed with a person.
Agent Capabilities
42 actionsAgenda and Account
3- Get Current Agenda Reads the agenda this connection is authorized for, which is the set of books every other operation works in. Worth calling first in any flow that could reach more than one.
- Get Current User Reads the iDoklad user the connection acts as, which is what its permissions follow from.
- List Agendas Lists the agendas the user can reach, so a multi entity flow can route a document to the right books.
Contacts
6- List Contacts Lists the contacts of an agenda with filtering, sorting, and paging. The lookup behind every match before a document is created.
- Get Contact Reads one contact in full, used to gather billing details before a write or a decision.
- Get Default Contact Reads a pre-filled contact template carrying the agenda's defaults. This is what a new contact should be built from rather than a blank object.
- Create Contact Creates a contact in an agenda, normally from the default template with the buyer's details applied over it.
- Update Contact Updates a contact. The identifier travels in the body rather than the path, which is how iDoklad's update routes work.
- Delete Contact Deletes a contact from an agenda.
Documents
11- List Documents Lists the documents of one register: issued invoices, proformas, credit notes, received invoices, sales receipts, sales orders, cash vouchers, recurring invoices, received receipts, or issued tax documents. The register is a parameter, so one operation covers all ten.
- Get Document Reads one document with its line items and totals, used to gather evidence before a decision.
- Get Default Document Reads a pre-filled document template carrying the agenda's own numbering sequence, payment option, currency, and dates. The intended starting point for anything a flow creates.
- Create Document Creates a document in one of the registers together with its line items.
- Update Document Updates a document in one of the registers. The identifier travels in the body rather than the path.
- Delete Document Deletes a document from a register. A numbered document may be refused, because a Czech numbering sequence must not have gaps.
- Copy Document Produces a copy of an existing document as an unsaved template with a fresh number, ready to be posted back through Create Document.
- Recount Document Recalculates a draft and returns it with the VAT, discounts, and totals worked out, without saving anything. The rehearsal step before a create.
- Download Document PDF Downloads a document as a PDF into FlowRunner file storage, optionally with its payments shown, which is the version to attach to a reminder.
- Send Document By Email Emails a document to its contact. This reaches the customer and cannot be recalled.
- Send Payment Reminder Emails an overdue payment reminder for issued invoices. This reaches the customer and cannot be recalled, and it is the operation this page's human gate exists for.
Payments and Reconciliation
9- List Payments Lists the payments recorded against sales documents.
- Get Default Payment Reads a pre-filled payment template for a document, already carrying the amount still outstanding.
- Create Payment Records a payment against a sales document.
- Set Document Fully Paid Marks a document fully paid by writing a payment for the whole outstanding amount, or removes that payment again.
- Delete Payment Deletes a payment from a document, which reopens it.
- List Bank Statements Lists the bank movements of an agenda. Where a reconciliation flow finds the money that the document register has not caught up with yet.
- Create Bank Statement Records a bank movement in an agenda.
- Get Default Bank Statement Reads a pre-filled bank movement template, either blank or already matched to a document.
- Pair Bank Statement Matches a bank movement to a document, which is the step that turns an imported bank line into a payment.
Price List
4- List Price List Items Lists the price list items of an agenda, which are the products and services document lines are built from.
- Create Price List Item Creates a price list item in an agenda.
- Update Price List Item Updates a price list item. The identifier travels in the body rather than the path.
- Delete Price List Item Deletes a price list item. An item already used on a document is refused unless you explicitly allow it, and allowing it removes the item from those documents.
Reference and Statistics
3- Get Reference List Reads one of the reference lists: currencies, countries, banks, payment options, VAT rates, VAT codes, constant symbols, exchange rates, numeric sequences, or tags. The VAT rates list is where the percentages behind iDoklad's rate bands come from.
- Get Next Document Numbers Reads the next numbers a numbering sequence will assign, used to predict a document's identity before creating it.
- Get Statistics Reads one of the statistics computed on the server: invoicing for a period or a year, the agenda summary, overdue amounts, the quarterly summary, top debtors, top partners, or VAT totals. A dashboard flow does not need to read every invoice.
Attachments
3- Download Attachment Downloads an attachment from a document into FlowRunner file storage.
- Upload Attachment Attaches a file to a document. The vendor's current limit is one attachment per document.
- Delete Attachment Deletes an attachment from a document.
Webhooks
3- List Webhooks Lists the webhook subscriptions of an agenda. The callback address itself lives in the iDoklad developer portal rather than in the API.
- Create Webhook Subscribes a developer portal webhook to an entity and an action. The callback address is configured in the portal, so this operation says what an existing endpoint fires for rather than creating one.
- Delete Webhook Removes a webhook subscription from an agenda.
Frequently Asked Questions
What can FlowRunner do with iDoklad?
FlowRunner agents can run Get Current Agenda, Get Current User, and List Agendas in iDoklad, plus 39 more actions.
Does connecting iDoklad to FlowRunner require OAuth?
Yes. iDoklad connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.
Can iDoklad trigger a FlowRunner workflow automatically?
iDoklad doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with iDoklad
Free plan, no card required. Connect in minutes.