easybill

easybill is German online invoicing and bookkeeping. Agents manage customers and the article catalog with stock, and create the single document object that serves as invoice, offer, credit note, or order, then send it and track payments.

1 trigger 55 actions API key available

easybill website Platform Documentation Capability data verified 2026-08-24

A customer accepts the offer they were sent

List Documents is read for that customer to see whether the offer has already produced an invoice

Get Document returns the offer with its items and the customer snapshot it was created against

The agent confirms the amounts are in cents and that the VAT treatment matches the customer's country

Convert Document produces the invoice, and Complete Document assigns its number

Send Document delivers the invoice and the number posts back to the deal record

A person confirms the conversion whenever the offer already has a sibling document

What This Integration Enables

easybill models sixteen kinds of document as one object. An invoice, an offer, a credit note, a delivery note and a dunning letter are all the same record differing by a type field, and that field can only be set when the record is created. That design is why this connector's document operations look so short: one create, one update, one complete, one cancel. It is also the single most important thing to understand before pointing an agent at it, because changing a document's kind is not an update. It is Convert Document, which produces a new record and leaves the original standing.

Around the document sit the parts that make easybill a working system rather than an invoice generator: customers with contacts and groups, a position catalog with stock entries, projects with tasks and time tracking, attachments, and received electronic invoices that can be read but not created. FlowRunner agents drive all of it. Two operational limits shape how. Every amount is an integer of cents, so 150 is one euro fifty and sending 1.50 produces a document for one and a half cents with no error. And the rate limit is low enough that a loop reading customers one at a time will hit it within seconds, so agents raise the page size rather than iterating.

Without FlowRunner

Two invoices for one job An offer gets converted twice, both invoices are valid, and the duplicate surfaces when the customer queries it

Prices off by a factor of a hundred Amounts are stored in cents, and a decimal figure produces a document nobody notices until settlement

Time recorded somewhere it cannot be billed Hours live in a tracker that never reaches the document they belong on

With FlowRunner

One document per piece of work The agent checks for an existing sibling before converting, and a person confirms when there is one

Amounts converted deliberately The conversion into cents happens in one place in the flow and is checked before the document is completed

Time reaches the invoice Hours are booked against the project and appear on the document that bills them

Use Case Scenarios

Offer to invoice, once

An offer is accepted in the CRM. Before doing anything, the agent reads List Documents for that customer and looks for a document already converted from this offer, because nothing in the conversion response tells you a sibling exists. If the offer is clean, Convert Document produces the invoice, Complete Document assigns its number and renders it, and Send Document delivers it. The customer's own reference travels on the document so Pipedrive can be updated without anyone storing an easybill id. If a sibling does exist, the flow stops rather than producing a second valid invoice for the same work.
Time and stock reaching the document that bills them

Hours are recorded against a project with Create Time Tracking, in minutes, and materials are drawn down with Create Stock Entry. At the end of the period the agent reads List Time Trackings and List Positions for the project, builds the line set, and calls Update Document with the complete set, because supplying items on an update replaces the whole line list rather than appending to it. The draft goes to the project manager for review before anything is completed, and the position catalog's own stock levels stay honest because the drawdowns were recorded as they happened rather than reconciled later.
Received electronic invoices routed into bookkeeping

German suppliers increasingly deliver electronic invoices, and easybill exposes those through List Incoming Documents and Download Incoming Document File as a read only feed. The agent pulls each one, classifies it against the right revenue or expense treatment, files the file into a document store like Dropbox, and posts a digest to Slack. Because incoming documents cannot be created through the API, this is a genuinely one way flow, and the agent's job is classification and routing rather than write back. Anything it cannot classify with confidence becomes an automation exception with the supplier and the two candidate treatments shown side by side.

Human-in-Loop Highlight

Convert Document is the operation on this connector that quietly creates a problem rather than reporting one. Because a document's type is fixed at creation, converting an offer into an invoice does not change the offer. It produces a new document and leaves the original exactly where it was, and the response says nothing about whether a conversion already happened. Run it twice, from a retry or from two flows watching the same acceptance signal, and you have two invoices for one job. Both are valid. Once completed, both carry real numbers, and the cleanup is Cancel Document, which produces a matching Storno the customer also receives. So the agent checks first and asks when the check is not clean: "Offer AN-2026-0271 for Weber Anlagenbau was accepted. An invoice dated 2 March already references this offer, completed, number RE-2026-0290, unpaid. Convert again, or treat the existing invoice as the one?" That is not a question about whether converting is dangerous in the abstract. It is a question the API cannot answer for itself.

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

