OfficeGuy

OfficeGuy, also known as SUMIT, is the Israeli business management and billing platform. Agents create accounting documents, manage customers, income items, and expenses, run payments and recurring billing, and work the CRM entity store and stock underneath.

1 trigger 46 actions API key available

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

A signed subscription order reaches the flow

The buyer's identity, the plan rows, and the billing interval are read from the order

List Entities in the customers folder resolves the buyer to exactly one existing record and its identifier

Get Customer Payment Methods confirms a stored token exists rather than raw card details

Create Document raises the first document as a draft while the terms are still editable

The resolved customer, the interval, and the number of payments post to the revenue owner

The owner confirms the customer match and the payment tail before Charge Recurring runs

What This Integration Enables

OfficeGuy, which the platform itself calls SUMIT, is an Israeli business management and billing system, and the way to think about it is that the accounting sits on top of a CRM rather than beside one. Everything is an entity in a folder. Customers are a folder, documents are a folder, and List Folders is the map of the account: it is what a trigger subscribes to, and Get Folder reports the field names an entity's properties have to be keyed by. That is why this connector carries a generic entity reader and writer alongside the typed accounting operations. The parts SUMIT models specifically get specific operations; the rest of the account is still reachable.

The typed half covers the ground an Israeli business actually bills on. Agents issue accounting documents, move drafts into the books, cancel booked documents with a reason, and record supplier expenses. They read a single customer's debt or the whole receivable aging view at once. On the money side they charge cards, open hosted payment pages so no card data passes through the flow, store and remove payment methods, and run recurring billing. One field governs more of this than any other. Customer blocks are find-or-create, and Search Mode decides whether a write matches an existing record or creates a new one, which is how a customer list fills with duplicates or how the wrong customer gets billed. Naming a customer identifier skips the search entirely, and that is what a careful connectors workflow does.

Without FlowRunner

Find-or-create left on its default A write matches whatever the platform recognizes, and nobody sees which record it chose

Subscriptions set up by hand Somebody keys in the interval and the number of payments, in a screen, once, at speed

The CRM and the books apart Customer records live in one tool and the documents billed to them live in another

With FlowRunner

The match proved before the write The customer is resolved to one identifier first, and an ambiguous match stops the flow

Subscriptions set up with the tail stated The interval, the recurrence, and the total commitment are read back before anything is charged

One store, reached end to end Documents, customers, and the folders both live in are reachable from the same flow

Use Case Scenarios

A deal closes and the books catch up

A deal moves to won in Pipedrive. The agent resolves the buyer against the SUMIT customers folder with List Entities, switching load properties on so the listing returns fields rather than bare identifiers, which is the most common way a search here looks empty when it is not. With one identifier in hand it calls Create Document with the draft flag set, so the document exists and can still be corrected. It attaches the deal reference through Create Customer Remark so the account team can see where the document came from, and returns a link with Get Customer Details URL for anyone who needs to open the account. Move Document To Books is left for the review step, because that is the point of no return.
Collections that read the account, not a spreadsheet

On a schedule the agent calls Get Debt Report, which returns the outstanding debt of every customer at once rather than requiring a pass over documents. Where a specific account is in question, Get Customer Debt answers for one. It cross references open support conversations in Zendesk, because a customer with an unresolved ticket about the thing they were billed for is a different collections case from a customer who simply has not paid. The prioritized list posts to the finance owner in Slack, with disputed balances separated from quiet ones and the debt figures taken straight from SUMIT rather than re-added anywhere.
New documents reaching a flow the moment they exist

The On Entity Event trigger subscribes to a folder and fires on creation, update, archive, or deletion. Because documents and customers are both folders, this is how a new invoice or a new customer reaches a workflow. A view narrows the subscription to part of a folder, so a trigger can watch unpaid invoices rather than every document that gets written. Deliveries are unsigned and do not restate what fired, so the agent treats a delivery as a signal and reads the record back with Get Entity before acting on it. That is the honest way to use an unsigned webhook, and it costs one extra call.

Human-in-Loop Highlight

Charge Recurring is the operation on this connector that has to stop for a person, and not because it takes money. Charge Customer takes money too, and a routine charge against a named customer identifier with a stored token can run unattended all day. Charge Recurring is different because it does two things in one call: it charges immediately, and it creates a standing order that keeps charging on an interval for a stated number of payments, or indefinitely when that number is left empty. And the customer block on that call is find-or-create, governed by Search Mode, which means an automatic match can bind an open ended payment schedule to the wrong customer's stored card. Cancel Recurring Item stops future payments; it does not unwind the ones already taken, and refunding those happens outside this connector.

So the agent proves the customer first and states the tail out loud: "Setting up recurring billing for what I resolved to customer 8841, matched on email address rather than on a customer identifier, because two records share this company name. Monthly, 12 payments, 890 shekels each, first charge now. Confirm this is the right record, or should I hold?" The revenue owner answers. The distinction worth keeping is between a charge and a commitment. A charge that turns out wrong is a refund. A standing order that turns out wrong is a refund every month until somebody notices.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

46 actions

Documents

