Resources · Make integration

BlueLink Make integrationAutomate BlueLink with Make.

Tired of copying applicant details into BlueLink by hand? The BlueLink Make integration gives you 13 action modules that create records, save quotes and fetch documents. This guide shows how to connect your account and build a first working scenario.

Try the BlueLink integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the BlueLink Make integration do for you?

The BlueLink Make integration lets Make write into BlueLink and read from it for you. Make is a visual automation tool: you chain bricks called modules into a scenario, and data from another app lands in BlueLink without anyone retyping it. BlueLink brings 13 action modules and no trigger, so another app or a schedule starts the flow.

Open a complete file from a single form. A web form collects an applicant, then Create Applicants Object, Create Address Object and Create Income Object build the matching records in BlueLink, one after the other. Your team opens a file that is already filled in.

Keep the history next to the file. When something changes in your CRM or your inbox, Create Case Note writes the update into BlueLink, so the next person on the file reads the context instead of asking for it.

Send documents where people actually work. Get documents metadata from quote lists what a quote holds, and Get Document pulls a single file so another module can store or share it.

What Make will not do here: BlueLink has no trigger, so it never tells Make that something happened on its side, and the app has no Make an API Call module to reach what the 13 modules leave out. The Make doc for BlueLink also warns that it was AI-generated and may contain mistakes. If you want to compare tools before you start, read n8n vs Make, and if a scenario stalls, Make troubleshooting covers the usual errors.

Connect

How do you connect BlueLink to Make?

  1. 01

    Add a BlueLink module

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

  2. 02

    Give the connection a name

    The Connection name field is optional. A clear name still helps the day you run a test account next to the live one, because you will pick it from a list in every new BlueLink module.

  3. 03

    Paste your credentials

    Enter the credentials from your BlueLink account, or follow the instructions Make shows on screen. The doc sends you to the Hyundai Developers service console: open your project, go to Project Overview, then copy the Client ID and the Client secret.

First scenario

Your first scenario with BlueLink and Make

GoalWhen a new applicant shows up in another app, Make creates the applicant in BlueLink and adds a case note to the file.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + on the empty canvas. A scenario is the automation itself: a chain of modules that runs on a schedule or when an app calls Make.

  2. 02

    Start from the app that holds the applicant

    BlueLink has no trigger, so the first module belongs to another app: the form, CRM or spreadsheet where new applicants appear first. Pick its trigger and create that connection.

  3. 03

    Add Create Applicants Object

    Click the + on the right of the first module, search BlueLink and choose Create Applicants Object. Select your BlueLink connection, then map the applicant details from the first module into the fields Make displays.

  4. 04

    Add Create Case Note

    Add Create Case Note next and map a short summary of where the applicant came from. Each bundle, meaning one item passed from a module to the next, now gives one applicant and one note.

  5. 05

    Test with Run once, then switch it on

    Click Run once and open each module bubble to read the bundles it received. Once the result is right, set the schedule on the first module (every 15 minutes by default) and switch the scenario on.

Modules

What each BlueLink module does

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

BlueLink1

Create Address Object

ActionIn the docs only

This module writes an address into BlueLink from data your scenario already carries, so nobody retypes it from an email or a PDF.

When to use it
right after the applicant exists, when the address comes from the same form submission and belongs in the same file.
Watch out
the doc gives no description of this module, so check with Run once which fields BlueLink expects.
BlueLink2

Create Applicants Object

ActionIn the docs only

Here is the starting point of most BlueLink scenarios: the applicant record gets created from another app, and every later module can hang its data on it.

When to use it
as the first BlueLink module after a form, a CRM entry or a spreadsheet row announces someone new.
Watch out
without a trigger in BlueLink, duplicates depend on the app upstream, so make sure it only fires on genuinely new entries.
BlueLink3

Create Case Note

ActionIn the docs only

A case note keeps the story of a file inside BlueLink, written automatically when something happens elsewhere, so colleagues read context instead of chasing it by email.

When to use it
at the end of a scenario, to record what Make just did or what changed in another tool.
Watch out
each bundle creates its own note, so a module upstream that returns many items will write many notes.
BlueLink4

Create Committed Monthly Expenditure Object

ActionIn the docs only

Monthly commitments reach BlueLink through this module, copied from wherever you first collect them, which spares the team a tedious re-entry step.

When to use it
when your intake form or spreadsheet has a section on regular outgoings and the applicant already exists in BlueLink.
Watch out
the doc is silent on the expected fields, so run the scenario once with one real record and inspect what comes back before you scale it.
BlueLink5

Create Fund Object

ActionIn the docs only

Fund details land in BlueLink as their own record with this module, fed by the tool where the information was first captured.

When to use it
when a file needs its funding details stored separately from the applicant, and those details already sit in a form or a sheet.
Watch out
the Make doc does not explain what a fund object contains, so confirm the meaning of each field with BlueLink before mapping it.
BlueLink6

