Resources · Make integration

Syncro Make integrationAutomate Syncro with Make.

Can Make open a Syncro ticket the moment a new client is created? Yes: Make offers 20 Syncro modules, 5 of them instant triggers. This Syncro Make integration guide helps MSP teams connect their account and build a first scenario without code.

Try the Syncro integration on MakeSee the 20 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Syncro Make integration do?

The Syncro Make integration links your Syncro account to Make, a visual tool where you chain apps together without code. It gives you 20 modules: 5 instant triggers that react to new customers, invoices, payments, RMM alerts and ticket changes, plus actions and searches on customers, leads and tickets.

Onboarding that starts itself. Watch New Customers fires when a client record is created, and Create a Ticket opens the setup ticket for your technicians. That is the first scenario built further down this page.

Alerts that reach a person. Watch New RMM Alerts passes each monitoring alert to Make, which can post it in the team chat or open a ticket, so a warning never sits unseen on a dashboard.

Billing news for the finance side. Watch New Invoices and Watch New Payments feed a spreadsheet or an accounting tool, and Update a Ticket can record the follow-up once the money arrives.

What the list leaves out: no module creates or edits invoices and payments, and leads have no delete module. Make an API Call covers those gaps with the same connection. Weighing another tool? The n8n vs Make comparison sets out the criteria, Make pricing explains how usage is counted, and the Make training goes further than this guide.

Connect

How do you connect Syncro to Make?

  1. 01

    Create an API token in Syncro

    In Syncro, open Profile/Password from the account menu, then API Tokens and New Token. On Custom Permissions, name the token, set an expiration date and the permissions you need, click Create API Token and copy it.

  2. 02

    Add a Syncro module in Make

    In your scenario, add any Syncro module and click Create a connection. A connection is your Syncro account linked to Make once and reused by every Syncro module after that. You can give it a name in Connection name.

  3. 03

    Paste the token and save

    Enter the token you copied from Syncro and confirm. Make can now read your customers, leads and tickets. For an instant trigger, click Create a webhook first, then create or pick the connection.

First scenario

Your first scenario: a ticket for every new Syncro customer

GoalWhen a new customer is created in Syncro, Make opens an onboarding ticket for that client.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. A scenario is the automation itself: a chain of modules that Make runs for you.

  2. 02

    Add Watch New Customers

    Search for Syncro, pick Watch New Customers, click Create a webhook, then Create a connection and paste your API token.

  3. 03

    Add Create a Ticket

    Click the + on the right of the trigger, choose Syncro again and pick Create a Ticket. Make reuses the same connection, so no second token is needed.

  4. 04

    Map the customer data

    Fill the ticket fields by mapping data from the first module, so each ticket carries the details of the client who just arrived. Make lists what it can read once the connection works.

  5. 05

    Test with Run once

    Click Run once, then create a test customer in Syncro. Read the bundle each module received and check the new ticket in Syncro before going further.

  6. 06

    Switch it on

    Turn the scenario on. Because the trigger is instant, Syncro calls Make as soon as a customer is created, with no polling schedule to wait for.

Triggers

What can start a Syncro scenario?

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

Syncro1Watch New Customers

Watch New Customers

Instant trigger

In Make“Triggers when a new customer has been created.”

Watch New Customers starts your scenario the moment a customer record appears in Syncro and hands Make that customer as a bundle, the item passed from one module to the next. From there you can open an onboarding ticket or copy the contact into another tool.

How it fires
instant. Syncro calls Make through a webhook as soon as the customer is created, so there is no interval to wait for.
When to use it
a new client signs with your MSP and setup work should begin without anyone retyping their details.
Watch out
when you add it, Make asks you to click Create a webhook before Create a connection; follow that order.
Syncro2Watch New Invoices

Watch New Invoices

Instant trigger

In Make“Triggers when a new invoice has been added.”

Watch New Invoices hands Make every invoice added in Syncro, so billing news can travel to your accounting or chat tools without a manual export. Each invoice arrives as its own bundle.

How it fires
instant. Syncro notifies Make through a webhook as soon as the invoice is added.
When to use it
your bookkeeper wants a message, or a new spreadsheet row, whenever a technician bills a job.
Watch out
the Syncro module list has no action that creates or edits invoices, so this trigger only reads them; to change an invoice from a scenario, turn to Make an API Call.
Syncro3Watch New Payments

Watch New Payments

Instant trigger

In Make“Triggers when a new payment has been added.”

Watch New Payments lets a scenario react when money comes in: each payment recorded in Syncro reaches Make as a bundle you can pass along. Every module that then processes it counts as one operation, a single execution of a module and the unit Make counts on your plan.

