Resources · Zapier integration

Langfuse Zapier integrationAutomate Langfuse with Zapier.

The Langfuse Zapier integration offers 1 trigger and 1 action, and no search. The trigger spots new projects; the action is a raw request to Langfuse for technical users. Small, but enough to keep a team and its tools in step with Langfuse. It works on the free plan.

See the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Langfuse Zapier integration actually does

Langfuse is an open-source engineering platform for applications built on large language models: teams use it together to debug, analyse and improve those applications. On Zapier, its app is narrow. It notices when a new project is created, and it can send a raw request to Langfuse for anything else, provided someone knows the exact call.

Three results teams build with it. First, a team that hears about new projects: New Project starts the Zap and the next step posts the project's name in a chat channel, so nobody has to open Langfuse to find it. Second, a project register outside Langfuse: the same trigger adds a row to a spreadsheet, handy for a manager who follows the list without opening the platform. Third, a custom call made from a Zap: a developer uses API Request (Beta) to reach a part of Langfuse that has no ready-made action.

What Zapier does not do here, and the app page will not tell you: there is no ready-made action to create, update or delete anything, no search step, and no trigger other than new projects. And the only trigger is a polling one, so nothing arrives the instant it happens.

If you are still deciding which tool should carry your AI workflows, our n8n vs Zapier comparison is worth a read before you commit.

Vocabulary

Zapier vocabulary, in one minute

Seven words come back on every block below. Here they are, once, in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for that event, here a new Langfuse project.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you in an app.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan counts those and nothing else.
Polling vs instant
Polling: Zapier asks the app for new items on a timer. Instant: the app calls Zapier itself the moment the event happens.
Filter
A step that lets the Zap carry on only when what arrived meets your condition, and stops it otherwise.
Connection
Your Langfuse account linked to Zapier once, then reused by every step in every Zap that talks to Langfuse.
Cost

What a Langfuse Zap really costs you

Langfuse is not a premium app, so it runs on the free plan. You pay for what the Zap does, not for the waiting.

  • Premium appNo, free plan included
  • Free plan100 tasks a month, two-step Zaps only
  • Trigger cost0 tasks, whatever the interval
  • Action cost1 task per successful run

The New Project trigger costs nothing, and neither do Zapier's checks for new projects, however often they run. Each action that succeeds is one task, API Request (Beta) included; a failed action is not counted. The free plan gives you 100 tasks a month and unlimited Zaps, but only two-step Zaps: one trigger and one action. A filter or a second action makes the Zap multi-step, which needs a paid plan. Because New Project is a polling trigger, your plan also sets how often Zapier looks.

Connect

Connect Langfuse to Zapier in three steps

  1. 01

    Open your connections

    In Zapier, open the Apps page of your account and click + Add connection. You need a Langfuse account first, plus access to any project you do not own but want the Zap to see.

  2. 02

    Pick Langfuse

    Search for Langfuse in the dialog, select it and click Add connection. A new tab opens on the Langfuse side, which is where the two accounts actually get linked.

  3. 03

    Sign in and allow access

    Sign in to Langfuse in that tab and grant Zapier access. The tab closes and the connection shows up in your list, reused from then on by every Zap that uses Langfuse.

First Zap

Your first Langfuse Zap: new project, team alerted

GoalEvery project created in Langfuse posts its name in the AI team's channel, so the people who will work on it know straight away.

  1. 01

    Build: start from Langfuse

    Create a Zap, pick Langfuse as the app that starts it and New Project as the event, then select the Langfuse connection you made earlier.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent projects of the connected account, so the fields you map come from a real one.

  3. 03

    Add the message

    Add your chat app as the action, choose the channel, and drop the project name from Langfuse into the text of the message.

  4. 04

    Test, then Publish

    Run the action once and look at the channel. If the message reads well, click Publish to switch the Zap on. Only projects created after that will start it.

Triggers

The Langfuse trigger

1 event starts a Zap when something happens in Langfuse. Zapier checks for them at the interval your plan allows.

1

New Project

Polling trigger

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

