Resources · Zapier integration

FaceUp Zapier integrationAutomate FaceUp with Zapier.

The FaceUp Zapier integration gives you 3 triggers, 0 actions and 0 searches. FaceUp can start a Zap when a report, a message or an internal comment lands, and all three fire instantly. Zapier cannot write anything back into FaceUp.

See the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the FaceUp Zapier integration does for your case handling

FaceUp is a whistleblowing platform and ethics hotline that HR and compliance teams use to collect reports. Connected to Zapier, it becomes a starting point: each new report, message or internal comment can push a notice into the tools your team already watches. It only reads from FaceUp. It never writes into it.

Three results come up again and again. First, an alert the moment a report arrives: New Report starts the Zap and a chat app pings whoever is on duty, so nobody has to keep a FaceUp tab open all day. Second, a follow-up queue: New Message catches every reply a sender writes in an existing case, which is the part people tend to miss. Third, a shared log of internal discussion: New Internal Comment copies each comment your colleagues leave into a sheet or a task, so the team lead sees who said what without logging in.

Now the honest part. Zapier offers no action for FaceUp at all. You cannot create a report, close a case, reply to a sender or post a comment from a Zap. It also has no search step, so a Zap cannot look up an older case either. If your plan depends on writing into FaceUp, Zapier is the wrong tool for that half of the job, and no setting covered in Zapier troubleshooting adds a missing action.

One upside matters a lot on a free account. All three triggers are instant, so the alert does not wait for a timer, even on the cheapest plan. If you are still weighing tools, the FaceUp Make integration page is the Make counterpart, and Make vs Zapier is the next read.

Vocabulary

The Zapier terms behind a FaceUp alert

Seven terms carry this page. Each is defined once, with a FaceUp case in mind, and then used as is.

Zap
Your automation on Zapier. Here it always opens with a FaceUp event, followed by one or more actions in other apps that repeat for every new event.
Trigger
The app event that sets a Zap off. With FaceUp it is a new report, a new message or a new internal comment; once the Zap is on, Zapier waits for it.
Action
The step that does something once the Zap has started. FaceUp has none of its own, so every action writes, sends or moves data in another app.
Task
What Zapier bills: one action that completes. A FaceUp alert sent to one chat channel costs one task, and the plan's monthly count is a count of these.
Polling vs instant
Polling: Zapier asks an app for news at a set interval. Instant: the app reports the event the moment it happens. All three FaceUp triggers are instant.
Filter
A step that only lets the run go on when the incoming data meets the condition you choose; when it does not, the Zap ends there.
Connection
Your FaceUp login linked to Zapier one time, then offered again in every FaceUp step, so no Zap asks you to sign in twice.
Cost

What a FaceUp Zap really costs

Short version: the FaceUp side is free, and you pay for what happens downstream.

  • Trigger0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo

A trigger never costs a task, so FaceUp can fire as often as it likes. What counts is each action that succeeds after it. A failed action is not billed. The free plan gives you 100 tasks a month and unlimited Zaps, and FaceUp is not a premium app, so it works there. The catch: free Zaps stop at two steps, one trigger and one action. Add a second action or a filter and the Zap becomes multi-step, which needs a paid plan. The polling grid (15, 2, 1 and 1 minutes) does not apply here, since every FaceUp trigger is instant.

Connect

Connect FaceUp to Zapier in 3 steps

  1. 01

    Open your Apps page

    In your Zapier account, go to Apps and click + Add connection. A dialog opens with a search box. Type FaceUp and pick it from the list. This is the one place where every app you link to Zapier lives.

  2. 02

    Sign in to FaceUp

    Click Add connection. A new tab asks you to sign in to FaceUp. You need your own account on the app, plus access to any case you do not own and want the Zap to see.

  3. 03

    Grant access

    Allow Zapier to use the account. The connection now sits on your Apps page, and every FaceUp step you add later picks it from a menu instead of asking you to sign in again.

First Zap

Your first Zap: route each new report to Slack and Asana

GoalEvery new FaceUp report pings the compliance channel in Slack and opens a follow-up task in Asana.

  1. 01

    Create the Zap

    Start a new Zap and pick FaceUp as the app that starts it. Choose New Report as the event, then select the connection you made earlier.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent reports from your account, so you map the next steps on a real one rather than on blank fields.

  3. 03

    Add the Slack message

    Add Slack as the first action. Choose the channel your compliance team reads, then drop values from the test report into the message so the alert says what came in.

  4. 04

    Add the Asana task

    Add Asana as a second action and map the same report into a task. Two actions make this a multi-step Zap, so it needs a paid plan.

  5. 05

    Test and publish

    Test each action once and check what landed in Slack and Asana. When both look right, click Publish. The Zap is now on.

Triggers

FaceUp triggers on Zapier

3 events start a Zap when something happens in FaceUp, and 3 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Message

Instant trigger

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

This one starts your Zap whenever a sender writes a new message in FaceUp. Think of it as the follow-up channel: the person who filed a report comes back with more detail, and your team hears about it at once.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when a case owner should get an email or a chat ping each time a reporter replies, so no answer sits unread for days.
Watch out
it only catches messages written after the Zap is published, never the history of a case.
2

