Resources · Zapier integration

Braintrust Zapier integrationAutomate Braintrust with Zapier.

The Braintrust Zapier integration gives you 2 triggers, 0 actions and 0 searches. Braintrust can start a Zap, never finish one: an automation event or a fresh project kicks things off, and another app does the work. Here is what that means on the free plan.

See the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Braintrust Zapier integration actually does

Braintrust is the place where AI teams test, trace and watch their models before and after launch. Hooked to Zapier, it becomes a source of signals: when one of its automations records an event, or when someone opens a new project, Zapier can pass the news to the tools your team already reads. That is the whole deal, and it is a one-way street.

Three things people usually get out of it. First, an alert in the channel where the team lives: New Event fires when a Braintrust automation creates an event, so a monitoring signal lands in chat instead of waiting for someone to open a dashboard. Second, a log row per event: the same trigger can feed a spreadsheet, which gives non-technical colleagues a history they can sort and filter. Third, a tidy project register: New Project spots each project created in Braintrust, so your tracker, wiki or CRM gets a matching line without anyone copying it over.

Here is the tip worth remembering. Of the two triggers, New Event is the only instant one. It reacts the moment the event exists, even on the free plan, while New Project waits for Zapier's next check. If speed matters (and for monitoring it usually does), build on events.

Now the honest part. Zapier cannot write anything into Braintrust: there is no action, so no Zap can create or change anything in Braintrust. There is no search step either, which means a Zap cannot look up an existing Braintrust record halfway through. If that is the job, the Braintrust Make integration is worth a look, and the Make vs Zapier comparison helps you weigh the two tools for that job.

Vocabulary

Zapier words in one minute

Seven terms come back on this page. Each one is explained once, here, 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. Here it is always a Braintrust event or project; once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you in another app.
Task
The unit Zapier bills. One task equals one action your Zap completes successfully; your plan counts those, nothing else.
Polling vs instant
A polling trigger is checked on a timer by Zapier. An instant trigger is reported by the app itself the moment the event happens.
Filter
A step that stops the Zap unless what arrived passes a rule you set, so only the items you care about reach the next app.
Connection
Your Braintrust account linked to Zapier one time, then reused by every step that needs Braintrust in any of your Zaps.
Cost

What a Braintrust Zap really costs

Short version: the Braintrust side costs nothing, because it only ever triggers.

  • Trigger0 task, always
  • Each successful action1 task (a few apps take more)
  • Free plan100 tasks a month, 2-step Zaps only
  • Premium appNo, available on Free

A trigger never consumes a task, and neither does Zapier checking for new data, however often it looks. What you pay for is the action in the other app, and only when it succeeds: a failed action is not counted. Braintrust is not a premium app, so it works on the free plan, which gives you 100 tasks a month and unlimited Zaps. The catch nobody mentions: free Zaps stop at two steps. Add a second action, or a filter, and the Zap becomes multi-step, which needs a paid plan.

Connect

Connect Braintrust to Zapier in 3 steps

  1. 01

    Open your apps list

    In your Zapier account, go to the Apps page and click + Add connection. A dialog opens: type Braintrust in the search box and pick it from the results.

  2. 02

    Sign in to Braintrust

    Click Add connection. A new tab opens on Braintrust: log in with the account that owns, or can at least read, the projects you want Zapier to keep an eye on.

  3. 03

    Grant access and close

    Accept the access request so Zapier can read your account. The connection now shows up in your apps list, and every future Braintrust step reuses it without asking again.

First Zap

Your first Braintrust Zap, step by step

GoalPost a message in your team chat each time a Braintrust automation logs a new event, and keep a row of it in a spreadsheet.

  1. 01

    Create the Zap

    Start a new Zap and choose Braintrust as the app that starts it, with New Event as the event. Pick the connection you set up earlier.

  2. 02

    Set the trigger

    Choose the project to monitor, give the automation a name your team will recognize, then select the event type. All three boxes are mandatory.

  3. 03

    Test the trigger

    Run the test. Zapier brings back the three most recent items from your account, so you map the next step on a real event rather than a guess.

  4. 04

    Add the two actions

    Add the chat app and map the event details into the message, then add the spreadsheet as a second action. Two actions make the Zap multi-step, so it needs a paid plan.

  5. 05

    Test, then publish

    Test each step once and read what came back. When the message and the row look right, click Publish to switch the Zap on. From then on, every new event goes out instantly.

Triggers

Braintrust triggers on Zapier

2 events start a Zap when something happens in Braintrust, and one of them is instant: the app calls Zapier straight away, whatever your plan.

