Skip to content
← All buyer guides

INTEGRATIONS

Connect your apps and bring the right information across

Start with a practical question: which information should move, where should it go and what should happen next? The answer tells us which connection your team needs.

01

Connect email and calendars

The integration catalogue includes Gmail, Outlook, Google Calendar and Microsoft Calendar. We check the account, the information involved and who can see it. Connecting a mailbox does not mean sharing every message with every colleague.

  • Choose which mailboxes and calendars to connect.
  • Confirm who can read the resulting activity.
  • Test the effect of disconnecting or changing account access.
02

Know the difference between an import and a sync

An import brings records across at one point in time. A sync keeps agreed information updated between systems. A workflow action does a particular job, such as passing a document to another tool. We confirm which kind each provider connection offers.

  • Ask whether your use case is an import, a workflow action or ongoing sync.
  • Agree which records should move and which actions should run.
  • Confirm provider subscription requirements and any implementation costs.
03

Build a connection for a specific job

An API lets apps exchange information and carry out actions. MCP lets a compatible assistant use approved tools. The CLI gives developers commands for scripts. Each connection needs the right account access and an action the other app actually supports.

  • Start with the documented API documentation or list of available tools.
  • List the information needed and check the result.
  • Decide what happens when an action fails, repeats or loses access.
04

Test the result and plan for errors

For example, check that a new enquiry creates the correct client record and gives Jamie the follow-up. Agree who is told if a connection fails and what happens if the same enquiry arrives twice. Test with example data before using it for daily work.

  • Identify which system is the main copy for each field.
  • Confirm how deletions and access changes are handled.
  • Give a person responsibility for connection failures.

Can Vitae connect to any app?

The app needs a way to exchange the information or perform the action you need. We check that access and agree the setup. A provider logo alone does not mean every feature of that app is available.

Read the Vitae API documentation

A PRACTICAL EXAMPLE

Connect an account and check the result.

See the workflow with example data. We will help you set it up around your team.

Vitae OSWorkflow exampleNS
Connected client record

Atlas & Co

Example data

CLIENT RECORD / FICTIONAL EXAMPLE

Vitae CRMCampaign brief
Agreed
Connected signing toolService agreement
Signed
Connected accounting toolFirst invoice
Awaiting payment
Vitae taskCheck in with Sam
Jamie · tomorrow

One client. Clear sources. Review before taking action.

Prepare the next conversation
04

Give the next conversation an owner and the right context.

Full example shown

EXPLORE THE TOOLS

LET'S CONNECT YOUR BUSINESS

You do the work.
Let your systems work together.

Book a demo

See a demo built around your business. Bring the tools you use and the tasks you want to improve.