Origami

Origami is the Israeli no-code business platform that runs CRM, HR, and ERP on one schemaless data model. Agents discover entities, query records with Origami's filter language, update fields and repeatable groups, attach files, read history, send email and SMS, and work the invoice system.

Verified 22 actions Custom auth available

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

A work order reaches a billable state in Origami

Get Entity Structure returns the group and field data names, because nothing in an Origami schema is fixed and every account names its own

Select Records pulls the customer record and the line items held in a repeatable group on the work order

The agent checks the totals and the billing details against the source record and the work order's own history

The agent posts the assembled document with its proposed type, its recipient and its amounts

A finance approver confirms the document type and the figures, because Create Invoice issues a real financial document and this connector has no operation that removes one

What This Integration Enables

Origami runs CRM, HR and ERP on one schemaless data model, which is a genuinely different starting point from a table-shaped database. Nothing is fixed: an entity is discovered at run time, its groups and fields carry generated data names, and a repeatable group is how a record holds line items. FlowRunner agents therefore start with List Entities and Get Entity Structure and build the rest of the workflow from what the account actually defines, which is why one flow can cover a sales record, a personnel record and a work order without three separate mappings.

The surface goes well past data. Agents archive records reversibly instead of deleting them, read a record's change history, reach Origami's own system tables through the protected entity route, move files in and out, read a calendar window, and reach a person through email, SMS, push notification or by injecting a conversation held on another channel into Origami's inbox. They also work the invoice system, and that is where this page turns serious.

One connector-level detail is worth stating plainly because it is a safety property rather than a feature. Origami accepts a malformed filter and silently returns every record, which is tolerable on a read and catastrophic on a delete. This connector refuses the wrong shape before the call is sent, on every operation that takes a filter. That is what building a connector against the vendor's documented behavior rather than its happy path buys you, and it is the floor that human-in-the-loop is built on rather than a substitute for it.

Without FlowRunner

One data model, three teams re-keying CRM, HR and ERP share a schema, and the work still moves between them by hand

A filter that means everything A malformed filter is accepted and quietly matches every record, which is survivable on a read and not on a delete

Billing waits on assembly Someone gathers the line items, the customer details and the totals before anything can be issued

With FlowRunner

One agent across the model Entity discovery at run time means the same workflow reads a lead, an employee record and a work order

Malformed filters refused, not obeyed The connector checks the filter shape before the call leaves, so a wrong filter fails instead of matching everything

Billing assembled, then decided The document arrives complete and priced, and a person decides whether it should exist

Use Case Scenarios

One agent reading across CRM, HR and ERP

A weekly operations review needs the state of open deals, staffed projects and outstanding work orders, all of which live as different entities on the same model. The agent calls List Entities to find them, Get Entity Structure for each so it knows the group and field data names, and Select Records with a correctly shaped filter per entity. Get Record History fills in what changed during the week. Get Calendar View adds the scheduled work. The digest posts to Slack and the underlying figures append to Google Sheets, assembled by one workflow rather than three.
Reaching the customer on the channel they actually use

A service appointment needs confirming. The agent updates the record, then chooses a channel: Send Email for the written confirmation, Send SMS when the appointment is same day, or Send Push Notification with a link button for customers on the Origami app. Where the conversation is already happening on WhatsApp, Inject Omnichannel Message pushes it into Origami's inbox so it appears against the record rather than living only in the messaging tool. Each of these sends a real message to a real person, so the workflow treats an unattended send as a decision the operator configured deliberately rather than a default.
Line items assembled before anyone opens the record

A completed work order needs billing. The agent reads the work order and its repeatable line item group, uses Add Group Repetition and Remove Group Repetition to correct the lines against what was actually delivered, attaches the delivery evidence with Upload File, and calls Select Invoices to check whether a document has already been issued for this order. Then it stops, with everything assembled, and asks. The reconciliation afterward runs against Xero or QuickBooks Online once the document exists.

