Resources · Zapier integration

Guru Zapier integrationAutomate Guru with Zapier.

The Guru Zapier integration gives you 19 triggers, 13 actions and 4 searches to wire your knowledge base into the rest of your tools. 16 of those triggers fire instantly, and Guru works from the free Zapier plan, no paid add-on needed.

See the 36 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Guru Zapier integration actually does for you

Guru is the place where your team keeps its trusted answers, written as cards. Zapier is the bridge that lets something happening in Guru start work elsewhere, or lets another tool change Guru without anyone opening it. The Guru Zapier integration is that bridge, set up once and left running.

Three outcomes come up again and again. First, a knowledge base that flags its own stale content: a comment on a card or a card that slips to unverified can start a Zap that tags it, unverifies it or archives it. Second, onboarding and offboarding that follow your HR moves: Invite User, Add User to Group and Remove User keep the Guru team in step with whoever joins or leaves. Third, answers on demand: Ask a Question and Search With Sources pull an answer out of Guru so a later step can use it.

Now the limits. Zapier only sees the operations on this page, nothing more. There is no action to edit the text of an existing card, and no trigger fires on a card deleted outright, only on one archived. Three triggers (Card Unverified, Collection Trust Score Crosses Threshold, Team Card Count Reaches a Milestone) are checked on a timer, so they lag on the free plan while the other 16 do not.

Weighing other tools before you commit? The n8n vs Zapier and Make vs Zapier comparisons set the criteria side by side.

Vocabulary

Zapier vocabulary, in one minute

Eight words you will meet in the editor. Each one is explained once here, then used as is.

Zap
The automation you build: one trigger, then one or more actions that run every single time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for it to happen.
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 task is one action your Zap completed successfully; your plan counts those.
Polling vs instant
A polling trigger is checked on a timer for anything new. An instant trigger is reported by the app itself the moment it happens.
Filter
A step that lets the Zap continue only when what arrived meets a condition you set, and stops it otherwise.
Search step
A step that looks up something already in an app, so the steps after it can reuse whatever it found.
Connection
Your Guru account linked to Zapier once, then reused by every step in every Zap that touches Guru.
Cost

What a Guru Zap really costs

Guru is not a premium app, so it runs on the free plan. The bill is counted in tasks, and only finished actions count.

  • Free plan100 tasks per month, unlimited Zaps
  • Steps on the free plan2: one trigger, one action
  • Guru premium appNo, available on the free plan
  • Instant triggers16 of 19

The trigger costs nothing, and neither does Zapier checking for new items. Every action that succeeds is one task, so a Zap with three actions uses three times what a one-action Zap uses. An action that fails is not counted. The catch on the free plan: Zaps stop at two steps, one trigger and one action. Add a filter, a search or a second action and you need a paid plan. Plan the first version within two steps if you want to test for free.

Connect

Connect Guru to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need a Guru account first, plus access to any card or collection you do not own and want the Zap to touch.

  2. 02

    Pick Guru and start the link

    Type Guru in the search box of the dialog, select it, then click Add connection. A new tab opens on the Guru side so you can sign in with the account the Zaps should act as.

  3. 03

    Sign in and grant access

    Log in to Guru in that tab and allow Zapier to use the account. From then on, every Guru step in every Zap reuses this connection, so you never repeat the sign-in.

First Zap

Your first Guru Zap, step by step

GoalWhen someone comments on a card, send the card back to unverified and tag it so the owner knows it needs a look.

  1. 01

    Build: pick the trigger

    In Build, choose Guru as the app and Card Comment Created as the event. It is instant, so a fresh comment starts the Zap straight away on any plan.

  2. 02

    Test the trigger

    Click Test. Zapier brings back the three most recent comments from your account, so you map the next steps on a real one instead of a made-up example.

  3. 03

    Add Unverify Card

    Add a Guru action and pick Unverify Card. Card ID is required: look in the trigger's test result for a field holding the card's identifier and map it here. If the comment does not bring one back, this Zap cannot run as drawn.

  4. 04

    Add Add Tag to Card

    Add a second Guru action, Add Tag to Card, and choose a tag your team already created for reviews. Two actions make this a multi-step Zap, which needs a paid plan.

  5. 05

    Test, then Publish

    Run each step once with Test and read what came back. When both actions look right, click Publish to switch the Zap on for good.