Create Income Object

ActionIn the docs only

Income information goes straight into BlueLink through this module, so the figures the applicant typed once do not have to be typed again by your team.

When to use it
in the same run as Create Applicants Object, placed after it, when the form asks for income in the same submission.
Watch out
an applicant with several income sources may arrive as several bundles, and each one becomes a separate operation that counts on your plan.
BlueLink7

Create Occupant

ActionIn the docs only

Occupant records reach BlueLink through this module, filled from your form or your CRM, instead of being typed by hand inside BlueLink.

When to use it
when your intake form collects occupant details and each occupant should exist as a separate record.
Watch out
if the names arrive as one list in a single field, you need to split them into separate bundles before this module.
BlueLink8

Get Document

ActionIn the docs only

Pull one document out of BlueLink with this module and pass it to another app, for example a shared drive or an email sent to the client.

When to use it
after Get documents metadata from quote, once you know which document you want to move.
Watch out
the Free plan caps files at 5 MB, which matters as soon as you move large scans.
BlueLink9

Get documents metadata from quote

ActionIn the docs only

Before moving any file, this module tells you which documents are attached to a quote, so the rest of the scenario knows what to fetch.

When to use it
when a quote is saved and you want its paperwork copied to another tool without opening BlueLink.
Watch out
a quote can hold several documents, so read the output with Run once before adding Get Document behind it.
BlueLink10

Request DIP

ActionIn the docs only

This module sends a DIP request from your scenario, so the request goes out as soon as the file is complete rather than when someone remembers to click.

When to use it
at the end of a scenario that has already created the applicant and the related records.
Watch out
the doc does not spell out the acronym or what BlueLink returns, so test it on a sample file first.
BlueLink11

Save Experian Open Banking Payload

ActionIn the docs only

Store an Experian Open Banking payload in BlueLink with this module, so data that arrives from another step lands in the right file without a manual upload.

When to use it
when an earlier module or another app in your scenario already hands you that payload.
Watch out
the Make doc says nothing about the payload's format, so check with BlueLink what it accepts before building around it.
BlueLink12

Save UK Quote

ActionIn the docs only

A UK quote gets recorded in BlueLink by this module, built from the answers your scenario gathered upstream, so the quote exists without anyone rebuilding it.

When to use it
once the applicant data is in place and your team wants the quote attached to the same file.
Watch out
the doc does not describe this module, so its role here is read from its name; check with Run once what BlueLink records.
BlueLink13

Submit Application

ActionIn the docs only

This is the last step of a file: the module submits the application in BlueLink once every record the scenario created is in place.

When to use it
as the final module, once the scenario has created every record the application needs.
Watch out
the doc does not say what happens after a submission, so try it with Run once on a dummy applicant before you switch the scenario on.
Need help

Need help automating BlueLink with Make?

A person reads every message.

FAQ

BlueLink and Make: common questions

01Is the BlueLink Make integration free?
Yes on the Make side. BlueLink is a standard app, so its modules work from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run, with usage counted in operations each month. Your BlueLink account is a separate matter: the doc points to the BlueLink pricing page for the subscription.
02What do you need to connect BlueLink to Make?
You need an active BlueLink account with valid credentials, as the Make doc states. Then add any BlueLink module, click Create a connection, optionally fill Connection name, and enter the credentials from your account or follow the instructions on screen. For the advanced setup, the doc describes the Hyundai Developers service console: open your project, go to Project Overview, and copy the Client ID and the Client secret. Since the doc warns it was AI-generated, confirm any unclear step with BlueLink support.
03Does BlueLink trigger Make scenarios in real time?
No. BlueLink has no trigger module at all, so it never notifies Make on its own. You still have two ways to start a scenario. The first is a trigger from another app, such as the form or CRM where your applicants come from; if that app offers an instant trigger, it calls Make through a webhook as soon as something happens. The second is the schedule on the first module, every 15 minutes by default, which you can tighten to 1 minute on a paid plan.
04What if a BlueLink module is missing in Make?
Then Make alone cannot fill the gap for BlueLink. The app has no Make an API Call module, the universal module that some apps offer for reaching endpoints outside their ready-made list. Your options are to work with the 13 existing modules, to move part of the job to another app that already holds the data, or to ask an automation team to review the case. Also keep in mind that the Make doc for BlueLink says it may contain mistakes, so a module that seems off is worth checking with BlueLink.
05Should you use Make or n8n for BlueLink?
It depends on what you need to build. Make gives you 13 ready BlueLink modules in a visual editor, a Run once button to test and a Free plan to start with, which suits a team that wants a first scenario quickly. Before choosing n8n, check whether it offers a BlueLink node and whether that node covers the actions you need, such as quotes, documents and applications. Base the choice on those modules and on where your other apps already run, not on general claims.
Same platform

Other docs you might need on this stack.

Browse all integrations