Resources · Make integration

Clio Manage Make integrationAutomate Clio Manage with Make.

What if new matters, contacts and documents in Clio Manage kicked off the follow-up work for you? The Clio Manage Make integration gives you 47 modules, 9 of them triggers. This guide shows how to link your account, build a first scenario and pick the right module for each job.

Try the Clio Manage integration on MakeSee the 47 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Clio Manage Make integration do for you?

The Clio Manage Make integration links your Clio account to Make, a visual tool where you build a scenario: an automation made of modules, each one a trigger, an action or a search. Clio Manage brings 47 of these modules, so matters, contacts, tasks, notes, documents and bills can move without anyone copying them by hand.

A task for every new document. Watch Documents spots each new file in Clio Manage, and Create a Task puts a review item on someone's list. Nobody has to remember to check the documents tab.

A cleaner contact list. Watch Contacts reacts the moment a contact is created, updated or deleted. Pair it with Search Contacts to catch a duplicate before Create a Contact adds a second copy.

Matter changes that reach the right people. When Watch Matters fires, Get a Matter pulls the full record and Create a Note or Create a Calendar Entry leaves a trace in the file.

A few limits are worth knowing before you start. The connection needs a registered developer application in Clio, not just a user login. The official Make documentation for this app is marked as AI-generated and asks you to verify important details, so test each module with Run once before you trust it. When a listed module does not cover your case, Make an API Call reaches the rest of the Clio API with the same connection.

The same app often has an n8n node too; the n8n vs Make comparison helps you choose. To get comfortable with the editor first, see Make training, or hand the build to a Make agency.

Connect

How do you connect Clio Manage to Make?

  1. 01

    Register a developer application in Clio

    In the Clio Developer Portal, create a new application, pick your region and paste https://www.integromat.com/oauth/cb/clio-manage as the callback URI. Clio then shows a Client ID and a Client secret: copy both.

  2. 02

    Add a Clio Manage module in Make

    Open your scenario, add any Clio Manage module and click Create a connection. A connection is your Clio account linked to Make once, then reused by every Clio module. The Connection name field is optional but helps when you have several.

  3. 03

    Paste the credentials and authorize

    Enter the Client ID and Client secret you copied, then follow the on-screen instructions to approve access in Clio. Once the connection is saved, Make can read your matters, contacts and other records when you fill in each module.

First scenario

Build your first scenario with Clio Manage

GoalWhen a new document lands in Clio Manage, Make creates a task so someone reviews it.

  1. 01

    Create a new scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module on the canvas.

  2. 02

    Pick Watch Documents

    Search for Clio Manage, choose Watch Documents and click Create a connection if this is your first Clio module. This trigger is scheduled: Make checks Clio for new documents at each run.

  3. 03

    Add Create a Task

    Click the + on the right of the trigger, pick Create a Task and map the document details from the previous module into the task, so the reviewer knows exactly which file to open.

  4. 04

    Test with Run once

    Add a document in Clio, then click Run once. Each module shows the bundles it received, a bundle being one item passed along. Check that one task appeared in Clio Manage.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Save, then switch the scenario on.

Triggers

Which Clio Manage triggers start a scenario?

9 modules start a scenario when something happens in Clio Manage. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Clio Manage as soon as it happens.

Clio Manage1Watch Activities

Watch Activities

Instant trigger

In Make“Triggers when a contact is created, updated or deleted.”

Watch Activities hands your scenario a fresh bundle each time an activity moves in Clio Manage, so the change can be copied, logged or reported elsewhere without a manual export.

How it fires
instant: Clio calls Make through a webhook as soon as it happens, so the scenario runs without waiting for a schedule.
When to use it
when an activity recorded on a matter should update a report sheet or alert the person who follows that client.
Watch out
the Make directory describes this trigger with the contact wording (created, updated or deleted), so run it once with a test activity to see exactly what it sends before you build on it.
Clio Manage2Watch Bills

Watch Bills

Instant trigger

In Make“Triggers when a bill is created, updated or deleted.”

Your billing work gets a live feed: this trigger passes a bill to Make whenever one is created, updated or deleted in Clio Manage, ready to be sent to accounting or a follow-up list.