Starts your Zap each time a project is created in Langfuse and passes its details to the steps that follow. It is the one door through which Zapier sees activity on the Langfuse side.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a new project should be announced to a team, logged in a register or turned into a task in your project tool.
Watch out
projects created before you publish the Zap are never picked up; listing them elsewhere is a separate job.
Actions

The Langfuse action

Langfuse gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.

1

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

An advanced step that sends a raw HTTP request to Langfuse with the connection you already set up, for anything the integration has no ready action for.

When to use it
a developer knows the exact Langfuse call needed and wants it to run inside a Zap.
Watch out
HTTP Method, URL and Stop on error are required, and only domains tied to the app are accepted.
When it breaks

When a Langfuse Zap breaks

Zapier links one help article to this app, How to get started with Langfuse on Zapier, and documents no Langfuse-specific rate limit. The usual failures are the ones every Zap shares.

  • Existing projects never show up

    A Zap reacts only to what happens after you switch it on. Projects already in Langfuse stay out of it; listing them elsewhere is another job.

  • A Zap that sets itself off

    If the API Request (Beta) step in the Zap creates a project, it writes where its own New Project trigger watches, starts again and again, and burns tasks.

  • A bulk import gets held

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

  • No double runs

    On a polling trigger, Zapier keeps track of what it has already seen, so the same project never starts the Zap twice.
Need help

Need help automating Langfuse with Zapier?

A person reads every message.

FAQ

Langfuse Zapier integration: common questions

01Is the Langfuse Zapier integration free?
Yes, for simple Zaps. Langfuse is not a premium app, so it works on Zapier's free plan, which includes 100 tasks a month and unlimited Zaps. The catch is the shape of the Zap: the free plan only builds two-step Zaps, one trigger and one action. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. On the free plan, Zapier also checks for new Langfuse projects every 15 minutes.
02How many tasks does a Langfuse Zap use?
One task per action that succeeds. The New Project trigger is free, and so are Zapier's checks for new projects, however often they happen. A Zap that posts each new project in a channel spends one task per project. An API Request (Beta) step that goes through also counts as one task, and one that fails is not counted. With two actions, each successful one is billed separately, so the cost grows with the steps, not with the waiting.
03Does Langfuse trigger Zaps in real time?
No. New Project is a polling trigger: Zapier asks Langfuse for new projects at a fixed interval set by your plan. That means every 15 minutes on Free, every 2 minutes on Professional, and every minute on Team and Enterprise. The type comes from the app's own service, so it cannot be switched to instant in the editor. On paid plans you can change the interval, and while testing you can run a check by hand from the editor.
04What does it take to connect Langfuse to Zapier?
A Langfuse account, and access to any project you do not own but want the Zap to read or touch. The connection is made from the Apps page of your Zapier account: add a connection, search for Langfuse, sign in on the tab that opens and grant access. Every Zap that uses Langfuse then reuses that same connection, so you only go through this once per account. No extra setup is needed on the Zapier side.
05Why does API Request (Beta) fail in a Langfuse Zap?
Usually because of one of its three required settings. The step needs an HTTP Method, a URL, and a choice for Stop on error. The URL must point to a domain associated with Langfuse; anything else is refused. Set to Yes, Stop on error halts the step when Langfuse returns an error; set to No, the Zap keeps going regardless, which can hide the problem. Test the step and read the response before you publish.
06What if the Langfuse operation you need is not on Zapier?
Then the ready-made app does not cover it. Zapier offers one trigger, New Project, and one action, API Request (Beta). For anything else, that raw request is the only route, and it needs someone who knows the exact Langfuse call. If nobody on the team does, the options are to keep that part manual or to check whether another automation tool offers the operation as a ready step. Workarounds built around a missing step tend to break later.
07Zapier, Make or n8n for Langfuse?
It depends on the criterion that matters most. On ready-made coverage, Zapier offers one trigger and the raw API Request (Beta) step, so compare that with what the other tools list for Langfuse. On cost, count your expected runs, since Zapier bills each successful action. On technical comfort, think about who on the team will write the raw requests. None of the three is better in every case; compare them on your own volume and needs.
Same platform

Other docs you might need on this stack.

Browse all integrations