← Back to Product overview

Getting in and out

Connect where you already work, and bring what you already have

Two different problems, both about not starting from zero: filing an email onto a contract record without leaving your inbox, and moving an existing roster of users, counterparties, or contracts into Contrayo without retyping every row by hand.

Email filing

File an email onto a contract record without leaving your inbox

One underlying capability — attach an email and its attachments to an existing contract record, tenant-scoped and safe to retry — reachable from wherever you actually read your mail.

Outlook add-in

A task-pane add-in for Outlook: open an email, pick the contract it belongs to, and file it — including attachments — onto that record. Deployed by your IT admin via manifest sideload or your organization's Microsoft 365 admin center, the same model Contrayo's existing Word add-in already ships with, rather than a public app-store listing.

Zapier and Make

A documented recipe — find the right contract, then file the email onto it — using two public API calls. Available on every tier, including self-serve, unlike the rest of Contrayo's public API, which is a Mid-market/Enterprise feature. Set up today by following the documented steps in either tool; a one-click Zapier app-directory listing is real, tested code in progress, not yet published.

Or call the API directly

The same lookup-then-file capability behind the Outlook add-in and the Zapier/Make recipe is a plain public API call — useful if you're already scripting against Contrayo or building your own integration.

The native Gmail add-on is built, not yet turned on. A Gmail add-on with the same "pick the contract, file the email" experience as the Outlook add-in is complete and tested, but shipped off by default — Google requires its own review of any Gmail add-on that requests inbox access before it can reach a real mailbox, and that review hasn't been completed yet. Until it is, file a Gmail message the same way as any other email: through Zapier/Make or the public API above.
Bulk import

Bring your existing roster in, don't retype it

Three importers — users, counterparties, and contracts — all built on the same reviewed engine: upload a TSV file, see exactly what will happen to every row, fix what needs fixing, and confirm before anything is created. Nothing imports silently; nothing is guessed.

Users

Upload a roster with name, email, and role — each accepted row becomes an ordinary invite, indistinguishable from one sent by hand. Up to 200 rows per file, on every tier including self-serve. An address that's already a member, or already invited, is skipped and reported, never overwritten — re-running the same file after fixing a few rows is safe.

Counterparties

Upload a list of counterparty names and see which are new versus already on file before anything is created — up to 500 rows per file, on every tier including self-serve.

Contracts

Bring in your existing contract register — title, type, status, counterparty, value, business unit, signing entity, and key dates — up to 200 rows per file, on every tier. An imported contract is never automatically routed through the approval engine: a migrated register is historical, already-executed paperwork, not a stack of new approval requests, so nothing fires at your approvers because you migrated. Route an individual contract yourself, the same one click a newly-created contract already needs, only for the ones that genuinely still need it.See how routing works →

Not gated behind a higher tier or a services engagement. Bulk user provisioning is often an Enterprise-only, SCIM-gated feature elsewhere in this category, and CLM implementation is commonly billed as professional services at $200–350 an hour. Contrayo's user and counterparty importers ship on every tier, including self-serve, with no separate fee.
Said plainly

What this doesn't do yet

No compose-side add-in

Both the Outlook and Gmail add-ins work from a message you're reading, not one you're writing — pulling contract data into an email you're composing isn't built.

No attachments through Zapier/Make yet

The Zapier app's filing step carries the message itself but doesn't yet expose an attachments field in either tool — the underlying capability supports it; the no-code step doesn't wire it up yet.

Contract import doesn't create counterparties

A contract row naming a counterparty that isn't on file yet is skipped, not auto-created — import your counterparties first, then re-run the contracts file.

No document or attachment migration

The contracts importer brings in record metadata — not the underlying contract files themselves. Attach documents to an imported record the same way you would any other.

Connected to

What this feeds

Contract records

A filed email or an imported contract becomes an ordinary record — the same one every other feature reads.

See contract records →

The DoA engine

An imported contract stays unrouted until you route it — the same policy that decides who approves everything else.

See the approval engine →

No separate line item for getting your data in

Bulk import and email filing ship at the same published price as everything else. Check the tier that fits your organization.