Resources · Make integration

FaceUp Make integrationAutomate FaceUp with Make.

Could a new FaceUp report reach the right person without anyone refreshing the dashboard? The FaceUp Make integration offers 3 instant triggers: reports, messages and internal comments. This guide shows HR and compliance teams how to connect the account and build a first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the FaceUp Make integration do?

The FaceUp Make integration lets a Make scenario, the automation you build in Make, start the moment something new lands in your FaceUp account. It only listens: a report, a message from a sender or an internal comment wakes the scenario up, and the next modules take care of the rest.

Route every new report. Watch Reports starts the scenario when a report is created. Add a module from your ticketing tool or chat app after it, and the case owner gets a heads-up without watching FaceUp all day.

Keep reporters from waiting. Watch Messages fires when a sender writes into an existing case. A compliance officer who handles several cases can receive each new message in the channel the team already reads.

Log internal discussion. Watch Internal Comments reacts to notes your investigators add. Sending them to a spreadsheet or a project tool gives a trace of who said what, outside FaceUp.

What this app does not do in Make: it has no action or search module, and no Make an API Call module either. Make cannot create a report, answer a sender or change a case status in FaceUp. Any follow-up happens in another app. If you want a second opinion on the tool itself, read the Make review, and the n8n vs Make comparison helps if you are still choosing a platform.

Connect

How do you connect FaceUp to Make?

  1. 01

    Copy your key and region

    In FaceUp, open the Integrations tab, click API keys then Create, and copy the key somewhere safe. Then open the Settings tab and copy the Data Hosting Region value.

  2. 02

    Create the webhook and connection

    In Make, add a FaceUp module to your scenario. All three are instant, so click Create a webhook first, then Create a connection. A connection is your FaceUp account linked to Make once and reused by every FaceUp module.

  3. 03

    Paste the values and save

    Give the connection a name if you like, paste the key into API Key and the region into Region, then click Save. If a window asks you to authenticate or confirm access, accept it.

First scenario

Your first scenario: alert the team on each new FaceUp report

GoalWhen a report is created in FaceUp, Make passes it to the app your team already uses for alerts.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to place the first module, which is where everything starts.

  2. 02

    Add Watch Reports

    Search for FaceUp, pick Watch Reports, create the webhook and link your connection with the key and region copied earlier.

  3. 03

    Add the alert module

    Click the + on the right of Watch Reports and choose the module of your mail or chat app. Map the report data into the message.

  4. 04

    Test with Run once

    Click Run once, then create a test report in FaceUp. Each bundle, one item passed between modules, shows up in the editor so you can check it.

  5. 05

    Switch it on

    When the test looks right, switch the scenario on. Since the trigger is instant, FaceUp calls Make each time a report arrives, with no polling interval to set.

Triggers

What starts a FaceUp scenario

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

FaceUp1Watch Internal Comments

Watch Internal Comments

Instant trigger

In Make“Triggers when a new internal comment is created.”

You get each internal comment your team writes on a case, handed to the next module as soon as it exists. That keeps investigators in sync even when some of them never open FaceUp between two meetings.

How it fires
instant, FaceUp calls Make through a webhook as soon as the comment is created.
When to use it
a legal advisor needs to see every note added by HR on sensitive cases, in the tool they already work in.
Watch out
internal comments are private by nature, so send them only to a destination with the same restricted access.
FaceUp2Watch Messages

Watch Messages

Instant trigger

In Make“Triggers when a new message from a sender is created.”

This trigger brings you every new message a sender writes, so a reply from a whistleblower never sits unread. It is the one to pick when the conversation matters more than the initial report.

How it fires
instant, FaceUp notifies Make through a webhook the moment the message is created.
When to use it
a case manager asked a reporter for more details and wants a ping in the team chat when the answer comes in.
Watch out
it covers messages from senders; notes written by your own team come through Watch Internal Comments instead.
FaceUp3Watch Reports

Watch Reports

Instant trigger

In Make“Triggers when a new report is created.”

Watch Reports gives you each brand new report the second it lands, which makes it the natural first module for any intake flow.

How it fires
instant, FaceUp calls Make through a webhook as soon as the report is created.
When to use it
an ethics committee wants a ticket opened, or a lead notified, for every incoming report.
Watch out
it reacts to new reports only, so later messages on the same case need Watch Messages in a separate scenario.
Need help

Need help automating FaceUp with Make?

A person reads every message.

FAQ

FaceUp and Make: common questions

01Is the FaceUp Make integration free?
Yes, on the Make side. FaceUp is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs of 5 minutes at most, files up to 5 MB and 512 MB of data transfer. Each operation, meaning one module run on one bundle, counts toward your plan. Paid plans (Core, Pro, Teams, Enterprise) remove the active scenario cap and extend runs to 40 minutes. You still need a FaceUp account, whose subscription is set by FaceUp itself.
02What do you need to connect FaceUp to Make?
A FaceUp account, an API key and your data hosting region. Create the key in FaceUp from the Integrations tab, under API keys then Create, and copy the Data Hosting Region value from the Settings tab. In Make, add a FaceUp module, click Create a webhook, then Create a connection, and paste both values into the API Key and Region fields before clicking Save. Accept the authentication prompt if one appears.
03Does the FaceUp trigger react in real time?
Yes. All three FaceUp triggers are instant: FaceUp calls Make through a webhook as soon as a report, a message or an internal comment is created. There is no polling interval to wait for, unlike scheduled triggers that Make checks every 15 minutes by default. This is why each FaceUp module asks you to create a webhook before the connection. Once the scenario is switched on, it runs every time the event happens.
04What if a FaceUp module you need is missing in Make?
It depends on what you need. The FaceUp app in Make only watches events: it cannot create, update or search anything, and it has no Make an API Call module to fill the gap. For the follow-up, chain a module from another app after the FaceUp trigger, such as your ticketing, mail or spreadsheet tool. If the process needs more than that, the team behind this page can look at your case and suggest a setup.
05Make or n8n for FaceUp?
It depends on your criteria. On Make, FaceUp brings three instant triggers and no actions, so the platform question comes down to where the rest of your flow lives and which editor your team is comfortable with. Before switching, check whether n8n has a FaceUp node and what it covers, because this page only documents the Make side. The n8n vs Make comparison linked above sets out the general differences without taking sides.