Origami 6.3.2: Vision Launches, Open Omnichannel API, and a Redesigned Mobile Experience

Version 6.3.2 brings Vision in its first release – an AI engine that builds your entire system through conversation. We’ve also opened Omnichannel to any external source via API, improved phone number matching across all formats, and upgraded the calendar, KPI view, and auto-fill. Here’s everything that’s new, with full details on how to use each capability.

Vision: Build a Complete System with AI

From the new Vision tab in System Preferences, you start a conversation with the AI: describe what you want to build, and it asks questions, makes suggestions, and shapes the structure with you – entities, field groups, fields, and relations. Once the structure is ready and you confirm it, Vision implements everything inside your live system. Instead of long manual setup, you reach the result through conversation.

Step by step

1. An admin opens System Preferences and selects the new Vision tab.
2. A chat interface opens to begin the conversation about the system structure you want to implement.
3. The AI Builder screen is split into two areas: a chat panel with the AI Implementer, and a live structure tree that updates in real time.
4. Describe what you want to build – a CRM, project management system, client portal, or anything else.
5. The AI asks guiding questions to define the structure: which entities to create, which field groups are needed, and how entities relate to each other.
6. As the conversation progresses, the structure tree updates live with Entities, Groups, Fields, and Relations.
7. You can manually edit the structure via the tree: rename, delete, or adjust field settings.
8. You can also import an Excel or CSV file and let the AI build the system structure from your existing data.
9. When the structure is ready, the AI displays a confirmation prompt.
10. Only after clicking “Build It / Implement my system” does Origami actually build the system.
11. You’re automatically taken to the new system and can edit it just like any manually built system.

Key use cases

• Build complete systems using AI – no manual setup required.
• Define the outcome you want, not the technical implementation steps.
• Create entities, field groups, fields, and relations automatically.
• Convert an Excel or CSV file into a live Origami system in minutes.
• Design your system structure visually, in real time.
• Refine and expand existing systems through natural conversation.

Who it’s for

• System admins and implementers.
• Product and Operations teams setting up new workflows.
• Organizations that want to onboard new processes quickly, without deep technical expertise.

What it solves

• Eliminates the time-consuming manual setup of entities, fields, and relations.
• Lets you build a complete system through natural conversation with AI.
• Significantly simplifies onboarding and system design.
• Enables fast migration from Excel to a live, structured system.

Omnichannel via API – Receive Messages from Any External Source

Any external application can now push messages directly into Origami’s Omnichannel – no WhatsApp connection, no email integration, no PBX required. Enable the External Apps toggle in the Omni Widget settings, and any system with API access can send messages that appear natively inside the Omnichannel thread.

Step by step

1. Add an Omni Widget to the desired entity.
2. In the widget settings, enable the External Apps toggle.
3. An external application sends an API request to Origami.
4. Origami receives the request and identifies it as an Omnichannel message.
5. The message is routed to the correct Omnichannel thread based on the identifier or mapping.
6. It appears inside the Omnichannel exactly like a WhatsApp, email, or PBX message.
7. The conversation can continue normally from within the system.

Key use cases

• Bring messages from any external system into a single Omnichannel view.
• Connect tools that aren’t natively supported – no direct WhatsApp or email integration needed.
• Unify all communication under one UI, regardless of the source.

Who it’s for

• Integration teams and technical implementers.
• Companies with custom internal communication systems.
• Service providers building tailored client integrations.

What it solves

• Removes the requirement for a direct WhatsApp, Gmail, or PBX connection.
• Consolidates all messages under a single interface.
• Simplifies complex integrations into one clean API structure.

Phone Number Normalization – Match Any Format to Any Format

The system now normalizes phone numbers behind the scenes, so every format of the same number – with or without a country code, with spaces, dashes, or a leading zero – is treated as a single contact. Numbers are stored as entered, but searches, filters, and incoming call detection all match across formats.

Step by step

1. An admin can set a default country code for phone fields (for example, Israel or the US).
2. For specific records, users can manually change the country code.
3. Phone numbers can be displayed with or without the country code, based on display settings.
4. Numbers can be entered in any format: with a leading 0, with +972, with another country prefix, with spaces or dashes, or without any prefix.
5. Entry is supported across all system channels: manual input, Webforms, Import, Workflows, and API calls.
6. The system stores the number exactly as entered.
7. In parallel, it generates a normalized search version that links all formats of the same number.
8. When searching, filtering, or receiving an incoming call, the system matches correctly across all formats.
9. Even if a number was saved in one format and searched in another, the match works.

What it solves

• Prevents the same person from appearing as two separate contacts due to format differences.
• Enables full matching between any phone number format.
• Significantly improves contact identification in incoming calls and searches.
• No need to enforce a standard format – numbers can be stored however they arrive, and the system still recognizes them.

Calendar Webform – Invite External Attendees Automatically

A new Email field option in Calendar field settings lets you link a meeting invite to a form respondent’s email address. When someone books an appointment through a Webform, both sides receive a full calendar invite with a Google Meet link.

Step by step

1. Open the Calendar field settings inside a Webform.
2. Below the existing URL for meeting field, select the new Invite to Event option and choose an Email field from the form.
3. A visitor fills out the Webform and books a time through the Calendar field.
4. After submission, a meeting is created in the Origami user’s calendar and a shared Calendar Invite is generated.
5. The invite includes the email address entered in the form.
6. Both parties receive the invite, including a Google Meet link.
7. The event appears in both calendars.

What it solves

• Until now, only the logged-in Origami user received the calendar event.
• The form respondent had no link and no calendar entry.
• This feature makes Webform scheduling work like a full Calendly-style flow – both sides are in the loop.

Calendar View – More Events Displayed per Day

When a single field is configured as the event description, the monthly calendar view now shows up to 4 events per day cell instead of 2. When multiple description fields are configured, the number of visible events adjusts to the available cell height. A button appears when additional events exist beyond what’s shown.

KPI Widget – Control Blocks Per Row

A new Blocks Per Row setting in the KPI Widget lets you define how many KPI blocks appear on each row. Full control over layout density – display more metrics in less space, or give each KPI room to breathe.

Auto-Fill from Fields – Dynamic Values in Table Widgets

Auto-fill in table widgets now supports two modes: a fixed custom value (as before), or a dynamic value pulled from another field. When a field is selected as the source, the auto-fill value is taken from that field at the time the record is created or updated – not from a hardcoded preset.

Key use cases

• Pass values dynamically between fields without manual entry.
• Create smarter auto-fill flows based on existing record data.
• Reduce repetitive manual input in multi-entity workflows.

What it solves

• Previously, only a fixed static value was supported in auto-fill.
• There was no way to pull a dynamic value from another field.
• This feature enables intelligent automation between entities and fields.

New Mobile Design

Version 6.3.2 includes a set of mobile UI improvements across several key screens, each focused on better readability and faster navigation in everyday use.

Navigation Bar and Search

The top navigation bar has been redesigned. All entities and the search field are now displayed at the top of the screen – accessible immediately, without scrolling.

Entity Menu

The entity menu has been redesigned – it opens from the top bar, and the currently active entity is highlighted for quick orientation.

Table View

The table view has been updated to show more data per row. Action buttons at the record level have moved to a separate icon at the start of each row – keeping the full row width available for actual data, not controls.

Gallery View

The gallery view has been updated – switching between enlarged and thumbnail images is now smoother and more intuitive.