Human-in-Loop Highlight

Look at what this connector's invoice surface contains: Create Invoice and Select Invoices. There is a create and there is a read, and there is nothing that removes or amends. That is not an oversight. Creating a tax invoice, receipt, proforma, credit invoice, work order or delivery note in Origami is not creating a draft, and in Israel these are legally meaningful documents, which is why the correction path is issuing another document rather than deleting the first one. An agent operating without a gate here would be issuing financial records with no inverse operation available to it.

So the billing agent assembles everything and then stops. It posts: "Work order 8842 for Levi Industries is complete. 6 line items, total assembled from the repeatable group and checked against the order. Select Invoices shows no document already issued against this order. Proposed document type: tax invoice. Issue it, change the document type, or hold?" A finance approver answers. Whether a document should be issued at all, and which type is correct, is a judgment made by the people accountable for the books. The agent's job was to make that judgment easy and quick, and to make sure the person making it had the line items in front of them. That is the whole thesis: the agent does the work, and the call that cannot be taken back belongs to a human.

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

22 actions

Structure

List Entities Returns the entities this account defines with their data names. The starting point, because nothing in Origami is fixed and an entity's data name is what every other operation needs.
Get Entity Structure Returns an entity's groups and fields with their data names and types. Where a workflow discovers the generated names every write uses.

Records

Select Records Reads an entity's records. The filter has to be an array of arrays, and this connector refuses the wrong shape rather than letting Origami silently return every record.
Get Record Reads one record by its identifier. A record read with the id filter already built.
Create Record Creates a record. The form data follows Origami's nested shape of groups, each carrying a data array of field maps.
Create Records In Bulk Creates a batch of records in one call, one inner array of groups per record.
Update Record Fields Writes fields on the records a filter selects, each field carrying its repetition index for repeatable groups. The filter decides what changes, so a loose filter changes more than intended.
Delete Records Deletes records by identifier or by filter. Deleting by filter is the vendor's own careful case, because a filter that matches more than intended deletes more than intended.
Archive Record Archives or unarchives a record. The reversible alternative to deletion, and archived rows can be brought back into a read.
Get Record History Returns a record's change history. The read behind any reconciliation or audit question.
Select Protected Records Reads a protected entity, which is how Origami's own system tables are reached, including looking up an Origami user's details.

Groups

Add Group Repetition Adds a row to a repeatable group on a record, which is how a line item is appended.
Remove Group Repetition Removes a row from a repeatable group on a record.

Files

Upload File Uploads a file to Origami and returns its id, which is then attached to a record through a file field.
Download File Downloads a stored file into FlowRunner file storage so a later step can use it.

Calendar

Get Calendar View Returns an entity's calendar events between two dates. Used to bring scheduled work into a workflow alongside the records it belongs to.

Messaging

Send Email Sends an email through Origami. This sends real mail, and the option to give each recipient their own copy keeps a distribution list private.
Send SMS Sends an SMS through Origami. This sends a real message and is usually billable.
Send Push Notification Sends a push notification to an Origami user's app. A button on the notification can carry a link, which turns it into a call to action.
Inject Omnichannel Message Pushes a message from an outside channel into Origami's omnichannel inbox, so a conversation held elsewhere appears against the record.

Invoices

Create Invoice Creates a financial document: a tax invoice, receipt, proforma, credit invoice, work order or delivery note. These are legally meaningful documents and creating one is not creating a draft.
Select Invoices Reads financial documents of one type. Used to check what has already been issued before anything new is.

Frequently Asked Questions

What can FlowRunner do with Origami?

FlowRunner agents can run List Entities, Get Entity Structure, and Select Records in Origami, plus 19 more actions.

Does connecting Origami to FlowRunner require OAuth?

Origami uses a custom authentication method to connect to FlowRunner.

Can Origami trigger a FlowRunner workflow automatically?

Origami doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Origami

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us