How it fires
instant: Clio notifies Make by webhook the moment the bill changes, so nothing waits for a schedule.
When to use it
when a new or edited bill should reach the person who handles collections, or a shared tracker the partners read.
Watch out
three kinds of events arrive through the same door. If only new bills matter to you, check the bundle after Run once and add a filter so edits and deletions do not create extra work.
Clio Manage3Watch Calendar Entries

Watch Calendar Entries

Instant trigger

In Make“Triggers when a bill is created, updated or deleted.”

Hearings, meetings and deadlines placed in the Clio calendar can reach other tools the moment they are set, because this trigger sends each calendar entry to your scenario.

How it fires
instant: Clio calls Make through a webhook as soon as the entry changes.
When to use it
when a new entry should also land in a team channel or in another calendar that assistants watch.
Watch out
the directory text for this module repeats the bill description, a copy slip on Make's side. Test it with Run once on a real calendar entry and read the bundle before mapping any field.
Clio Manage4Watch Communications

Watch Communications

Instant trigger

In Make“Triggers when a communication is created, updated or deleted.”

Every logged call, email or message record in Clio becomes something Make can act on: the trigger delivers the communication as soon as it is created, updated or deleted.

How it fires
instant: Clio sends a webhook call to Make right away, so nothing waits for the next scheduled check.
When to use it
when a communication logged on a matter should notify the responsible lawyer or feed a client history kept outside Clio.
Watch out
an update fires the trigger again. A scenario that writes back to the same communication with Update a Communication can end up calling itself, so keep the write in another record.
Clio Manage5Watch Contacts

Watch Contacts

Instant trigger

In Make“Triggers when a contact is created, updated or deleted.”

Keep every other system in step with your Clio contact list: this trigger fires on each created, updated or deleted contact and passes the record to the next module.

How it fires
instant: Clio calls Make through a webhook the moment the contact changes.
When to use it
when a new client entered by the front desk should also appear in your mailing tool or CRM without a second round of typing.
Watch out
deletions arrive too. Run once on a deleted test contact to see what arrives, then filter before any module creates something, or a deleted contact could be recreated somewhere else.
Clio Manage6Watch Documents

Watch Documents

Scheduled trigger

In Make“Triggers when a new document is created.”

Watch Documents looks for newly created documents in Clio Manage and sends one bundle per file, which makes it the natural start for review, filing or notification flows.

How it fires
scheduled: Make checks Clio on the scenario's schedule, every 15 minutes by default, and picks up what arrived since the last check.
When to use it
when each new document on a matter should trigger a review task or a message to the paralegal in charge.
Watch out
it reports new documents only, not edits. Also avoid ending the same scenario with Upload a Document, since that file would be caught on the next run.
Clio Manage7Watch Matters

Watch Matters

Instant trigger

In Make“Triggers when a matter is created, updated or deleted.”

Opening a matter in Clio can set the rest of the intake in motion: this trigger passes the matter to Make each time one is created, updated or deleted.

How it fires
instant: Clio calls Make through a webhook as soon as the matter changes.
When to use it
when a new matter should get its folder, its first tasks and a welcome note without anyone clicking through the same checklist.
Watch out
the same trigger fires on every edit of the matter. Look at an edit with Run once, then add a filter after the trigger, or each small change will create another folder and another round of tasks.
Clio Manage8Watch Notes

Watch Notes

Scheduled trigger

In Make“Triggers when a new note is created.”

Notes written in Clio Manage can travel beyond the matter they belong to: this trigger collects each new note and hands it to your scenario for forwarding or archiving.

How it fires
scheduled: Make asks Clio for new notes on the scenario's schedule instead of being called by Clio.
When to use it
when a note added after a client call should be copied into a shared digest or a document the whole team reads.
Watch out
only new notes come through, so a later edit stays invisible here. Do not add Create a Note in the same flow, or the note it writes becomes the next run's input.
Clio Manage9Watch Tasks

Watch Tasks

Instant trigger

In Make“Triggers when a task is created, updated or deleted.”

This trigger turns task changes in Clio into events Make can route, sending the task each time one is created, updated or deleted.