Triggers

Guru triggers on Zapier

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

1

Announcement Sent

Instant trigger

In Zapier“Triggers when a new announcement is sent”

Starts your Zap each time someone sends an announcement in Guru, so a message meant for the team can travel further without being pasted by hand into another channel or tool.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your support lead announces a new refund policy in Guru, and you want that same update logged for the managers who rarely open the knowledge base.
Watch out
each announcement is one run, and every action after it counts as a task.
2

New Folder

Instant trigger

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

Watches one collection and wakes up when a folder is added to it. Handy when new folders mark the start of a project or a new product line inside your knowledge base.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
the product team opens a folder for each upcoming release, and you want the right people pulled in from day one.
Watch out
the trigger needs a Collection ID, so it only watches one collection; a second collection means a second Zap.
3

Card Archived

Instant trigger

In Zapier“Triggers when a user archives a Card.”

Fires when a person archives a card. It is the closest signal Guru gives Zapier that a piece of knowledge has been retired, which matters when other tools still point to it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
an ops manager wants a trace of every retired procedure, or wants to bring back cards from a sensitive collection with Restore Card when they get archived by mistake.
Watch out
it reacts to archiving, not to a card being edited or unverified.
4

Card Comment Created

Instant trigger

In Zapier“Triggers when a user comments on a Card.”

Reacts as soon as a user leaves a comment on a card. Comments are usually where people say an answer is wrong or out of date, so this is the natural entry point for a review loop.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a sales rep flags a pricing card as off, and you want the card unverified and tagged for review without the knowledge manager chasing it.
Watch out
every comment starts a run, and each successful action after it costs a task.
5

Card Content Copied

Instant trigger

In Zapier“Triggers when a user either copies the content within the Card or clicks on the “Copy Card content" icon.”

Picks up the moment someone copies text out of a card, either by selecting it or with the copy-content icon. It tells you which answers actually get reused in conversations.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a support team wants to see which macros and policies agents paste into tickets, to know what deserves a fresh review first.
Watch out
copying is a frequent gesture, and each copy that leads to a successful action spends a task.
6

Card Created

Instant trigger

In Zapier“Triggers when a new Card is published.”

A new card published in Guru starts this one. What counts is the card going live for the team, not the moment someone starts writing it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
every new HR policy card should get a PDF copy through Create PDF From a Guru Card ID, for the folder your auditors read.
Watch out
the Zap only sees cards published after you switch it on, never the ones already there.
7

Card Favorited

Instant trigger

In Zapier“Triggers when a user favorites a Card.”

Runs when a user adds a card to their favorites. A favorite is a quiet vote of confidence: someone found that answer useful enough to want it close at hand.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
an enablement manager wants to spot the cards new hires bookmark in their first weeks and tag them as onboarding essentials.
Watch out
each favorite is one run, so a popular card can start the Zap many times.
9

Card Unfavorited

Instant trigger

In Zapier“Triggers when a user removes a Card from their "My Favorite Card" list.”

Reacts when a user takes a card out of their favorites list. On its own it is a small signal, but repeated it can say an answer stopped being useful.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
pair it with Card Favorited to keep a running record of which cards gain or lose fans across the team.
Watch out
people clean up their favorites for many reasons, so read it as a hint, never as proof that a card is wrong.
10

Card Unverified

Polling trigger

In Zapier“Triggers when a Card becomes unverified.”

Catches a card that falls out of its verified state. In Guru that is the moment an answer stops being flagged as trusted.

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 compliance owner wants every unverified card in a regulated collection tagged for review, so nothing stays doubtful for long.
Watch out
this one is not instant, so on the free plan the Zap can start up to 15 minutes after the card changes.
11

Card Updated

Instant trigger

In Zapier“Triggers when a user makes an edit to a Card.”

Fires whenever a user edits a card. Any change counts, from a rewritten paragraph to a typo fix, which makes it the widest trigger of the list.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a legal team wants a fresh PDF of a contract-template card every time someone touches it, so the archive always matches the live version.
Watch out
a Zap that edits the same card would set itself off again; keep actions that write into Guru away from this trigger.
12

