Resources · Make integration

Siteglide Make integrationAutomate Siteglide with Make.

What can Make actually do with your Siteglide site? The Siteglide Make integration gives you 14 modules: 7 triggers that watch CRM users, form cases, WebApp items and eCommerce records, plus actions and searches. This guide links your account and walks you through a first scenario.

Try the Siteglide integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Siteglide Make integration let you automate?

The Siteglide Make integration links your Siteglide site to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, creates, finds or updates something. Siteglide brings 14 of those bricks, centered on CRM users, WebApp items, form cases and eCommerce records.

Every web order reaches the rest of your stack. Watch New eCommerce Order hands each new order to Make, and the next module can pass it to your accounting tool, a team chat or a spreadsheet. A shop manager stops copying orders by hand.

Leads from other tools land in your Siteglide CRM. A contact captured elsewhere can become a record through Create a CRM User, and when that person already exists, Find an Individual CRM User followed by Update a CRM User keeps one clean profile instead of duplicates.

Content edits follow a review path. Watch Updated WebApp Item notices changes to WebApp items, the structured content of a Siteglide site, so an editor can be told, or a copy can be written to another system.

Know one limit before you start: Make itself flags its Siteglide documentation as limited, because little public information exists about the app. Expect to test each module with Run once and read what comes back. The Make troubleshooting guide helps when a run fails.

Still choosing a platform? The same app often has an n8n node as well, and the n8n vs Make comparison lays out the criteria. For a wider look at the tool, read our Make review.

Connect

How do you connect your Siteglide account to Make?

  1. 01

    Open the connection window

    Add any Siteglide module to your scenario, then click Create a connection. A connection is your Siteglide account linked to Make once, and every Siteglide module of your scenarios reuses it afterwards.

  2. 02

    Name the connection

    This step is optional, but a clear name such as the site it points to saves confusion later, especially if you manage several Siteglide sites and need to pick the right account from a list.

  3. 03

    Authorize Make and save

    Depending on what the window asks, approve access on the Siteglide page or paste the key Siteglide gives you. Then click Save, and Make can start listing what it is allowed to read.

First scenario

Build your first scenario with Siteglide

GoalWhen a visitor sends a form on your Siteglide site, Make turns that form case into a CRM user.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the big + in the middle of the editor to place your first module.

  2. 02

    Add the form trigger

    Search for Siteglide, choose Watch New Form Case and click Create a connection if this is your first Siteglide module. Fill in what the module asks for.

  3. 03

    Add Create a CRM User

    Click the + to the right of the trigger, pick Create a CRM User and map the values from the form case into its fields, with data coming from the previous module.

  4. 04

    Test with Run once

    Send a test form on your site, then click Run once. Open each module's bubble to read the bundle it received, meaning the single item that moved through the flow.

  5. 05

    Schedule and switch it on

    Click the clock on the first module to set the schedule, which is every 15 minutes by default, then turn the scenario on so it keeps working without you.

Triggers

Which Siteglide triggers can start a scenario?

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

Siteglide1Watch New CRM User

Watch New CRM User

triggerIn the docs only

This trigger hands Make every CRM user added to your Siteglide site, one bundle per person, so a new sign-up can kick off a welcome sequence or a sync to your email tool without anyone copying names across.

How it fires
scheduled: Make checks the app on the scenario's schedule, so new users show up at the next check rather than the second they register.
When to use it
when the moment a person enters your CRM is what should start the work.
Watch out
it only sees new users; edits to an existing profile belong to Watch Updated CRM User.
Siteglide2Watch New Form Case

Watch New Form Case

triggerIn the docs only

You get each new form case from your site as its own bundle, which makes it the natural starting point for routing a quote request, a support question or a registration to the right person or tool.

How it fires
scheduled: Make checks the app on the scenario's schedule, so a submission waits for the next check before the scenario picks it up.
When to use it
when the form itself is the event, whatever happens to the sender's CRM record afterwards.
Watch out
Make's Siteglide documentation is limited, so send one test form and read the bundle before mapping anything.
Siteglide3Watch New WebApp Item

Watch New WebApp Item

triggerIn the docs only

Publishing a new WebApp item, such as a listing, an article or an event entry, can now start a scenario that announces it, archives it or copies it somewhere your team already looks.

How it fires
scheduled: Make checks the app on the scenario's schedule and returns the items created since its previous look.
When to use it
when a fresh item on the site needs a follow-up outside Siteglide, like a post in the team chat.
Watch out
changes to items that already exist will not appear here; pair it with Watch Updated WebApp Item if edits matter to you.
Siteglide4Watch New eCommerce Order

Watch New eCommerce Order

triggerIn the docs only

Each order placed in your Siteglide shop arrives in Make as a bundle, ready to feed invoicing, fulfillment notes or a sales dashboard, so the order record no longer lives only inside the site admin.

How it fires
scheduled: Make checks the app on the scenario's schedule, so orders are collected at each check, not pushed the moment a customer pays.
When to use it
when a sale should reach another tool without a person exporting it.
Watch out
on the Free plan the shortest gap between two checks is 15 minutes, which matters if your warehouse expects faster handoffs.
Siteglide5Watch New eCommerce Product

Watch New eCommerce Product

triggerIn the docs only

Adding a product to your catalog can trigger the chores that usually follow it: telling the sales team, logging it in an inventory sheet or preparing a social post, with each new product delivered as one bundle.

How it fires
scheduled: Make checks the app on the scenario's schedule and collects the products added since the last check.
When to use it
when a catalog addition should reach people or tools that never open the Siteglide admin.
Watch out
it reacts to new products only, so a price or stock change on an existing product will not wake it up.
Siteglide6Watch Updated CRM User

