Resources · Make integration

SiteSeam Make integrationAutomate SiteSeam with Make.

Can Make pick up what happens on your SiteSeam website? The SiteSeam Make integration gives you 5 action modules, including Make an API Call. This guide is for site owners new to Make: it links your account, walks through a first scenario and says plainly what the documentation leaves open.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the SiteSeam Make integration let you automate?

The SiteSeam Make integration links your SiteSeam account to Make, a visual tool where you build a scenario (the automation itself, a chain of modules) without writing code. A module is one brick of that chain. SiteSeam brings 5 of them, all listed as actions, so the scenario starts on a schedule or on another app.

The module names tell you where to look: bookings, contact forms, quote requests and newsletter sign-ups on your site. A sales team could run Contact Form Submission on a schedule and send what comes back to its CRM. A service business could do the same with Booking Scheduled to keep a shared calendar in step. A shop that sends quotes could route Instant Quote Submission to whoever prices the job.

Treat those as ideas to check, not promises. The Make documentation for SiteSeam is marked as limited: it gives no field list and no description for any module, so open each one in the editor and test it with Run once before you rely on it. When a listed module does not cover your case, Make an API Call reaches any endpoint of the SiteSeam API with the same connection.

If you are still weighing tools, the n8n vs Make comparison sets out the differences, and the Make pricing page explains how operations are counted. Stuck on a run that fails? See Make troubleshooting.

Connect

How do you connect SiteSeam to Make?

  1. 01

    Add a SiteSeam module

    In a new scenario, click the + and search for SiteSeam. Pick any of its modules, then click Create a connection. A connection is your SiteSeam account linked to Make once and reused by every SiteSeam module.

  2. 02

    Name it and authorize

    Give the connection a name if you like, which helps when you run several sites. Then either approve Make on the SiteSeam page that opens, or paste the key SiteSeam gives you, depending on what the window asks for.

  3. 03

    Save the connection

    Click Save. Make returns to the module, and once the connection works it can list what it is able to read in your SiteSeam account, so you pick values instead of typing them.

First scenario

Your first scenario with SiteSeam

GoalWhen the scenario runs on its schedule, Make runs Contact Form Submission in SiteSeam, then calls the SiteSeam API for the step the listed modules do not cover.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to place the first module. Search for SiteSeam and choose Contact Form Submission.

  2. 02

    Link your account

    Click Create a connection and follow the three steps above. The connection is saved once and every later SiteSeam module reuses it.

  3. 03

    Fill in the module

    Complete the fields Make shows for Contact Form Submission. The documentation does not list them, so read each label in the editor and pick from the values Make offers.

  4. 04

    Add the API call

    Click the + on the right of the first module and add Make an API Call from SiteSeam. Map data from the previous module into it to reach the endpoint you need.

  5. 05

    Test with Run once

    Click Run once. Make executes the scenario one time and shows the bundles each module received, meaning each item passed along. Check they hold what you expected.

  6. 06

    Schedule and switch on

    Click the clock on the first module. A new scenario runs every 15 minutes by default; keep that or change it, then switch the scenario on so it runs without you.

Modules

What the SiteSeam modules do

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

SiteSeam1

Booking Scheduled

ActionIn the docs only

Booking Scheduled is the module to try first if appointments are what matter on your site, since its name points to bookings. Make lists it as an action, and the documentation gives neither a description nor its fields.

When to use it
when the bookings taken on your SiteSeam site need to reach another tool, such as a calendar or a task list.
Watch out
confirm with Run once what the bundle really contains before you map it anywhere.
SiteSeam2

Contact Form Submission

ActionIn the docs only

This module gives your scenario a way into the contact form side of SiteSeam, judging by its name. Make types it as an action; the documentation stays silent on what it returns or which fields it expects, so the editor is your guide.

When to use it
when messages left through your site should end up in a CRM, a help desk or a team inbox.
Watch out
each module run counts as an operation on your Make plan, so keep the schedule sensible.
SiteSeam3

Instant Quote Submission

ActionIn the docs only

Quote requests are the likely subject of Instant Quote Submission, going by its name alone. Despite the word instant, Make lists it as an action and not as an instant trigger, so it will not start a scenario by itself.

When to use it
when the person who prices jobs needs each quote request passed on from your SiteSeam site.
Watch out
place it after a schedule or another app's trigger, never as a way to react the moment a quote arrives.
SiteSeam4

Make an API Call

ActionIn the docs only

Make an API Call lets you reach any endpoint of the SiteSeam API from your scenario, using the connection you already created. It is the safety net for everything the four named modules leave out.

When to use it
when the task you need has no ready-made module, or when a named module does not return what you expected.
Watch out
you need the SiteSeam API documentation for the endpoint and its parameters, since Make does not describe them for this app.
SiteSeam5

Subscribe Form Submission

ActionIn the docs only

Newsletter sign-ups are what Subscribe Form Submission seems built around, based on its name. Make classes it as an action, and nothing in the documentation describes its output yet, so a test run is the quickest way to learn it.

When to use it
when new subscribers from your site belong in an email marketing tool or a mailing sheet.
Watch out
the name does not say whether it reads sign-ups or sends them, so check the direction with Run once first.
Need help

Need help automating SiteSeam with Make?

A person reads every message.

FAQ

SiteSeam and Make: common questions

01Is the SiteSeam Make integration free?
Yes, SiteSeam is a standard app in Make, so you can use it on the Free plan. That plan has limits: 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) lower the interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one per module run on one bundle. This page says nothing about the price of SiteSeam itself.
02What does it take to connect SiteSeam to Make?
A SiteSeam account and a Make account are enough to begin. The Make documentation for SiteSeam lists no prerequisite and no specific steps, so the generic flow applies: add a SiteSeam module, click Create a connection, optionally name it, then either approve Make on the SiteSeam page or paste the key SiteSeam provides, and click Save. The connection is stored once and reused by all 5 SiteSeam modules in every scenario you build afterwards.
03Does the SiteSeam Make integration react in real time?
No. SiteSeam has no trigger module in Make: its 5 modules are all actions, so none of them can start a scenario by itself. You start the flow another way. The simplest is the schedule on the first module, which runs a new scenario every 15 minutes by default, and the Free plan never goes faster than that. The other option is to open the scenario on a trigger from another app, then place the SiteSeam modules after it.
04What if a SiteSeam module is missing in Make?
Use Make an API Call. SiteSeam has this module, and it calls any endpoint of the SiteSeam API with the connection you already set up, so you are not limited to the four named modules. Keep in mind that the Make documentation for SiteSeam is marked as limited: it describes no fields and no module behavior. You will need the SiteSeam API reference to choose the endpoint, and a Run once test to check what comes back before you switch the scenario on.
05Make or n8n for SiteSeam: which fits better?
It depends on where your other automations already live. On the Make side, SiteSeam offers 5 action modules and the Make an API Call fallback, which this page covers. Many apps also have an n8n node, but that is not confirmed here for SiteSeam, so check the n8n node list before you decide. If your team already builds in one of the two tools, staying there avoids running two setups. The n8n vs Make comparison linked above sets out the general differences.