Card Verified

Instant trigger

In Zapier“Triggers when a user verifies a Card.”

Runs the moment a user verifies a card, meaning an expert has confirmed the answer is right. It is the cleanest signal that content is ready to be shared outside the team.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
once a product spec card is verified, a sales engineer wants a tag set on it so the sales team knows it is safe to quote.
Watch out
unverified cards do not fire here; they have their own trigger, which works on a timer.
13

Card Viewed

Instant trigger

In Zapier“Triggers when a user views a Card.”

Fires every time a user opens a card. It is the raw reading signal, useful when you care about who looked at something rather than who changed it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a training lead wants to know when new hires open the security policy card, as a light check that the reading actually happened.
Watch out
views pile up fast, and each one followed by a successful action costs a task, so pair it with a narrow scope.
14

New Collection

Instant trigger

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

Starts the Zap when a collection is created in Guru. Collections are the top shelves of your knowledge base, so a new one often means a new team or department coming on board.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
IT wants a matching group set up with Create Group as soon as a department opens its own collection.
Watch out
the Zap sees only collections created after it is published.
15

Collection Trust Score Crosses Threshold

Polling trigger

In Zapier“Triggers when a Collection’s Trust Score crosses a specified threshold.”

Watches the trust score of one collection and fires when it moves past a level you choose, in either direction. Set 85 and the Zap starts when the score dips below or climbs above 85%.

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 knowledge manager wants a warning when the support collection drops under the bar the team agreed on.
Watch out
both Collection ID and Threshold are required, and one Zap watches a single collection.
16

New Group

Instant trigger

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

Fires when someone creates a group in Guru. A new group often means a team is being reorganized.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
an admin wants a record of every new group, so permission changes never happen without a trace somewhere else.
Watch out
it covers creation only; people joining an existing group come through User Added to Group instead.
17

New Tag

Instant trigger

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

Every tag created in Guru wakes this trigger up. Tags are how teams slice cards across collections, so new ones can drift into duplicates if nobody watches them.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a content owner wants every new tag logged, to catch two people inventing near-identical labels in the same week.
Watch out
Add Tag to Card only uses tags that already exist, so this trigger is a good place to notice when the right one is missing.
18

Team Card Count Reaches a Milestone

Polling trigger

In Zapier“Triggers when a Team’s Card count reaches a milestone.”

Counts the cards of your Guru team and fires at each step you define. With an Increment of 100, it starts at 100 cards, then 200, then 300, and so 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
a head of support wants to celebrate, or simply report, each time the knowledge base grows by a round number.
Watch out
the Increment field is required, and the Zap only notices a milestone on its next check.
19

User Added to Group

Instant trigger

In Zapier“Triggers when a user is added to a Group.”

Someone joining a Guru group sets this one off. It is the signal that someone just joined a team inside Guru.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a team lead wants new members of the Finance group to land on the right starter cards without asking anyone.
Watch out
if a Zap adds users to groups itself, keep it apart from this trigger, or the two can feed each other.
Actions

Guru actions on Zapier

Guru gives you 13 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Tag to Card

Action

In Zapier“Adds an existing Tag to a Card.”

Attaches a tag to a card, which makes it easy to filter and find later. Good for labeling cards by status or audience.

When to use it
every card flagged in a comment gets a needs-review tag.
Watch out
the tag must already exist in Guru; this action does not create new ones.
2

Add User to Group

Action

In Zapier“Adds a user to a Group.”

Puts a user in a group, and can invite them to the team or create the group on the way if needed. Two yes-or-no fields decide that.

When to use it
a new sales rep joins the Sales group automatically.
Watch out
User Email, Invite User?, Group Name and Create Group? are all required.
3

Archive Card

Action

In Zapier“Archives a Card.”

Retires a card from active use by archiving it. Readers stop landing on content that no longer applies.

When to use it
a product is discontinued in your catalog tool, and its how-to card should go with it.
Watch out
Card ID is required, and an archived card can still be brought back with Restore Card.
4

Ask a Question

Action

In Zapier“Submits a question to Guru and returns the answer.”