How it fires
instant: Clio notifies Make by webhook the moment the task changes, without waiting for a scheduled check.
When to use it
when a task assigned in Clio should also ping the assignee in a chat tool, or when a completed task should move a line in a tracking sheet.
Watch out
a scenario that answers with Update a Task on the same task will fire the trigger again. Write to another object, or filter out the changes your own scenario makes.
Modules

What else can Make do in Clio Manage?

Clio Manage gives you 38 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Clio Manage1

Create a Calendar Entry

Action

In Make“Creates a new calendar entry.”

Put a date straight into the Clio calendar from any other app, so a meeting booked elsewhere shows up where the firm plans its week.

When to use it
after a booking tool confirms an appointment, or when a new matter needs a first meeting on the calendar.
Watch out
every bundle creates one entry, so a trigger that also fires on updates will stack duplicates unless you filter it.
Clio Manage2

Create a Communication

Action

In Make“Creates a new communication.”

Log an exchange in Clio without opening it: this module records a communication from data another app already holds, such as an email or a form reply.

When to use it
when client emails received in a shared inbox should also be kept in the Clio history of the matter.
Watch out
if Watch Communications starts the same scenario, the record you create fires it again; keep the two in separate flows.
Clio Manage3

Create a Contact

Action

In Make“Creates a new contact.”

New people enter Clio Manage without retyping: the module turns a form entry, a lead or a signed agreement into a Clio contact.

When to use it
when an intake form on your website collects the name and email of a prospective client.
Watch out
Make does not check for an existing record here. Place Search Contacts before it and create only when the search comes back empty.
Clio Manage4

Create a Folder

Action

In Make“Creates a new folder.”

A folder appears in Clio Manage, ready to receive the files of a case, so every matter starts with the same tidy structure.

When to use it
right after Watch Matters reports a new matter, to build the folders your team expects to find there.
Watch out
run it once per event you care about. If the trigger also sends matter updates, each edit adds another folder.
Clio Manage5

Create a Matter

Action

In Make“Creates a new matter.”

Opening a file no longer waits for someone at a desk: Create a Matter builds the matter in Clio from data collected upstream, like a signed engagement or a qualified lead.

When to use it
when an e-signature or CRM step marks a deal as won and the case should exist in Clio right away.
Watch out
the matter usually belongs to a client, so find or create that contact first and map it in.
Clio Manage6

Create an Activity

Action

In Make“Creates a new activity.”

Record an activity in Clio from outside, so work done in another tool still shows up in the firm's system of record.

When to use it
when a task finished in a project tool should leave a matching activity on the matter.
Watch out
this page does not go into the fields an activity needs. Fill the module once by hand, click Run once, and check the result in Clio before mapping data automatically.
Clio Manage7

Create a Note

Action

In Make“Creates a new note.”

Leave a written trace in Clio automatically: this module adds a note, which is handy for recording what an automation did and when.

When to use it
when a matter changes stage and the team wants a short note explaining what triggered it, or to store a form answer next to the case.
Watch out
with Watch Notes at the start of the same scenario, this note would come back as a new input on the next run.
Clio Manage8

Create a Task

Action

In Make“Creates a new task.”

Hand out work in Clio from any event: Create a Task adds a to-do there, so follow-ups live in the tool your team already checks.

When to use it
when a new document, a new matter or a client email means someone has to act on it.
Watch out
if Watch Tasks sits in another active scenario, the new task wakes it up too. Map a clear task name so both flows stay readable.
Clio Manage9

Delete a Calendar Entry

Action

In Make“Deletes a calendar entry by identificator.”

Remove a calendar entry from Clio when its source disappears, so cancelled meetings stop cluttering the schedule.

When to use it
when an appointment is cancelled in a booking tool and the matching Clio entry should go too.
Watch out
the module works by identifier and a deletion cannot be undone from Make. Store the Clio entry ID when you create it, so you remove the right one later.
Clio Manage10

Delete a Communication

Action

In Make“Deletes a communication by identificator.”

Clear a communication record from Clio by its identifier, for example one that was logged by mistake by another scenario.

When to use it
in a clean-up flow that removes records flagged as duplicates after a review in a spreadsheet.
Watch out
nothing asks for confirmation. Test on a dummy record with Run once and keep a copy of the data elsewhere before you let it run on its own.
Clio Manage11