1

New Event

Instant trigger

In Zapier“Triggers when an automation creates a new event.”

Each time one of your Braintrust automations records an event, this trigger hands it to Zapier, ready to be routed to chat, email or a sheet. You decide which project and which kind of event it listens to, so one Zap can stay focused on a single signal.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you want the on-call engineer or the product lead to hear about a monitoring signal without opening Braintrust.
Watch out
the project, automation name and event type are all required, so the connected account has to see the project before the trigger can be saved.
2

New Project

Polling trigger

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

Spots every project that appears in your Braintrust account and passes its details along, which keeps an outside register in step with what the AI team is actually working on.

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
your ops or finance colleagues track AI initiatives in a spreadsheet or a project tool and want a line added automatically for each new one.
Watch out
projects created before you publish the Zap are never picked up, so seed your register by hand once.
When it breaks

When a Braintrust Zap breaks

Zapier publishes no help article specific to Braintrust, so the failures below are the general ones that hit any Zap built on these two triggers.

Most problems come from expecting the Zap to know about the past, or from asking it to do something it cannot. Four cases cover nearly everything. If you are stuck on one that is not here, the Zapier troubleshooting guide goes deeper.

  • Old events and projects never show up

    A Zap only reacts to what happens after you switch it on. Anything already in Braintrust stays where it is; moving that backlog is a separate job.

  • A burst of projects gets held back

    If a bulk import or a migration suddenly creates many projects, Zapier's flood protection can pause the trigger instead of firing for each one.

  • The same project is not sent twice

    On the polling trigger, Zapier remembers which projects it has already seen, so the same project never starts the Zap a second time.

  • The filter never lets anything through

    Filter rules are typed: a text rule only works on text, a number rule only on numbers. Picking the wrong kind is the usual reason nothing passes.
Need help

Need help automating Braintrust with Zapier?

A person reads every message.

FAQ

Braintrust Zapier integration: common questions

01Is the Braintrust Zapier integration free?
Yes, it works on the free plan because Braintrust is not a premium app on Zapier. The free plan gives you 100 tasks a month and as many Zaps as you like. The limit is the shape of the Zap: one trigger and one action, nothing more. As soon as you add a filter or a second action, Zapier treats it as a multi-step Zap and asks for a paid plan.
02How many tasks does a Braintrust Zap use?
The Braintrust part uses none, since both operations are triggers and a trigger never costs a task. Checking for new projects is free too, however often Zapier looks. You are billed one task each time the action in the other app succeeds, and a failed action is not counted. A Zap with three actions after the trigger would therefore use three tasks per event, assuming all three go through. Only that action counts.
03Does Braintrust trigger Zaps in real time?
Half of it does. New Event is an instant trigger: Braintrust tells Zapier the moment the event exists, so the Zap starts right away on every plan, free included. New Project is a polling trigger: Zapier checks on a timer, every 15 minutes on the free plan, 2 minutes on Professional and 1 minute on Team or Enterprise. That type comes from the app itself and cannot be switched in the editor.
04What do you need to connect a Braintrust account?
A Braintrust account, plus read access to any project you do not own and want the Zap to watch. In Zapier you open the Apps page, click + Add connection, pick Braintrust, then sign in on the tab that opens and grant access. The connection is saved once and reused by every Braintrust step afterwards, so you will not repeat the process for each new Zap. The connection only sees what that Braintrust account can see, which matters for the project you pick in New Event.
05Why can't New Event be saved without a project?
Because the trigger needs three required settings before it can listen: the project to monitor, a name for the automation and the event type. If the project dropdown stays empty, the connected account simply has no access to any project. Reconnecting with an account that can see the right project usually fixes it. Give each automation a clear name so your team can tell several Zaps apart later. A name that mentions the project and the event type works well.
06What if the Braintrust operation you need is missing?
Then Zapier cannot do it with Braintrust today. The integration only has two triggers, New Event and New Project, with no action and no search, so no Zap can write into Braintrust or look up an existing record there. Writing back means checking another automation tool's Braintrust module or the app's own features. In practice, the realistic setup is Braintrust as the starting point and every write happening in the other app, where Zapier offers actions.
07Zapier, Make or n8n for Braintrust?
It depends on the job rather than on a winner. If you only need Braintrust to alert other tools, Zapier's two triggers cover it, and New Event is instant even on the free plan. If you need to write back into Braintrust, Zapier has no action for that, so check what Make and n8n offer for this app, then compare their pricing logic and how each tool fits the way your team already works.
Same platform

Other docs you might need on this stack.

Browse all integrations