Resources · Make integration

Site Search 360 Make integrationAutomate Site Search 360 with Make.

Keep your site search index in step with your content, without copying pages by hand. The Site Search 360 Make integration gives you 2 action modules. This page shows how to link your API key, build a first scenario and test it before you switch it on.

Try the Site Search 360 integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Site Search 360 Make integration let you do?

The Site Search 360 Make integration links your Site Search 360 account to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick that does one job. Here you get two action modules, Index Document and Indexing Progress, and no trigger of their own.

Push fresh content into search. When another app signals new content, such as a form entry or a published page, Index Document is the module whose name points to adding that item to your Site Search 360 index. The official documentation gives no description for it, so read the fields Make shows once your connection is set.

Follow a large indexing job. After a batch of Index Document runs, Indexing Progress is the natural next brick to look at how the work is going. Again, its exact output is not documented, so a first test with Run once tells you what comes back.

Start from any other app. Since Site Search 360 cannot start a scenario itself, the first module belongs to another tool you use, or you let Make run the scenario on its schedule. The Make review walks through how the editor behaves if you are new to it.

What Make does not give you here: no trigger, and no universal Make an API Call module for this app. Make also notes that its documentation page for Site Search 360 is AI-generated and may contain mistakes, so double-check anything important with the vendor. If you are weighing tools, the n8n vs Make comparison sets the two side by side, and the Make pricing page covers plans.

Connect

How do you connect Site Search 360 to Make?

  1. 01

    Generate your API key

    Log in to Site Search 360 and open your account dashboard. Go to the API Access tab, click Generate if no key exists yet, then copy the key shown on screen. Your account needs API access enabled.

  2. 02

    Open the connection window

    In your Make scenario, add a Site Search 360 module and click Create a connection. A connection is your Site Search 360 account linked to Make once, then reused by both modules of the app.

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you like, it is optional. Paste the API key you copied, or follow the instructions Make displays, and confirm. The module is now ready to fill.

First scenario

Your first scenario with Site Search 360

GoalWhen new content shows up in another app, Make sends it to Site Search 360 with Index Document and then checks the job with Indexing Progress.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where your new content appears, since Site Search 360 has no trigger.

  2. 02

    Add Index Document

    Click the + to the right of that first module, search for Site Search 360 and choose Index Document. Click Create a connection and paste your API key.

  3. 03

    Map the content

    Fill the fields of Index Document with data from the first module. Each bundle, meaning one item passed along, such as one page, becomes one document to send.

  4. 04

    Add Indexing Progress

    Click the + again and add Indexing Progress with the same connection. It sits last in the flow so you can see where the indexing stands after the send.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, which is the easiest way to learn what both modules return.

  6. 06

    Schedule and switch on

    Open 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.

Modules

What the Site Search 360 modules do

Site Search 360 gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Site Search 3601

Index Document

ActionIn the docs only

This action gets new or updated content into your Site Search 360 index, going by the module name, so visitors can find it through your site search. Make lists no official description, so check its fields after connecting.

When to use it
right after the module of another app that hands over a new page, article or product.
Watch out
each document sent is one operation, the unit Make counts on your plan, so a long list costs one operation per item.
Site Search 3602

Indexing Progress

ActionIn the docs only

Use this action to see how far indexing has gone on your Site Search 360 account, going by its name, instead of opening the dashboard. The documentation says nothing more, so run it once to read what it returns.

When to use it
after a batch of Index Document runs, to confirm the work moved forward.
Watch out
it is an action, not a trigger, so it never starts a scenario on its own.
Need help

Need help automating Site Search 360 with Make?

A person reads every message.

FAQ

Site Search 360 and Make: common questions

01Is the Site Search 360 Make integration free?
Yes, on the Make side. Site Search 360 is a standard app, so you can use it from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, 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 and remove the cap on active scenarios. Your Site Search 360 subscription is separate: check the vendor's pricing page for an account with API access.
02What do you need to connect Site Search 360 to Make?
An active Site Search 360 account with API access enabled, plus an API key. You find it in your account dashboard under the API Access tab, where the Generate button creates one if none exists. In Make, add a Site Search 360 module, click Create a connection, optionally name it in Connection name, then paste the key. The same connection then serves both modules, Index Document and Indexing Progress, so you only do this once.
03Can Site Search 360 start a Make scenario in real time?
No. The app has no trigger module, scheduled or instant, so it cannot start a scenario by itself. Two ways around that. Put a trigger from another app first, the one where your content changes, and place Index Document right after it. Or leave the first slot to Make's own schedule, which runs a new scenario every 15 minutes by default, with 1 minute as the shortest interval on paid plans and 15 minutes on Free.
04What if a Site Search 360 module is missing in Make?
Then Make alone will not cover it. This app has only two modules and no Make an API Call module, the universal module some apps offer for calls outside the list. You can check whether another app in your stack covers the need, or ask for help building the scenario. Keep in mind that Make flags its Site Search 360 documentation as AI-generated and possibly wrong, so confirm important details with Site Search 360 directly.
05Should you use Make or n8n for Site Search 360?
It depends on your setup, not on a ranking. On Make, you get two action modules, Index Document and Indexing Progress, a connection by API key, and access from the Free plan, but no trigger and no Make an API Call module. The same app often has an n8n node too, so check that list before you choose. If the rest of your scenarios already live in Make, adding these two modules there keeps everything in one place.
Same platform

Other docs you might need on this stack.

Browse all integrations