Delete a Contact

Action

In Make“Deletes a contact by identificator.”

Take a contact out of Clio Manage by its identifier when it no longer belongs in your records.

When to use it
when a merge done in another system leaves a duplicate that should disappear from Clio as well.
Watch out
this one hurts most if it goes wrong, because contacts are linked to matters. Run Get a Contact first to be sure of the target, and only then delete.
Clio Manage12

Delete a Folder

Action

In Make“Deletes a folder by identificator.”

Delete a Clio folder by its identifier, useful for removing structures that an earlier automation created by mistake.

When to use it
when you tested a folder-building scenario and need to remove the empty folders it left behind.
Watch out
what sits inside a folder matters more than the folder itself. Check its content in Clio before you let Make remove it, since there is no undo in the scenario.
Clio Manage13

Delete a Matter

Action

In Make“Deletes a matter by identificator.”

Remove a matter from Clio Manage by its identifier, the heaviest of the delete modules because a matter carries the whole case.

When to use it
rarely; a typical case is a test matter created while you were building and checking a scenario.
Watch out
keep this module out of any flow that runs unattended on real data. A wrong ID mapping deletes a live matter, and Make cannot bring it back.
Clio Manage14

Delete an Activity

Action

In Make“Deletes an activity by identificator.”

This module erases one activity from Clio, found by its identifier, so wrong entries do not stay on the matter.

When to use it
when an activity pushed from another tool turns out to be a duplicate and your reviewer marks it for removal.
Watch out
map the ID from a trusted source, such as Search or Get, and test on a sample first; the deletion is final once the scenario runs.
Clio Manage15

Delete a Note

Action

In Make“Deletes a note by identificator.”

Notes that no longer belong on a matter can be removed by identifier, keeping the case history readable.

When to use it
when an automation wrote notes during testing and you want them gone before the team sees them.
Watch out
a note removed here is gone from Clio for everyone. Limit the scenario to notes your own automation created, and keep their IDs when you write them.
Clio Manage16

Delete a Task

Action

In Make“Deletes a task by identificator.”

Drop a task from Clio by its identifier when the work it describes is no longer needed.

When to use it
when a matter is closed elsewhere and the open follow-up tasks created by Make should disappear with it.
Watch out
if Watch Tasks runs in another scenario, this deletion fires it too. Decide in advance how that scenario should react to removed tasks.
Clio Manage17

Get a Calendar Entry

Action

In Make“Gets an existing calendar entry.”

Fetch the full details of one calendar entry from Clio, so the next modules can use what the trigger alone did not include.

When to use it
after Watch Calendar Entries, to read the complete entry before posting a reminder or copying it to another calendar.
Watch out
it reads one existing entry and needs its ID mapped from an earlier module; on its own it cannot guess which entry you mean.
Clio Manage18

Get a Communication

Action

In Make“Gets an existing communication.”

Read back one existing communication from Clio, with everything Clio stores on it, to feed a report or a message.

When to use it
when a trigger or a note only points to a communication and you need its full content before forwarding it to a colleague.
Watch out
reading counts as an operation, one module run on one bundle, so skip it if the trigger already gives you what you need.
Clio Manage19

Get a Contact

Action

In Make“Gets an existing contact.”

Pull one contact's record from Clio Manage when a scenario needs more than a name, before sending a message or filling a document.

When to use it
after Watch Matters, to fetch the client attached to the matter and reuse their details in a welcome email.
Watch out
it expects a known contact. If all you have is an email or a name, use Search Contacts instead.
Clio Manage20

Get a Folder

Action

In Make“Gets an existing folder.”

Look up one existing folder in Clio to learn what it holds or where it sits before another module works with it.

When to use it
before Upload a Document, to confirm the target folder exists and map it in with confidence.
Watch out
a folder ID from another scenario can point to something deleted since. Run once and check that the bundle is not empty before relying on it.
Clio Manage21

Get a Matter

Action

In Make“Gets an existing matter.”

Load a whole matter from Clio in one step, which gives later modules the case details they need to write messages or create records.