How it fires
instant. Syncro sends the payment to Make through a webhook right after it is added.
When to use it
a client settles an overdue invoice and the account manager should hear about it, or the ticket that tracked the debt should be closed out with Update a Ticket.
Syncro4Watch New RMM Alerts

Watch New RMM Alerts

Instant trigger

In Make“Triggers when a new RMM alert has been added.”

Watch New RMM Alerts brings the alerts raised by Syncro's remote monitoring into Make, so a warning on a client machine reaches a person or a ticket straight away.

How it fires
instant. As soon as the alert is added, Syncro calls Make through a webhook.
When to use it
your on-call technician lives in a chat app and should see new alerts there, or each alert should open a ticket with Create a Ticket.
Watch out
every alert is one bundle, and each module after the trigger spends an operation on it, so a noisy client network can use up the operations on your plan quickly.
Syncro5Watch Ticket

Watch Ticket

Instant trigger

In Make“Triggers when a ticket has been created, updated or resolved.”

Watch Ticket follows the whole life of a ticket: Make receives it when it is created, when it is updated and when it is resolved. That makes it the trigger for status reports, client notifications and handoffs between teams.

How it fires
instant. Syncro calls Make through a webhook each time one of those three events happens.
When to use it
a client should get a short note when their ticket is resolved, or a manager wants each new ticket posted to a team channel.
Watch out
an update fires Watch Ticket again, so keep Update a Ticket out of any scenario that starts from this trigger.
Modules

What can Make do in Syncro?

Syncro gives you 15 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Syncro1

Create a Customer

Action

In Make“Creates a new customer.”

Create a Customer adds a new client record to Syncro from data another app already holds, such as a signed quote or a form entry, so nobody retypes the company name and contact.

When to use it
a deal is won in your CRM and the client must exist in Syncro before the first ticket.
Watch out
run Search Customers first when the same client could come in twice, or duplicates will pile up.
Syncro2

Create a Lead

Action

In Make“Creates a new lead.”

Create a Lead puts a prospect into Syncro's lead list, which keeps early conversations apart from paying customers until the deal is real.

When to use it
someone fills the contact form on your website asking for managed IT support, and sales wants the request in Syncro rather than buried in an inbox.
Watch out
check with Search Leads before creating, since the same person may write twice.
Syncro3

Create a Ticket

Action

In Make“Creates a new ticket.”

Create a Ticket opens a support ticket in Syncro from any event Make can see: an email, an alert, a form, a chat message. Your technicians keep working from one queue.

When to use it
a new customer arrives through Watch New Customers and an onboarding ticket should be waiting for the team.
Watch out
if the incoming data only holds an email address, find the client first with Search Customers so the ticket lands on the right account.
Syncro4

Delete a Customer

Action

In Make“Deletes a customer specified by ID.”

Delete a Customer removes a client record from Syncro, identified by its ID. It is the cleanup step for records that should not exist.

When to use it
a test account created while building a scenario has to disappear, or a duplicate found by Search Customers must go.
Watch out
none of the Syncro modules restores a deleted record, so treat the deletion as final: test with Run once on a dummy record and check the ID it receives before switching the scenario on.
Syncro5

Delete a Ticket

Action

In Make“Deletes a ticket specified by ID.”

Delete a Ticket erases one ticket, chosen by its ID, from Syncro. Keep it for tickets that should never have existed rather than ones that are simply finished.

When to use it
an automation opened tickets from spam emails and the queue needs clearing, with Search Tickets feeding the IDs.
Watch out
no module in the list brings a deleted ticket back; for a job that is done, Update a Ticket is the safer choice.
Syncro6

Get a Customer

Action

In Make“Retrieves a single customer specified by ID.”

Get a Customer reads one client record from Syncro when you already know its ID, and makes its details available to every module that follows.

When to use it
an earlier module has given you the customer's ID and the next step needs the full record, for example to write to the right contact.
Watch out
it needs the ID; with only a name in hand, start with Search Customers.
Syncro7

Get a Lead

Action

In Make“Retrieves a single lead specified by ID.”

Get a Lead fetches a single prospect from Syncro by its ID, so a scenario can check where that lead stands before acting on it.

When to use it
a follow-up automation stored the lead's ID earlier and now needs its current details before sending anything.
Watch out
it returns exactly one lead and needs its ID; to find leads any other way, go with Search Leads.
Syncro8

Get a Ticket

Action

In Make“Retrieves a single ticket specified by ID.”

Get a Ticket pulls one ticket from Syncro by its ID, in its current state, so the rest of the scenario works on fresh data instead of what an earlier step saw.

When to use it
a message in your chat tool contains a ticket ID and the scenario should reply with that ticket's details.
Watch out
test with Run once on a real ticket ID and read the bundle it returns before mapping anything.
Syncro9

