Origami 6.2.6 – Build Faster, Schedule Smarter, Secure Better

Origami 6.2.6 brings real-time polish and smarter flows – live RG styling, sharper webforms, and calendar-aware scheduling – plus admin superpowers like multi API keys and smarter Convert & Copy. Build cleaner and keep every click accountable.

Live CSS Formatting for RG (Repeating Groups) – Contracts & Documents

Polish your contract and document templates in real time. Repeating groups (items, clauses, pricing rows) now update their styling instantly with CSS – no reloads, no exports. What you tweak is exactly what legal sees and clients receive.

Multi API Keys per User
Give power users and integrations more flexibility – and tighter security. Each user can now create multiple API keys, so they can separate keys by app, entity, or use case, and rotate/revoke them independently without breaking everything.

How to enable / generate a key

  1. Go to Users → open the target User settings
  2. Scroll to Allow API Access
  3. Click Generate token
  4. Label it by app/use case and save

Turn calculated links into instant actions. Formula fields can now output a URL that’s clickable right from the record – no copy–paste, no hunting.

Clickable Links from Formula Fields    
Turn calculated links into instant actions. Formula fields can now output a URL that’s clickable right from the record – no copy–paste, no hunting.

A→Z Sorting for Relation & User Fields
Make long picklists effortless to scan. You can now sort values alphabetically in:

  • User field
  • Multi-User field
  • Relation field
  • Multi-Relation field

How it works
In the field settings of any of the fields above, toggle Order Alphabetically. Applies to both single and multi selectors, including user pickers.

Webforms: Smarter Prefill & Conditional Logic

Three upgrades that make your webforms faster to fill, easier to control, and more reliable.

1) Dynamic URL Prefill for Relation Fields

You asked, we delivered: you can now pass values via URL parameters and map them into relation fields.
Use it to preselect an Account, Ticket, Project, or any related record before the form opens.

Example:
https://stage-public.origamicloud.ms/s/webform/stage/69074b327d60c/?fields=fld_7391_dup_e_731:Ellah,fld_7392_dup_e_731:famili,fld_7882_dup_e_731:Rita Ora,fld_12826:BB

2) “Possible Values” Show Even When the Trigger Field Is Hidden – On Webforms

Possible Values (allowed options derived from another field) now resolve even if the trigger/conditional field is hidden by form logic. You configure Possible Values from the field settings of your selection fields.

Result: users still see the correct allowed options without exposing the control field.

3) Hidden Fields Can Drive Conditions & Values

Include hidden fields that actively influence conditional logic and Possible Values (filters, cascades, validations).

Great for: passing context from URL/session and shaping the form without extra clicks.

Why it’s great:

  • Frictionless prefill from campaigns, emails, and embeds
  • Cleaner UX: show only what matters while logic runs behind the scenes
  • More powerful conditional flows without revealing internal control.

Smarter Search & Better Indexing.
Find what you need faster – with more forgiving search across common fields.

1) Substring Search for Phone & Formula Fields

You can now search by partial strings in structured fields like Phone and Formula (e.g., typing 9725 or -321 will match the full value).
Result: quicker lookups, even if you only remember part of the number or calculated string.

2) Space/Dash-Aware Indexing for Text & Text Area

Search in Text and Text Area fields is now smarter about spaces and dashes. If a value contains separators – like a full name or a code – you can search any part after the space or dash and still get a match.

Examples

  • John Smith / john-smith → searching smith finds it
  • ACME-1234 → searching 1234 finds it
  • Customer Success → searching success finds it

How it works
Set the field filter to Contains to leverage the improved indexing and partial matching across separators.

Reports: New On-Screen Filters
Find the right report in seconds. The Reports screen for every entity now includes quick filters for:

  • Report Creator (who built it)
  • Creation Date (range picker)
  • Report Name (contains search)

Why it’s great

Cleaner organization when you’ve got lots of saved reports

Zero scrolling – jump straight to the report you need

Faster audits and housekeeping by owner and date