Create Document Issues an accounting document such as an invoice, receipt, or price quotation. A document that reaches the books cannot be edited, only canceled, so use the draft flag while it is still being built.
List Documents Lists documents by type, number range, or date range. Filtering by number also requires the document type, because numbering restarts for each type.
Get Document Reads one document, addressed either by its identifier or by its number together with its type.
Download Document PDF Downloads a document as a PDF into FlowRunner file storage. The original can normally be produced only once, after which SUMIT issues certified copies.
Send Document Emails a document to a recipient, optionally with a personal message and in a chosen language.
Cancel Document Cancels a document that is already in the books. A reason is required, and the original stays on file with the cancellation recorded against it.
Move Document To Books Finalizes a draft document into the books. After this it can no longer be edited, only canceled.
Add Expense Records a supplier expense, optionally attaching the scanned invoice in the same call.
Get Customer Debt Reads how much one customer still owes, computed from the documents on their account.
Get Debt Report Reads the outstanding debt of every customer at once, which is the accounts receivable aging view.
Create Scheduled Documents Creates scheduled documents from an existing document, which is how a one-off invoice becomes a repeating one.

Customers

Create Customer Creates a customer, or returns an existing one when Search Mode matches. Search Mode None always writes a new record.
Update Customer Updates a customer. Naming a customer identifier addresses that record; without one, Search Mode decides which customer is matched or whether a new one is written.
Get Customer Details URL Returns a link to a customer's page, which is what a flow hands a person when someone needs to look at the account.
Create Customer Remark Adds a remark to a customer's record, which is how a flow leaves a note for the people working the account.

Items and Stock

Create Income Item Creates an income item, which a document row or a charge can then reference instead of restating the name and price.
List Income Items Lists the income items of the company, which is where an item identifier or SKU for a document row comes from.
List Stock Lists the stock levels held in the company.

Reference and Accounting Settings

Get VAT Rate Reads the Israeli VAT rate in force on a given date, which is what keeps a back dated document correct.
Get Exchange Rate Reads the exchange rate SUMIT uses between two currencies on a given date.
Verify Bank Account Checks that an Israeli bank, branch, and account number combination exists, which is worth doing before a direct debit is set up.
Get Next Document Number Reads the number SUMIT will give the next document of a chosen type. Numbering runs separately for each type.
Set Next Document Number Sets the number SUMIT will give the next document of a chosen type. It has to be higher than the last one issued, because numbering cannot go backwards, so a number set too high burns the range beneath it.
Update Accounting Settings Updates the settings of the accounting application. The fields are passed through as given, because the settings surface differs by company.
Create Transaction Batch Posts a batch of bookkeeping transactions into SUMIT Books, which is the double entry ledger underneath the documents.

Payments

Charge Customer Charges a customer, using the payment method already on file unless a token is given, and issues the resulting document. This takes money immediately.
Begin Payment Redirect Opens a hosted payment page and returns the URL to send the payer to. The card is collected by SUMIT, so no card details pass through the flow.
Get Payment Reads one payment by the identifier that a charge or a payment redirect returned.
List Payments Lists payments in a date range. Both ends of the range are required, and the valid flag separates settled payments from failed attempts.
Get Customer Payment Methods Reads the payment methods stored against a customer, such as a tokenized card or a direct debit mandate.
Set Customer Payment Method Stores a payment method against a customer. Use a single use token where possible, because the alternative is putting raw card details through the flow.
Remove Customer Payment Method Removes the stored payment method from a customer, which stops any recurring billing that relies on it.

Recurring Billing

Charge Recurring Charges a customer now and creates a standing order for the payments that follow. The interval and the number of payments are set per row, and an empty recurrence means indefinitely. The operation this page's human gate exists for.
List Customer Recurring Items Lists the standing orders held against a customer, which is where the recurring item identifier the update and cancel operations need comes from.
Update Recurring Item Changes a standing order's price, quantity, next payment date, or remaining payments. Recurrence and last payment date cannot both be given.
Cancel Recurring Item Cancels a standing order so that no further payments are taken. Payments already taken are not affected.
Update Recurring Settings Updates the settings of the recurring billing application. The fields are passed through as given, because the settings surface differs by company.

CRM Entity Store

Create Entity Creates a record in a CRM folder. Everything in SUMIT lives in a folder, so this is the generic writer for the ones the accounting operations do not cover.
Update Entity Updates a record in a CRM folder. Only the fields supplied are changed.
Get Entity Reads one record by its identifier, which is also how a record reported by the trigger is read back in full.
List Entities Lists the records in a CRM folder. Load properties has to be switched on to get the fields, otherwise the answer is little more than a list of identifiers.
Archive Entity Archives a record, which is the reversible alternative to deleting it and is one of the events a trigger can watch.
Delete Entity Deletes a record permanently. Archive Entity is the reversible alternative.
List Folders Lists the CRM folders, which is the map of where customers, documents, and everything else live, and what a trigger subscribes to.
Get Folder Reads one CRM folder. Including properties reports the fields it has, which is what an entity's properties object must be keyed by.
List Views Lists the saved views. A view narrows a folder, so a trigger can subscribe to one instead of watching everything in the folder.

Triggers

1 triggers

Event Triggers

On Entity Event Fires when a record is created, updated, archived, or deleted in a chosen folder. Documents and customers are both folders, so this is how a new invoice or a new customer reaches a flow, and a view narrows the subscription to part of a folder. Deliveries are unsigned and do not restate which trigger type fired, so a payload is a signal to act on rather than trusted data, and a flow that cares about the contents should read the record back with Get Entity.

Frequently Asked Questions

What can FlowRunner do with OfficeGuy?

FlowRunner agents can run Create Document, List Documents, and Get Document in OfficeGuy, plus 43 more actions.

Does connecting OfficeGuy to FlowRunner require OAuth?

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

Can OfficeGuy trigger a FlowRunner workflow automatically?

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

Start building with OfficeGuy

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us