Resources · Make integration

BrideScan Make integrationAutomate BrideScan with Make.

Can Make pick up your BrideScan purchases without any code? The BrideScan Make integration gives you 4 modules: one trigger, two actions and one search. This guide shows each one in plain words, links your account and walks you through a first scenario.

Try the BrideScan integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the BrideScan Make integration do?

The BrideScan Make integration links your BrideScan account to Make, a visual tool where you build a scenario: an automation made of modules, where each module is one brick such as a trigger, an action or a search. With it, new BrideScan purchases can start a chain of steps without any code.

React to each sale. Watch for New Purchases gives your scenario a starting point. Every purchase it finds becomes a bundle, meaning one item passed to the next module, so you can send it to a sheet, a CRM or a chat app from another Make integration such as 2Chat Make integration.

Pull the list of events. List Events is a search module: it can return zero, one or many bundles. Place it after the trigger or on its own when a later step needs that list.

Keep the account side tidy. Two actions, Request a BrideScan API Key and Update Account Info, act on the account itself, so account changes can live in the same scenario as the rest of your process.

Know the limits before you start. Make's own documentation for BrideScan is marked as limited, because little public information exists about the app. The module names are known, the fields are not described there, so test every module with Run once and read what it returns. Many apps also have an n8n node; if you are weighing both tools, the n8n vs Make comparison lays out the criteria, and Make pricing explains how operations are counted.

Connect

How do you connect BrideScan to Make?

  1. 01

    Add a BrideScan module

    In your scenario, click the + and search for BrideScan, then pick any of its modules. A connection is your BrideScan account linked to Make once; every BrideScan module reuses it afterwards. Click Create a connection to start.

  2. 02

    Name it and authorize

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

  3. 03

    Save and reuse

    Click Save. The connection now shows up in the dropdown of every BrideScan module, so the next module you add only needs you to pick it from the list instead of signing in again.

First scenario

Build your first scenario with BrideScan

GoalWhen a new purchase shows up in BrideScan, Make pulls the list of events in the same run, so your next steps have both at hand.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to add the first module. That first module decides when everything else runs.

  2. 02

    Add the purchase trigger

    Search for BrideScan and pick Watch for New Purchases. Click Create a connection if this is your first BrideScan module, then fill the fields Make shows for it.

  3. 03

    Add List Events

    Click the + on the right of the trigger and choose List Events. Map any value you need from the purchase bundle the trigger sends into the fields of this second module.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time; open the bubbles above each module to read the bundles it received and check that the purchase and the events look right.

  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. Pick your interval, then switch the scenario on.

Triggers

What triggers can start a BrideScan scenario?

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

BrideScan1Watch for New Purchases

Watch for New Purchases

triggerIn the docs only

This trigger hands your scenario each new BrideScan purchase as a bundle, so every sale can start the same follow-up without you copying anything by hand. Its scheduled type is inferred from its name, since the directory did not describe it.

How it fires
scheduled, which means Make checks the app on the scenario's schedule, every 15 minutes by default, and picks up what arrived since the last check.
When to use it
any time a purchase should lead to a record elsewhere, like a row in a sheet or a note in your CRM.
Watch out
it is not instant, so a purchase appears in your scenario only at the next scheduled check.
Modules

What can BrideScan do in a Make scenario?

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

BrideScan1

List Events

SearchIn the docs only

List Events brings back BrideScan events so the steps that follow can work on them, one bundle per event. As a search module, it may return nothing, a single item or several.

When to use it
after the purchase trigger, or on its own, when a later step needs the list of events.
Watch out
each returned event runs the next modules again and counts as operations, so check the result with Run once.
BrideScan2

Request a BrideScan API Key

ActionIn the docs only

This action asks BrideScan for an API key from inside a scenario, which saves a trip to the app when a key is part of your process. What the response contains is not documented, so read it in the bundle after a test.

When to use it
when a key request belongs to a sequence you already run in Make.
Watch out
treat the key as a secret and only map it into modules that really need it.
BrideScan3

Update Account Info

ActionIn the docs only

Update Account Info changes the details of your BrideScan account from Make, so an edit made elsewhere reaches BrideScan without a manual copy. It acts on one account at a time.

When to use it
when account details change in another tool and BrideScan should follow.
Watch out
the fields it accepts are not described in the docs; test it with Run once on a value you can easily restore.
Need help

Need help automating BrideScan with Make?

A person reads every message.

FAQ

BrideScan and Make: common questions

01Is the BrideScan Make integration free?
Yes, BrideScan is a standard app, so it is available on Make's Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, up to 5 minutes per execution, 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 40 minutes per execution. Usage is counted in operations, one per module per bundle. Any BrideScan subscription of its own is a separate matter this page does not cover.
02What is needed to connect BrideScan to Make?
A BrideScan account and a Make account are the base. Make's documentation lists no specific prerequisite for BrideScan and gives no official connection steps, so the generic path applies: add a BrideScan module, click Create a connection, optionally name it, then either authorize Make on the BrideScan page or paste the key BrideScan provides, and click Save. The connection is then reused by all four BrideScan modules. If the window asks for a value you cannot find, look for it in your BrideScan account settings.
03Does the BrideScan trigger in Make work in real time?
No. Watch for New Purchases is a scheduled trigger, based on its name, since the directory entry was unavailable. Make checks BrideScan on the scenario's schedule, which is every 15 minutes by default for a new scenario. On the Free plan the interval cannot go below 15 minutes; on paid plans it can go down to 1 minute. There is no instant BrideScan trigger listed, so a purchase reaches your scenario at the next check rather than the moment it happens. Plan your follow-up steps with that gap in mind.
04What if a BrideScan module is missing in Make?
It depends on what is missing. BrideScan offers 4 modules in Make and no Make an API Call module, so there is no generic way to reach other parts of the BrideScan API from the editor. Make's own documentation for BrideScan is also flagged as limited, with few details on fields. If your process needs something the four modules do not cover, another app in Make may hold the data you need, or the Hack'celeration team can look at your case and suggest a workaround before you build around a gap.
05Should BrideScan users pick Make or n8n?
It depends on your criteria rather than on a ranking. Make gives BrideScan 4 ready modules, including a scheduled purchase trigger, and a visual editor where you test with Run once before switching a scenario on. The same app may also have an n8n node, in which case both tools are worth checking. Compare the modules each tool offers for BrideScan against the steps you actually need, and the way each one counts usage. This page does not claim one is faster or cheaper for this app.
Same platform

Other docs you might need on this stack.

Browse all integrations