Make an API Call

Action

In Make“Performs an arbitary authorized API call.”

Make an API Call lets a scenario reach any endpoint of the Syncro API with the connection you already set up, which covers whatever the other modules leave out.

When to use it
you need something the ready-made modules do not offer, such as changing an invoice, since the list only watches invoices and payments.
Watch out
you write the request yourself from the Syncro API documentation, so it asks more of you than the other modules.
Syncro10

Update a Customer

Action

In Make“Updates a customer specified by ID.”

Update a Customer changes an existing client record in Syncro, found by its ID, so details that change elsewhere stay in step without copy and paste.

When to use it
a client's billing contact changes in your accounting tool and Syncro should show the new person too.
Watch out
it needs the customer ID, which comes from Search Customers or from a trigger earlier in the scenario.
Syncro11

Update a Lead

Action

In Make“Updates a lead specified by ID.”

Update a Lead edits a prospect already in Syncro, chosen by its ID, so the sales pipeline reflects the latest conversation.

When to use it
a prospect books a call through your scheduling tool and the lead in Syncro should carry that news for the salesperson.
Watch out
when the incoming data has no lead ID, look the lead up with Search Leads first.
Syncro12

Update a Ticket

Action

In Make“Updates a ticket specified by ID.”

Update a Ticket changes a ticket in Syncro, picked by its ID, so events that happen outside Syncro move the ticket forward on their own.

When to use it
a payment arrives through Watch New Payments and the ticket that tracked the unpaid invoice should be updated for the team.
Watch out
Watch Ticket fires on updates too, so never place this module in a scenario that starts from Watch Ticket.
Syncro13

Search Customers

Search

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

Search Customers looks through your Syncro clients, or lists them all, and returns zero, one or several bundles. It is how a scenario finds a client when it has no ID yet.

When to use it
right before Create a Customer, to check the client is not already there.
Watch out
several results mean every following module runs once per bundle and uses an operation each time.
Syncro14

Search Leads

Search

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

Search Leads finds prospects in Syncro, or returns the whole list, one bundle per lead. It feeds the modules that need a lead ID.

When to use it
a new contact form entry arrives and you want to know whether that person is already a lead before running Create a Lead.
Watch out
an empty result is a valid answer; plan what happens when no lead matches, or the next module has no ID to work with.
Syncro15

Search Tickets

Search

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

Search Tickets returns matching Syncro tickets, or all of them, as separate bundles, which makes it the starting point for bulk updates and reports.

When to use it
a customer's contract ends and each of their tickets needs a pass through Update a Ticket.
Watch out
listing everything can return many bundles, and each module after it runs once per bundle, which adds up in operations on your plan.
Need help

Need help automating Syncro with Make?

A person reads every message.

FAQ

Syncro Make integration: common questions

01Is the Syncro Make integration free?
Yes. Syncro is a standard app in Make, so its 20 modules are available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution 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 credits each month. Syncro itself still requires its own active account.
02What is needed to connect Syncro to Make?
An active SyncroMSP account and an API token created in it. In Syncro, open Profile/Password from the account menu, go to API Tokens, click New Token, choose the Custom Permissions tab, name the token, pick an expiration date and the permissions your scenarios need, then click Create API Token and copy it. In Make, add a Syncro module, click Create a connection and paste the token. For the instant triggers, click Create a webhook first.
03Do the Syncro triggers in Make work in real time?
Yes. All 5 Syncro triggers are instant: Syncro calls Make through a webhook as soon as a customer, an invoice, a payment, an RMM alert or a ticket event appears, so the scenario does not wait for a polling schedule. In the editor they carry the lightning badge. The step to remember is the setup order: Create a webhook, then Create a connection. Watch Ticket covers three events on its own: creation, update and resolution of a ticket.
04What if a Syncro module is missing in Make?
Use Make an API Call. It ships with the Syncro app and reaches any endpoint of the Syncro API with the connection you already created, so tasks outside the listed modules stay possible, such as editing invoices, which the other modules only watch. You build the request from the Syncro API documentation yourself. The Make documentation for Syncro lists no specific limits, only a notice that it was generated with AI from Syncro's documentation, so confirm important details with Syncro directly.
05Make or n8n for Syncro?
It depends on the tool your team already uses and the way you like to build. On the Make side, Syncro comes with 20 ready modules, including 5 instant triggers and Make an API Call, and the connection only takes an API token. The same app often has an n8n node too, so look at what that node offers before deciding. Try a small scenario in each editor, such as a ticket opened for each new customer, and keep the one your team maintains comfortably.
Same platform

Other docs you might need on this stack.

Browse all integrations