When to use it
after a task or note trigger, to know which case it belongs to and who is responsible for it.
Watch out
without a matter ID to map, the module has nothing to read. When you only know a name or number, go through Search Matters first.
Clio Manage22

Get an Activity

Action

In Make“Gets an existing activity.”

Read the complete record of one activity in Clio, useful when a report or an invoice check needs more than the trigger delivered.

When to use it
after Watch Activities, to fetch the full activity before copying it into a spreadsheet the partners review.
Watch out
it works on a single existing activity. To go through many of them, a search or a trigger must hand over the IDs one bundle at a time.
Clio Manage23

Get a Note

Action

In Make“Gets an existing note.”

Retrieve a single note from Clio with its text, so another app can store, forward or analyze what was written.

When to use it
when Watch Notes gives you a new note and you want its complete content before sending it to a shared channel.
Watch out
if the trigger bundle already carries the text you need, this extra read only adds an operation to your plan.
Clio Manage24

Get a Task

Action

In Make“Gets an existing task.”

Get the current state of one Clio task, so a scenario can decide what to do based on what the task says right now.

When to use it
after Watch Tasks, to read the latest version of the task before updating a project board or pinging its assignee.
Watch out
it needs the task ID from an earlier module. Map it from the trigger, not typed by hand, or the scenario will always read the same task.
Clio Manage25

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reach any part of the Clio API that the listed modules leave out, using the connection you already set up, with no second login.

When to use it
when you need a Clio object or an operation that none of the other modules offers, for example a record type not covered here.
Watch out
you write the request yourself, so keep the Clio API reference open and test with Run once before mapping the response into later modules.
Clio Manage26

Update a Calendar Entry

Action

In Make“Updates an existing calendar entry.”

Change an existing calendar entry in Clio so the firm's schedule follows when a meeting moves somewhere else.

When to use it
when a client reschedules through a booking tool and the Clio entry should move to the new slot.
Watch out
the module needs the ID of the entry to change. Keep it when you create the entry, or you will have nothing reliable to map later.
Clio Manage27

Update a Communication

Action

In Make“Updates an existing communication.”

Edit a communication already stored in Clio, for instance to complete a record that was logged in a hurry.

When to use it
when a follow-up reply arrives and you want the original communication record to reflect it.
Watch out
an edit fires Watch Communications. If that trigger starts this same scenario, you have built a loop; split the flows or filter your own changes out.
Clio Manage28

Update a Contact

Action

In Make“Updates an existing contact.”

Keep Clio contact details current from the system where they change first, like a CRM or a client portal.

When to use it
when a client updates their phone or address in another tool and Clio should follow without a manual edit.
Watch out
find the right contact first with Search Contacts, and handle the case where the search returns nothing or more than one result.
Clio Manage29

Update a Folder

Action

In Make“Update an existing folder.”

Rename or adjust an existing Clio folder from a scenario, so the structure keeps pace with the case.

When to use it
when a matter changes name or stage and its folder should carry the new label your team searches for.
Watch out
only existing folders can be changed. Store the folder ID when Create a Folder runs, since that is what this module needs later.
Clio Manage30

Update a Matter

Action

In Make“Updates an existing matter.”

Move a matter forward in Clio from outside events: this module edits an existing matter with new information.

When to use it
when an e-signature is completed or a payment clears elsewhere and the matter should show the new stage.
Watch out
Watch Matters also fires on updates. Keep the two in separate scenarios, or filter on the change, so the update does not restart the flow.
Clio Manage31

Update an Activity

Action

In Make“Updates an existing activity.”

Correct or complete an activity already in Clio, keeping what was recorded in line with what really happened.

When to use it
when a reviewer fixes an entry in a shared sheet and the change should flow back to Clio.
Watch out
map the activity ID carefully; an update on the wrong record replaces data silently, and Make will report the run as a success.
Clio Manage32

Update a Note

Action

In Make“Updates an existing note.”

Rewrite a note that already exists in Clio, which lets one living note replace a pile of small ones.

When to use it
when a scenario maintains a status note on each matter and should refresh it rather than adding a new note each time.
Watch out
keep the note ID from its creation. Without it, you are back to creating notes, and the history grows again.
Clio Manage33

Update a Task

Action

In Make“Updates an existing task.”

