Resources · Make integration

Syda Make integrationAutomate Syda with Make.

Can Make pick up your new Syda jobs and act on them without a line of code? The Syda Make integration gives you 18 modules: one trigger, 10 actions and 7 searches. This guide explains each one in plain words and walks you through a first scenario you can test.

Try the Syda integration on MakeSee the 18 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Syda Make integration do for you?

The Syda Make integration links your Syda account to Make so that jobs, contacts, clients and job reports can move between Syda and your other tools on their own. You build a scenario, which is the automation itself: a chain of modules, each module being one brick such as a trigger, an action or a search.

React to fresh work. Watch New Jobs picks up, at each scheduled check, the jobs Syda did not hold at the previous one. Chain Get a Client behind it and the next tool receives the job together with the client record, so nobody has to open Syda to copy details.

Keep people records clean. Search Contacts looks for someone before anything is written. Found nobody? Create a Contact adds the person. Found them? Update a Contact corrects what changed. That small check prevents duplicates.

Close the loop on field work. Search Job Reports finds the reports you care about and Update a Job Report writes back a change coming from another app, while Update a job adjusts the job itself.

Know the limit before you start: Make's own documentation for Syda is marked as incomplete, because too little public information about the app exists. When a listed module does not reach what you need, Make an API Call uses the same connection to call Syda's API directly. If you are still choosing a platform, read the n8n vs Make comparison, and when a run goes wrong, the Make troubleshooting guide covers the usual causes. Want a guided start? The Make training goes step by step.

Connect

How do you connect your Syda account to Make?

  1. 01

    Add a Syda module

    In a scenario, click the + and search for Syda, then pick any of its modules. Make asks for a connection, meaning your Syda account linked to Make once and reused by every Syda module. Click Create a connection.

  2. 02

    Name the connection

    Giving it a name is optional, yet it helps as soon as you have more than one Syda account or workspace. Pick something you will recognize later, like the team or the environment it belongs to.

  3. 03

    Authorize and save

    Depending on what Syda offers, either approve Make on the Syda page that opens or paste the key Syda gives you. Then click Save. Every other Syda module in your scenarios can now reuse this connection.

First scenario

Your first scenario with Syda

GoalWhen a new job shows up in Syda, Make fetches the client record linked to it so the next module has everything at hand.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the canvas. This first slot always holds the module that starts everything.

  2. 02

    Place Watch New Jobs

    Search for Syda, choose Watch New Jobs and pick your connection, or click Create a connection if this is your first Syda module.

  3. 03

    Add Get a Client

    Click the + on the right of the trigger, add Get a Client and map the client reference from the job bundle, a bundle being one item passed from module to module.

  4. 04

    Test with Run once

    Click Run once, then open the bubbles above each module. You see the bundles each one received, which tells you whether the client lookup matched the job.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and the Free plan cannot go below that. Adjust it, then turn the scenario on.

Triggers

What starts a Syda scenario?

1 module starts a scenario when something happens in Syda. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Syda as soon as it happens.

Syda1Watch New Jobs

Watch New Jobs

triggerIn the docs only

Watch New Jobs hands your scenario every job that has appeared in Syda since the last check, one bundle per job, so later modules can process each one separately.

How it fires
scheduled, Make checks the app on the scenario's schedule. The type comes from the module's name because Make's directory had no entry for Syda, so confirm the clock badge in the editor.
When to use it
when a new job should trigger something elsewhere, such as a message to the team or a record in another tool.
Watch out
on a scheduled trigger, several jobs can arrive in one run, and each one uses operations, the unit Make counts on your plan.
Modules

What can you do with Syda in Make?

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

Syda1

Create a Contact

ActionIn the docs only

You get a new contact person in Syda, filled from data another app just sent, without typing it again.

When to use it
a lead from a web form or a new customer in your billing tool should also exist as a Syda contact.
Watch out
run Search Contacts first, otherwise the same person ends up in Syda twice.
Syda2

Create a Job

ActionIn the docs only

This module opens a fresh job in Syda from outside, so a request captured anywhere turns into work your team can see.

When to use it
an order confirmed in your shop or a ticket accepted in your help desk should become a Syda job.
Watch out
a job created this way is also a new job for Watch New Jobs, so keep both scenarios apart.
Syda3

Get Site

ActionIn the docs only

Get Site returns one site from Syda when you already know which one you want, which saves a search when the reference is in hand.

When to use it
a job bundle points to a site and the next step needs the site details.
Watch out
it needs a precise reference; when you only have a name or a partial clue, Search Sites is the better fit.
Syda4

Get a Client

ActionIn the docs only

You receive the complete client record for a single client whose reference you already hold, ready to map into later modules.

When to use it
right after Watch New Jobs, to add the client's details to a notification or a record in another app.
Watch out
it reads one client only; to browse several, switch to Search Clients.
Syda5

Get a Contact

ActionIn the docs only

Get a Contact loads one contact person from Syda so their details are available to the rest of the scenario.

When to use it
another module gave you the contact's reference and you need their full record before sending an email or updating a CRM.
Watch out
without a reference, start with Search Contacts, which finds candidates first.
Syda6

Get a User

ActionIn the docs only

This one fetches a single Syda user, meaning someone working in your account, so you can tell who a record belongs to.

When to use it
a job points to a user and you want that person's details to route a message to them.
Watch out
users are your team members inside Syda, not your clients' contacts; pick Get a Contact for those.
Syda7