Watch Updated CRM User

triggerIn the docs only

When a CRM user's profile changes, this trigger passes the updated record to Make at its next check, which lets you keep a mailing list, a helpdesk or a spreadsheet aligned with what Siteglide holds.

How it fires
scheduled: Make checks the app on the scenario's schedule and returns the users edited since its previous look.
When to use it
when another system keeps a copy of your contacts and must not drift out of date.
Watch out
if the next module writes back to the same CRM user, you can create an endless cycle of edits; send updates outward only.
Siteglide7Watch Updated WebApp Item

Watch Updated WebApp Item

triggerIn the docs only

Edits to WebApp items reach Make here, so a revised listing or a corrected event page can trigger a review message, a change log or a sync to another content store.

How it fires
scheduled: Make checks the app on the scenario's schedule, catching the items modified between two checks.
When to use it
when someone outside the site needs to know that published content moved, not just that it appeared.
Watch out
avoid ending the scenario with Update a WebApp Item on the same item, or the next check will likely catch your own edit and run again.
Modules

What can Siteglide do inside a scenario?

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

Siteglide1

Create a CRM User

ActionIn the docs only

This action adds a new person to your Siteglide CRM from data that came from somewhere else, such as a webinar tool or a spreadsheet, so contacts no longer need retyping.

When to use it
when you are sure the person is new, for instance right after a first-time sign-up elsewhere.
Watch out
if the contact may already exist, run Find an Individual CRM User first to avoid a duplicate.
Siteglide2

Create a WebApp Item

ActionIn the docs only

Pushes a fresh entry into one of your WebApps, which turns content prepared in a form, a sheet or a project tool into a live item on the site without a copy and paste session.

When to use it
when entries are drafted outside Siteglide, like job offers or events planned in a spreadsheet.
Watch out
run it once on a test WebApp first, since the documentation does not detail its fields.
Siteglide3

Find an Individual CRM User

SearchIn the docs only

Looks up a person already stored in your CRM and returns what it finds, which gives later modules the record they need to update or reference.

When to use it
before any create or update, when the incoming data might describe someone Siteglide already knows.
Watch out
a search can return zero, one or several bundles, so plan what the scenario does when nothing matches.
Siteglide4

Find an Individual WebApp Item

SearchIn the docs only

Retrieves an existing WebApp item so the scenario can read its content or hand it to Update a WebApp Item, instead of guessing which entry to change.

When to use it
when an outside event, such as a sold-out booking, should alter a specific listing on your site.
Watch out
like every search, it may return no bundle at all; add a filter so the next module is skipped in that case.
Siteglide5

Make an API Call

ActionIn the docs only

Reaches any endpoint of the Siteglide API with the connection you already set up, covering what the listed modules do not, whatever that endpoint does.

When to use it
when none of the listed Siteglide modules does the job you need, and you know the endpoint that would.
Watch out
you need to know which endpoint to call, and Make's Siteglide documentation will not tell you, so keep the API reference of Siteglide at hand.
Siteglide6

Update a CRM User

ActionIn the docs only

Changes the details of a person already in your CRM, so a new phone number captured by your helpdesk or a status set in your billing tool shows up in Siteglide too.

When to use it
after Find an Individual CRM User has located the right record.
Watch out
if the same scenario starts with Watch Updated CRM User, the next check will likely pick up your own update and loop.
Siteglide7

Update a WebApp Item

ActionIn the docs only

Edits an existing WebApp item, keeping a listing, a price note or an availability flag on your site in line with the tool where that information really changes.

When to use it
when a source outside Siteglide owns the truth and the site should simply reflect it.
Watch out
pair it with Find an Individual WebApp Item so you edit the intended entry and not a random one.
Need help

Need help automating Siteglide with Make?

A person reads every message.

FAQ

Siteglide and Make: common questions

01Is the Siteglide Make integration free?
Yes, Siteglide is a standard app in Make, so it works on the Free plan. That plan has limits you will feel quickly: 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 gap between runs to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, meaning one module handling one bundle.
02What do you need to connect Siteglide to Make?
A Siteglide account with access to the site you want to automate and a Make account. The documentation lists no other prerequisite and no dedicated steps, so the usual Make flow applies: add a Siteglide module, click Create a connection, give it a name if you like, approve access on the Siteglide page or paste the key the app provides, then click Save. Because Make marks its Siteglide documentation as limited, test the connection with a first Run once before building anything larger.
03Do Siteglide triggers in Make fire in real time?
No. All 7 Siteglide triggers are scheduled: Make checks Siteglide on the scenario's schedule instead of being called the instant something happens. A new scenario checks every 15 minutes by default, which is also the shortest gap allowed on the Free plan. On a paid plan you can bring that down to 1 minute. Note that the trigger type here comes from the module names, since Make's Siteglide documentation is limited, so check the clock badge on the module in your editor.
04What if a Siteglide module you need is missing in Make?
Use Make an API Call. This module can reach any endpoint of the Siteglide API with the same connection as the other modules, so you are not stuck with the 14 listed ones. The catch is knowledge rather than access: Make's Siteglide documentation is limited, so you will need Siteglide's own API reference to know which endpoint and which data to send. Test every call with Run once before switching the scenario on.
05Should you use Make or n8n with Siteglide?
It depends on the tool your team already runs. On Make, Siteglide offers 14 modules, including 7 scheduled triggers and Make an API Call for the rest, and it works on the Free plan within that plan's limits. The same app often has an n8n node too, so check the n8n side before deciding. Neither choice is universally better: pick the platform where your other automations live, and compare the modules each one offers for Siteglide.
Same platform

Other docs you might need on this stack.

Browse all integrations