Connect KlientBrain to Zapier to start a Zap when something happens in one of your projects: post to a channel, add a row to a sheet, open a ticket or send an email.
Triggers
| Trigger | Starts a Zap when |
|---|---|
| Check Finished | A check of the project finishes |
| Visibility Moved | The project's visibility goes up or down after a check |
| New Inaccuracy | A check finds a new wrong or outdated claim about your brand |
Connect
- In KlientBrain, open Settings, then API keys, and generate a key. A Read only key is enough. Only a workspace Admin can make keys.
- In Zapier, create a Zap and choose KlientBrain AI Visibility as the trigger app. Pick one of the triggers above.
- Choose Sign in and paste the key.
- Choose the Project to watch. Each Zap watches one project.
- Choose Test trigger to see the latest event, then add your action.
Zapier looks for new events every few minutes, as often as your Zapier plan allows. Each check starts a Zap once.
What each trigger gives you
Every trigger gives the project's name, website and link, the event's time and its id.
| Trigger | Also gives |
|---|---|
| Check Finished | The check's id and finish time, and visibility with its low and high, now and at the previous check |
| Visibility Moved | Up or down, the change in points, whether the change is within the normal range, and visibility now and before |
| New Inaccuracy | How many claims were found and, for each (up to 20), what AI said, what is wrong, the severity, wrong or outdated, and the engine |
Visibility is a whole percentage, as the app shows it.
From your own scripts
The triggers read GET /api/v1/projects/{id}/events?event=check.finished. Use visibility.moved or claim.flagged for the other two. It returns the events of the latest finished checks, newest first, in the same form as webhooks, and each event keeps its id between requests. Add checks (1 to 25, default 10) to read more or fewer checks. For keys and errors, see API access.