Make an API Call

ActionIn the docs only

Make an API Call lets you reach any endpoint of Syda's API from your scenario, reusing the connection you already created.

When to use it
the action you need is missing from the list above, which can happen since Make's Syda documentation is incomplete.
Watch out
you write the request yourself, so you need Syda's API reference at hand; the rest of this page cannot help with endpoints.
Syda8

Search Clients

SearchIn the docs only

Search Clients looks through your Syda clients and returns what it finds as separate bundles, from none to many.

When to use it
before creating a job for a company, check whether the client already exists in Syda.
Watch out
plan for the case where no client comes back, because the rest of the scenario then has nothing to work on.
Syda9

Search Contacts

SearchIn the docs only

You find out whether a person is already in Syda before writing anything, which keeps your contact list free of copies.

When to use it
in front of Create a Contact or Update a Contact, to decide which of the two should run.
Watch out
several matches mean several bundles, and each one triggers the following modules once.
Syda10

Search Job Reports

SearchIn the docs only

Search Job Reports pulls the reports attached to work done in Syda, each report arriving as its own bundle.

When to use it
you want finished reports copied to a shared drive, a spreadsheet or a message for the account manager.
Watch out
a broad search can return many reports and spend one operation per report on every module downstream.
Syda11

Search Jobs

SearchIn the docs only

This search lists existing Syda jobs, whereas Watch New Jobs only reacts to jobs that just appeared.

When to use it
another app sends an update and you need to locate the matching job before running Update a job.
Watch out
if the search matches more than one job, the update would run on each of them; narrow the search first.
Syda12

Search Services

SearchIn the docs only

Search Services returns the services defined in your Syda account, so a scenario can pick the right one instead of guessing.

When to use it
an incoming request names a type of work and you want the matching Syda service before creating the job.
Watch out
the request may name the service differently from Syda, so check after Run once that the search really returned the one you expect.
Syda13

Search Sites

SearchIn the docs only

With Search Sites you locate the Syda sites that match what your scenario knows, one bundle per site found.

When to use it
a customer gives an address or a site name and you need the Syda site before planning work there.
Watch out
once you hold the exact reference, Get Site is lighter because it returns a single site directly.
Syda14

Search Users

SearchIn the docs only

Search Users finds the people who work in your Syda account, useful whenever a scenario must know who is available or responsible.

When to use it
you want to send a notification to the colleague handling a job, starting from their name or email.
Watch out
searching returns zero, one or several users; add a filter so the message reaches the right person only.
Syda15

Update a Contact

ActionIn the docs only

Your Syda contact stays in step with the tool where the change really happened, without anyone editing it by hand.

When to use it
a contact changes phone or email in your CRM and Syda should follow.
Watch out
it needs the right contact reference, so place Search Contacts or Get a Contact just before it.
Syda16

Update a Job Report

ActionIn the docs only

This module writes changes into an existing job report, so information gathered after the visit lands where it belongs.

When to use it
a customer signs off in another tool and the matching Syda report should reflect that.
Watch out
find the report first with Search Job Reports; an update pointed at the wrong report overwrites real work.
Syda17

Update a job

ActionIn the docs only

Update a job changes a Syda job that already exists, keeping its status and details aligned with what happens outside Syda.

When to use it
a payment clears in your invoicing tool or a customer reschedules by email, and the job should show it.
Watch out
this edits live data, so run it once on a test job before switching the scenario on.
Need help

Need help automating Syda with Make?

A person reads every message.

FAQ

Questions about Syda and Make

01Is the Syda Make integration free?
Yes, Syda is a standard app in Make, so it works from the Free plan onward. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, runs of up to 5 minutes, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow runs of up to 40 minutes. Usage is counted in operations per month, one operation being one module handling one bundle.
02What do you need to connect Syda to Make?
A Syda account and a Make account are the starting point. Make's documentation for Syda lists no prerequisites and no specific steps, so the usual path applies: add a Syda module, click Create a connection, name it if you like, then either approve Make on the Syda page or paste the key Syda provides, and save. The connection is created once and every Syda module reuses it. If it fails, check in Syda which kind of access your account offers.
03Does the Syda trigger in Make react in real time?
No, Watch New Jobs is a scheduled trigger, a type inferred from its name because Make's directory had no entry for Syda. Make checks Syda on the scenario's schedule, every 15 minutes by default, and never faster than every 15 minutes on the Free plan. Paid plans can go down to 1 minute. Each check collects the jobs added since the previous one, so several can arrive together, and nothing is pushed to Make the moment a job is created.
04What if a Syda module is missing in Make?
It depends on what you need, but Make an API Call usually covers it. That module reaches any endpoint of Syda's API through the connection you already set up, so you are not limited to the 18 listed modules. Keep in mind that Make's documentation for Syda is marked as limited because public information about the app is scarce, so have Syda's own API reference open while building the request. For errors during a run, compare the bundles shown after Run once.
05Should you use Make or n8n for Syda?
It depends on the tool your team already runs. On Make, Syda comes with 18 modules, a scheduled trigger for new jobs and Make an API Call for anything else, all available on the Free plan. Many apps also have an n8n node, but this page cannot confirm one for Syda, so check the n8n node list before deciding. Then weigh your existing scenarios, the skills in the team and where your other apps are already connected rather than a general ranking.
Same platform

Other docs you might need on this stack.

Browse all integrations