55 actions

Customers

List Customers Lists customers with paging. Raise the page size rather than reading one at a time, because the rate limit is low.
Get Customer Retrieves a single customer with its terms and country.
Create Customer Creates a customer. Both a last name and a company name are required, so a private individual carries their own name twice.
Update Customer Updates a customer. Documents already issued keep the snapshot they were created with.
Delete Customer Deletes a customer without breaking documents already issued against it.
List Customer Contacts Lists the people attached to a customer.
Create Customer Contact Adds a person to a customer, which is how a document reaches a named recipient.
Delete Customer Contact Removes a person from a customer.
List Customer Groups Lists the groups customers are organized into.
Create Customer Group Creates a customer group.
Delete Customer Group Removes a customer group.

Documents

List Documents Lists documents of every kind, filtered by type, customer and date. The read that proves whether a conversion has already happened.
Get Document Retrieves a single document with its items and customer snapshot.
Create Document Creates a document. The type is fixed here and cannot be changed afterwards.
Update Document Updates a draft document. Supplying items replaces the whole line set rather than appending to it.
Complete Document Finalizes a draft, assigns its number and renders it. The draft flag itself is read only.
Cancel Document Voids a completed document by producing the matching Storno, which keeps the numbering sequence unbroken.
Convert Document Produces a new document of a different kind and leaves the original standing. The operation this page's human gate exists for.
Send Document Delivers the document. It can also prepare the message and hand it back when your own mail system does the sending, and it can post a paid physical mailing.
Download Document PDF Fetches the PDF specifically, whatever else the account is configured to produce.
Download Document File Fetches whichever format the account is configured for, which for a German public sector invoice may be an electronic invoicing format rather than a PDF.
Delete Document Deletes a document. For a completed invoice, Cancel Document is the lawful route instead.
List Document Versions Lists a document's versions, which is the record of what changed and when.

Payments

List Document Payments Lists the settlements recorded against a document.
Create Document Payment Records a settlement in cents against a document.
Delete Document Payment Removes a recorded settlement.

Positions (catalog)

List Positions Lists the catalog with prices and stock limits.
Get Position Retrieves a single catalog position.
Create Position Adds a position to the catalog. Its price type decides whether the stored price is read as net or gross.
Update Position Updates a catalog position.
Delete Position Removes a catalog position.
List Position Groups Lists the groups positions are organized into.
List Stock Entries Lists the stock movements recorded against positions.
Create Stock Entry Records a stock movement, which is how a drawdown reaches the catalog as it happens.

Projects, tasks and time

List Projects Lists projects with their budgets, held in minutes and in cents.
Create Project Creates a project with a budget and an hourly rate.
Update Project Updates a project.
Delete Project Removes a project.
List Tasks Lists tasks across projects.
Create Task Creates a task, which is how an agent hands work to a named person.
Update Task Updates a task.
Delete Task Removes a task.
List Time Trackings Lists recorded time, in minutes.
Create Time Tracking Records time against a project, which is what makes it billable later.
Delete Time Tracking Removes a time entry.

Attachments and incoming documents

List Attachments Lists the files attached to documents.
Create Attachment Attaches a file, sent base64 encoded in the request body rather than as a multipart upload.
Download Attachment Fetches an attached file's bytes.
Delete Attachment Removes an attachment.
List Incoming Documents Lists received electronic invoices. This feed is read only; easybill publishes no route to create one.
Get Incoming Document Retrieves a single received document.
Download Incoming Document File Fetches a received document's file for filing or classification.

Webhooks

List Webhooks Shows what is currently registered.
Create Webhook Registers a webhook by hand. easybill creates one inactive by default, so the active toggle matters.
Delete Webhook Removes a registered webhook.

Triggers

1 triggers

Event Triggers

On easybill Event Fires on any of the documented events across documents, payments, customers and positions, or on all of them at once. FlowRunner registers the webhook when the trigger is switched on, sets it active explicitly because easybill creates webhooks inactive, and removes it when the trigger is switched off. Set a webhook secret and every delivery is checked before the flow runs; with no secret configured deliveries are accepted unverified, which leaves the callback URL as the only control on who can start your workflow.

Frequently Asked Questions

What can FlowRunner do with easybill?

FlowRunner agents can run List Customers, Get Customer, and Create Customer in easybill, plus 52 more actions.

Does connecting easybill to FlowRunner require OAuth?

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

Can easybill trigger a FlowRunner workflow automatically?

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

Start building with easybill

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us