Sends a question to Guru and returns its answer, so a later step can use the reply. It turns your knowledge base into something other tools can query.

When to use it
an incoming customer question gets a suggested answer drafted before an agent reads it.
Watch out
the Question field is required, and the answer is only as good as the cards behind it.
5

Create Card

Action

In Zapier“Creates a new Card.”

Publishes a new card in Guru from data another step brings in. It is how answers born elsewhere end up in your knowledge base.

When to use it
a resolved support ticket with a good answer becomes a card the whole team can read.
Watch out
a Collection ID is required, so decide the destination collection before you build.
6

Create Group

Action

In Zapier“Creates a new Group.”

Sets up a new group in your Guru team. It needs no required field to set up.

When to use it
a new office or department appears in your HR tool and needs its own group in Guru from the start.
7

Invite User

Action

In Zapier“Adds a user to your Guru Team.”

Adds a person to your Guru team from their email address. New colleagues get access without an admin typing anything.

When to use it
a hire marked as started in your HR tool gets their Guru invite on day one.
Watch out
User Email is required, so the earlier step must carry a valid address.
8

Create PDF From a Guru Card ID

Action

In Zapier“Generate a PDF file from a Guru card ID. You must have access to the Guru card in order to generate a PDF”

Turns a card into a PDF file that later steps can store or send. Useful when an answer has to leave Guru as a fixed document.

When to use it
verified policy cards get archived as PDFs for an audit trail.
Watch out
the connected account needs access to the card, or no PDF comes out.
9

Remove User

Action

In Zapier“Removes a user from your Guru Team.”

Removes a person from your Guru team entirely, based on their email address. This is the offboarding move.

When to use it
a leaver flagged in your HR tool loses Guru access the same day.
Watch out
User Email is required; test with a dummy account before you point it at real people.
10

Remove User From Group

Action

In Zapier“Removes a user from a Group.”

Takes a user out of one group while keeping them in the Guru team, unlike Remove User.

When to use it
someone moves from Support to Marketing and should leave the Support group.
Watch out
both User Email and Group are required.
11

Restore Card

Action

In Zapier“Restores a previously Archived Card.”

Brings an archived card back into service. It accepts either the card title or its ID.

When to use it
a seasonal offer returns, and the card that explained it last year should come back too.
Watch out
a title can match more than one card; the ID is the safer choice when you have it.
12

Unverify Card

Action

In Zapier“Unverifies a Card.”

Pulls a card back to unverified so readers know it should not be fully trusted yet. The opposite move of Verify Card.

When to use it
a comment or a product change means the answer needs a second look from its owner.
Watch out
Card ID is required.
13

Verify Card

Action

In Zapier“Verifies a Card.”

Marks a card as verified on behalf of the connected account. The card then shows as trusted to everyone who reads it.

When to use it
an approval recorded in another tool should also confirm the matching card in Guru.
Watch out
it only needs a Card ID, so double-check you map the right one.
Searches

Guru searches on Zapier

4 search steps look for data that already exists in Guru, so a later step can use it.

Searches sit at the bottom of the action list in the editor, under SEARCH. They look something up in Guru and pass it to the next steps. Adding one makes the Zap multi-step. Three settings decide what happens when the result is not the one you expected.

1

Find Card

SearchFind or create

In Zapier“Finds a Card. If you cannot find the Card, you can create a Card”

Looks for an existing card so a later step can act on it. This is also the search behind Find or Create Card, which the editor lists as a separate line but is the same step with the create box ticked.

When to use it
before tagging or verifying, make sure the card exists, and create it if it does not.
2

Find Archived Card

Search

In Zapier“Finds an Archived Card.”

Searches among archived cards, by title. It is the search to reach for when a card has been retired.

When to use it
locate a retired card before handing it to Restore Card.
Watch out
Card Title is required, and Guru, not Zapier, decides how close the match must be.
3

Search With Sources

Search

In Zapier“Performs a search and returns results with their sources.”

Runs a search in Guru and returns results together with where they come from. Handy when a reply has to cite its source.

When to use it
an internal helpdesk reply links back to the cards it relied on.
Watch out
with Include Content switched on, only the first 5 documents carry their content.
4