Convert & Copy: Map Date Fields + Time Picker

You can now map date fields in Convert & Copy workflows (e.g., Start Date, End Date, Due Date). When a mapped date field is required, the system opens a date & time selector so you can place the new occurrence exactly where you want it, no manual edits later.

How it works

  1. In your workflow, go to Step 3 – Action and choose Convert or Copy.
  2. Scroll to the Mapping section.
  3. Select the relevant Date/Date-Time field (e.g., Start Date).
  4. Open the field’s dropdown and choose Custom value.
  5. The familiar Date & Time picker (same as the frontend) will appear, pick your exact date/time and Save.


Convert & Copy: Dynamic Values for All System Fields

Supercharge your workflows. In Convert and Copy actions, you can now assign dynamic values to any system field at the moment of duplication/conversion – no manual edits afterward.

How it work

  1. In your workflow, choose Convert or Copy (Step 3 – Action).
  2. In Mapping, pick any system field.
  3. Open the field’s dropdown → choose Dynamic value.
  4. Compose your value with field references/formula → Save.

Why it’s great

  • One-shot setup: records are production-ready as they’re copied/converted
  • Consistent data: enforce naming, ownership, and SLAs automatically
  • Fewer edits: eliminate cleanup passes and human error

External Calendar Connection (per-user) – Webform Scheduling

Connect a user’s external calendar (Google or Microsoft) so your webform’s calendar element respects their real availability – including events not created in Origami. Each form is tied to a specific user’s calendar.

What you get

  • True availability: webform slots auto-avoid conflicts from the user’s external calendar (even non-Origami events).
  • Instant scheduling: submitting the webform creates an event in the connected calendar.
  • Two-way hygiene: deleting the event in Origami also deletes it in the external calendar and sends a cancellation email.
  • Auto-safety: if an admin changes the assigned user, the calendar disconnects automatically to prevent mis-routing.
Setup (once per form)

Step 1 – Add a User field to the entity
 This field represents the calendar owner.
Step 2 – Edit the Webform
Add the Calendar element to a new section and configure it.

Inside the Calendar element, define the date range for meetings and the time slots you want to offer.

To link a calendar, set the User field on the form to the user whose calendar you want to connect.

Save the form.

User connection flow (one-time per user)

After you save the form, the selected user gets an email asking them to connect their calendar.

In the email, the user clicks Click here and signs in with Google or Microsoft.


Once approved, the user sees a confirmation that the calendar is connected.

The user will receive a confirmation email with a Disconnect link in case he was removed from the user field in the Webform settings.

Live behavior after connection

  • The webform honors all events on the user’s external calendar (e.g., it won’t allow booking over a standing morning meeting).
  • Every webform submission automatically creates an event in the user’s external calendar – until the user disconnects.
  • Deleting the event in Origami removes it from the external calendar and triggers a cancellation email.

Calendar Element – Advanced Availability Controls (Webform)

Configured inside the Calendar element settings of your webform:

These options help you tailor availability beyond the basic date range & time slots.

1) Notice Time

Prevent “book-now-for-right-now” scenarios by enforcing a minimum lead time before a meeting can be booked.

  • What it does: hides slots that are too soon from the current time.
  • Example: set 30 minutes → if it’s 10:00, the earliest visible slot is 10:30.

Use when: your team needs prep time, room setup, or buffer before meetings.

2) Future Scheduling

Limit how far into the future people can book – inside your overall form date range.

  • What it does: sets a forward visibility cap (e.g., “only show the next 30 days”), even if the form’s date range spans longer.
  • Example: form covers 6 months, but Future Scheduling = 1 month → from today, users only see the next 30 days of slots.

Use when: you want rolling availability without exposing distant dates.

3) Max Meetings

Cap how many meetings can be booked per day / week / month.

  • What it does: once the limit is reached (including events from the connected external calendar), that period becomes unavailable in the form.
  • Example: set 5 per week → if the external calendar already has 5 meetings that week, the week won’t be selectable.

Use when: you need to control load, SLAs, or team capacity.