New Internal Comment

Instant trigger

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

Your colleagues talk about a case inside FaceUp through internal comments, and each fresh one can set off a Zap. Copying them out is a way to keep a team record of each case outside FaceUp.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when a team lead wants every comment copied into a Google Sheets log to follow the discussion without opening each case.
Watch out
the copy lives outside FaceUp, so check who can open that sheet before you send sensitive notes there.
3

New Report

Instant trigger

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

Fires as soon as someone submits a fresh report on FaceUp. It is the natural starting point for most setups, because a new case is the event everyone wants to know about first.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when the person on duty must be alerted in Slack or Microsoft Teams the minute a case opens, even on a free account.
Watch out
after a bulk import, a sudden wave of reports can be held back by Zapier's flood protection.
When it breaks

When a FaceUp Zap breaks

Zapier links no help article to FaceUp, so the known failures are the general ones. They still bite.

With triggers only, a FaceUp Zap cannot loop back into FaceUp itself. The risks sit elsewhere: the history it never sees, sudden bursts, and steps further down the chain.

  • Old reports are never picked up

    A Zap reacts only to what happens after it is switched on. Cases already in FaceUp stay put, and moving them is a separate job.

  • A burst of reports gets held back

    When a trigger suddenly returns a huge batch, for example after a migration, Zapier's flood protection can hold those items back.

  • A loop in the apps after FaceUp

    If a later step writes into a place that another of your Zaps watches, they can set each other off and burn through your tasks fast.

  • The free plan refuses a second action

    Free Zaps stop at one trigger and one action. Adding a filter or a second step makes the Zap multi-step, and it then needs a paid plan.
Need help

Need help automating FaceUp with Zapier?

A person reads every message.

FAQ

FaceUp Zapier integration: questions people ask

01Is the FaceUp Zapier integration free?
Yes, it works on the free Zapier plan, because FaceUp is not a premium app. The free plan gives you 100 tasks a month and as many Zaps as you want. The limit to know is the size of each Zap: on the free plan it holds one trigger and one action, nothing more. So a Zap that sends each new report to one chat channel is free, while one that also creates a task or adds a filter is multi-step and needs a paid plan. No FaceUp account tier is described in Zapier's listing, so check your own FaceUp access separately.
02How many tasks does a FaceUp Zap use?
The FaceUp trigger itself uses none. Zapier bills only the actions that succeed after it, one task each. A Zap with one action costs one task per report, message or comment it handles. A Zap with three actions costs three per event, since every successful action is counted on its own. An action that fails is not billed. A few apps take more than one task per action, so check the app you send data to. On a busy hotline with many follow-up messages, the action count is what you should watch, not the trigger.
03Do FaceUp triggers fire in real time?
Yes. All three FaceUp triggers are instant: FaceUp tells Zapier the moment a report, message or internal comment is created, and the Zap starts right away. That holds on every plan, including the free one, so the polling intervals of the plan grid do not apply. In the editor, a Zap built on an instant trigger shows a lightning bolt. This type is decided by FaceUp's own setup and cannot be switched from Zapier. The only delay you may see comes from the steps after the trigger, not from waiting for a check.
04What do you need to connect FaceUp to Zapier?
You need an account on FaceUp, plus read or write access on any case you do not own yourself and want the Zap to see. The steps happen from the Apps page of your Zapier account: add a connection, search for FaceUp, sign in to it in the tab that opens, then grant Zapier access. The connection is made once and reused by every FaceUp step afterwards. If a colleague owns the cases you care about, sort out their access in FaceUp before building, or the Zap will not see those events.
05Can Zapier create or update a FaceUp report?
No. Zapier lists no action and no search for FaceUp, only three triggers. A Zap can react when a report, a message or an internal comment appears, but it cannot open a case, close it, answer a sender or post a comment. Any change inside FaceUp still happens in FaceUp itself. What a Zap can do is carry the event out to other apps: a chat alert, a row in a sheet, a task in a project tool. Plan your workflow so that FaceUp stays the place where cases are handled, and Zapier only spreads the news.
06What if the FaceUp trigger or action you want is missing?
Then it does not exist on Zapier today, and there is no hidden menu to find. The listing holds exactly three triggers, New Message, New Internal Comment and New Report, and nothing that writes into FaceUp. A different event, such as a status change on a case, is not offered. Your options are to start the Zap from one of the three events that come closest, or to handle that step by hand inside FaceUp.
07Zapier, Make or n8n for FaceUp?
Judge it on criteria, not on a ranking. On Zapier, check three things against your needs. First, coverage: three triggers, no action, no search, so it suits alerting and logging, not writing back into FaceUp. Second, speed: every trigger is instant, on every plan. Third, cost: FaceUp works on the free plan, but only in two-step Zaps of one trigger and one action. Then put the same three questions to the other tool's own FaceUp listing before you choose, and pick the one that covers the events your team actually needs.
Same platform

Other docs you might need on this stack.

Browse all integrations