Find Tag

Search

In Zapier“Finds a Tag.”

Looks up an existing tag in Guru and hands it to the next step. A tag found this way can feed Add Tag to Card directly.

When to use it
pick the right tag by name before attaching it, instead of hardcoding it in the action.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and skips the steps that relied on it. Switch it on and the Zap carries on empty-handed.
  2. Create Card if it doesn't exist yet?
    Ticking this box turns Find Card into Find or Create Card. The setting above then disappears, and the step asks for what it needs to create the missing card.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on together.
When it breaks

When a Guru Zap breaks

Zapier links no help article to Guru, so the traps below are the general ones, applied to how Guru works.

They come from the order of events, not from Guru itself. If a Zap stops, the Zapier troubleshooting guide is the next stop.

  • Nothing from before the Zap

    A Zap only reacts to what happens after you publish it. Cards, comments or groups that already existed are never picked up; moving them is a separate job.

  • A Zap that triggers itself

    Card Updated plus an action that edits the same card makes a loop. The Zap sets itself off again and again and eats your task count quickly.

  • A bulk import held back

    After a big import or a migration, a trigger can return a huge batch at once. Zapier's flood protection can then hold those items back.

  • Polling does not double up

    On the three timer-based triggers, Zapier remembers what it has already seen, so the same card does not start the Zap twice.
Need help

Need help automating Guru with Zapier?

A person reads every message.

FAQ

Guru and Zapier: common questions

01Is the Guru Zapier integration free?
Yes, Guru is not a premium app, so it works on the free Zapier plan. That plan gives you 100 tasks per month and unlimited Zaps, but each Zap is limited to two steps: one trigger and one action. As soon as you add a second action, a filter or a search, the Zap becomes multi-step and needs a paid plan. No prices appear here on purpose, because Zapier changes its grids often; check the plan page before you decide.
02How many tasks does a Guru Zap use?
One task per action that succeeds, nothing for the trigger. A Zap that unverifies a card uses one task each time it runs. Add a second action, say tagging the card, and every run costs two. Failed actions are not counted, and Zapier checking Guru for new items is free. Watch the busy triggers, Card Viewed and Card Content Copied in particular, because they can start many runs in a short time and each run with a successful action spends tasks.
03Do Guru triggers fire in real time?
Sixteen of the nineteen do. Those are instant: Guru tells Zapier the moment the event happens, and the Zap starts at once whatever your plan. The three others, Card Unverified, Collection Trust Score Crosses Threshold and Team Card Count Reaches a Milestone, are polling triggers. Zapier checks them on a timer: every 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. The type comes from Guru's side and cannot be changed in the editor.
04What does it take to connect Guru to Zapier?
A Guru account and a Zapier account. You add the connection from the Apps page with + Add connection, pick Guru, sign in to Guru in the tab that opens and grant access. The account you connect should be able to read or edit the cards, collections and groups your Zaps will touch. Several steps depend on that: Create PDF From a Guru Card ID only works on a card the account can open, and Create Card needs a collection.
05Why does Add Tag to Card fail with a new tag?
Because the action only attaches tags that already exist in Guru. It does not create them. If the tag name your Zap sends has never been created, the step has nothing to attach. Create the tag in Guru first, or put Find Tag before the action so the Zap picks a real tag by name. Keep in mind that a search makes the Zap multi-step, so that version needs a paid plan.
06What if the Guru operation needed is missing?
Then Zapier cannot do it with this integration, at least for now. The list on this page is the full set the editor offers: 19 triggers, 13 actions and 4 searches. There is, for example, no action to rewrite the body of an existing card. The workarounds are to rethink the flow around the operations that do exist, such as archiving and creating a new card, or to look at another automation tool that talks to Guru differently.
07Zapier, Make or n8n for Guru?
It depends on your criteria, not on a winner. Zapier fits if you want to start fast on the free plan and the 36 operations listed here cover your needs. If you already run your automations elsewhere, the useful criterion is coverage: compare the operations each tool exposes for Guru, then what a typical run costs you on each, before you choose. The free plan limit of two steps per Zap is the other line to weigh.
Same platform

Other docs you might need on this stack.

Browse all integrations