Change a Clio task from another tool, for example to reassign it or mark progress made elsewhere.

When to use it
when work tracked in a project board moves forward and the matching Clio task should reflect it.
Watch out
this edit wakes up Watch Tasks. If that trigger sits at the start of the same scenario, each update calls the scenario again.
Clio Manage34

Upload a Document

Action

In Make“Creates a new document.”

Send a file into Clio Manage as a new document, so contracts or scans produced by other tools end up in the case file.

When to use it
when an e-signature tool returns a signed contract, or an email attachment should be filed on the matter.
Watch out
the Free plan handles files up to 5 MB. Also keep Watch Documents out of this scenario, or the uploaded file comes back as input.
Clio Manage35

Search Bills

Search

In Make“Searches for bills or lists them all.”

Find bills in Clio, or list them all, and pass each one on as its own bundle for reporting or reminders.

When to use it
when a scenario should gather the bills for one client or matter and write them into a sheet for review.
Watch out
a search can return zero, one or many bills, and each following module runs once per bill. A wide search can use many operations.
Clio Manage36

Search Contacts

Search

In Make“Searches for contacts or lists them all.”

Check whether a person already exists in Clio before doing anything else, or pull a list of contacts for a sync.

When to use it
ahead of Create a Contact, to avoid duplicates when a web form sends a returning client.
Watch out
an empty result does not stop the scenario on its own. Add a filter after the search that only lets the flow continue when zero contacts came back.
Clio Manage37

Search Matters

Search

In Make“Searches for matters or lists them all.”

Locate matters in Clio from what you know, or list them, so later modules can act on the right case.

When to use it
when an email or form mentions a case and you need the matching matter before adding a note or a task.
Watch out
several matches mean several bundles and several runs of the next module. Narrow the search so one case comes back.
Clio Manage38

Search Users

Search

In Make“Searches for users or lists them all.”

List the people who work in your Clio account, or find one of them, to assign work to the right person.

When to use it
before Create a Task, when the assignee comes from an outside tool and you need the matching Clio user.
Watch out
users are your colleagues, not clients. To look for a client, use Search Contacts instead.
Need help

Need help automating Clio Manage with Make?

A person reads every message.

FAQ

Clio Manage and Make: common questions

01Is the Clio Manage Make integration free?
Yes, on the Make side. Clio Manage is a standard app, available from the Free plan like the 3,000+ other standard apps. The Free plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and count usage in operations per month. You still need your own Clio account, which Clio bills separately.
02What do you need to connect Clio Manage to Make?
You need a Clio account and a registered developer application in Clio. In the Developer Portal, create an application, pick your region and enter the callback URI given by Make, then copy the Client ID and Client secret. In Make, add a Clio Manage module, click Create a connection, and paste both values or follow the on-screen steps. With an instant trigger, click Create a webhook first. One connection then serves every Clio module in your scenarios.
03Do the Clio Manage triggers in Make fire in real time?
Most of them do. Seven triggers are instant: Watch Activities, Watch Bills, Watch Calendar Entries, Watch Communications, Watch Contacts, Watch Matters and Watch Tasks. Clio calls Make through a webhook as soon as the record is created, updated or deleted. The two others, Watch Documents and Watch Notes, are scheduled: Make checks Clio on the scenario's schedule, every 15 minutes by default and never more often than every 15 minutes on the Free plan, or 1 minute on paid plans.
04What if the Clio Manage module you need is missing in Make?
Use Make an API Call. It sends any request to the Clio API with the connection you already created, so an object or operation missing from the other modules is still within reach. You will need to read the Clio API reference to write the request. Keep in mind that the Make documentation for this app is flagged as AI-generated, so check important details with Clio directly and test every module with Run once before activating a scenario.
05Should you use Make or n8n for Clio Manage?
It depends on the tool your team already uses and knows. On Make, Clio Manage comes with 47 modules, including 9 triggers, and this page walks through the connection and a first scenario. The same app often has an n8n node as well, so compare the two against the objects and events you actually need, such as matters, bills or documents, rather than on general reputation. The n8n vs Make comparison linked above sets out the differences between the two platforms.
Same platform

Other docs you might need on this stack.

Browse all integrations