Resources · Zapier integration

Perfect Wiki Zapier integrationAutomate Perfect Wiki with Zapier.

The Perfect Wiki Zapier integration gives you 0 triggers, 1 action and 0 searches. One move, but a useful one: any question that shows up in another tool can be put to your Perfect Wiki knowledge bot, and the answer handed on to whoever asked.

See the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Perfect Wiki Zapier integration actually does

Perfect Wiki is a knowledge base: the place where a company gathers and organises what its people need to know, so they can find it without asking around. On Zapier, it does exactly one thing: it sends a question to the Perfect Wiki knowledge bot and passes the answer to the next step of your Zap.

Three results come out of that single action, Query Knowledge Bot. An internal help channel that answers itself: a question posted in team chat goes to the bot, and the answer comes back as a reply in another channel. A support inbox with a first draft ready: an incoming request is put to the bot, and the answer lands next to the ticket for an agent to check before sending. A form that does not leave people waiting: a question submitted on an internal form gets the bot's answer by email.

What Zapier does not do here is just as clear. Perfect Wiki has no trigger on Zapier, so nothing that happens in your wiki can start a Zap: a new page, an edit, a question asked directly in Perfect Wiki all stay invisible. There is no search step and no way to create or edit wiki pages from a Zap either. Every Zap begins in another app and uses Perfect Wiki as a source of answers.

Asking the bot alone already fills the two steps the free plan allows, so any flow that also delivers the answer is multi-step and needs a paid plan. To see where Zapier stands among similar tools, the Zapier review is a good start.

Vocabulary

Zapier vocabulary in one minute

Seven terms carry this page. Here they are in everyday words.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event that starts the Zap. Perfect Wiki offers none, so your trigger always comes from another app, such as team chat.
Action
What the Zap does once it starts: the step that writes, sends or moves something. Perfect Wiki's only one asks its bot a question.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan is a monthly count of those.
Polling vs instant trigger
Polling: Zapier checks the other app on a timer. Instant: that app reports the event itself. Your trigger app decides which.
Filter
A step that lets the Zap continue only if what arrived meets a condition you set, and stops it otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes it one, and that needs a paid plan.
Cost

What a Perfect Wiki Zap really costs

Perfect Wiki is not reserved for paid plans: it works from the free plan.

  • Trigger (other app)Free, never counted
  • Each successful bot query1 task
  • Free plan100 tasks a month, two-step Zaps
  • Query plus replyMulti-step Zap, paid plan

The trigger, from whichever app starts your Zap, never costs a task. Each successful question to the bot counts as one task; a failed one is not counted. The catch is the shape of the Zap. The free plan gives you 100 tasks a month but stops at two steps: one trigger and one action. Asking the bot uses that single action, so sending the answer anywhere needs a second action, which makes the Zap multi-step and requires a paid plan. A filter has the same effect.

Connect

Connect your Perfect Wiki account

  1. 01

    Go to the Apps page

    In your Zapier account, open Apps and click + Add connection. You need an existing Perfect Wiki account, since Zapier only links accounts and never creates them for you.

  2. 02

    Select Perfect Wiki

    Type Perfect Wiki in the dialog, pick it, then click Add connection. Zapier opens a new tab so the sign-in happens on the Perfect Wiki side, not in Zapier.

  3. 03

    Sign in and grant access

    Log in to Perfect Wiki in that tab and allow Zapier into the account. The connection works with your own rights, so use an account that has access to the content your team will ask about.

First Zap

Your first Zap: answer team questions from the wiki

GoalWhen someone posts a question in a dedicated chat channel, ask the Perfect Wiki bot and post its answer to a separate channel.

  1. 01

    Pick the trigger

    Create a Zap and choose your chat app as the one that starts it, with a new message in the questions channel as the event. Perfect Wiki cannot start a Zap itself.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items from that channel, so you build the rest on a real question rather than a blank one.

  3. 03

    Ask the bot

    Add Query Knowledge Bot as the action, choose your Perfect Wiki connection, and map the message text into Query. Test it and read the answer that comes back.

  4. 04

    Post the answer

    Add a chat message as the second action and drop the bot's answer into it. Send it to a different channel than the one the trigger watches, and note this step needs a paid plan.

  5. 05

    Publish

    Click Publish to switch the Zap on. How fast it reacts depends on the chat trigger, not on Perfect Wiki. Questions posted before that moment are not picked up.

Actions

The Perfect Wiki action

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

1

Query Knowledge Bot

Action

In Zapier“Query a knowledge bot to find an answer”

Puts a question to your Perfect Wiki knowledge bot and hands its answer to the following steps, so any tool can tap what your wiki already knows.

When to use it
the same internal questions keep landing in chat or a help inbox, and the answers already live in the wiki.
Watch out
Query is required, and each successful call costs a task, so a busy channel can drain a free plan.
When it breaks

When it breaks

Zapier attaches no help article to Perfect Wiki, so these cases come from how Zapier behaves with every app, applied to this one.

With one action and no trigger, a Perfect Wiki Zap usually breaks around the edges: the trigger app, the plan, or a loop between the question and the answer. Four checks cover it. If a Zap still misbehaves after that, the Zapier troubleshooting page is the next stop.

  • The bot answers itself forever

    If the answer is posted where the trigger listens, that answer counts as a new question and the Zap sets itself off again, burning tasks fast. Reply in a different place.

  • Old questions are never answered

    A Zap only reacts to what happens after it is switched on. Questions posted before publication stay unanswered, and catching them up is a separate job.

  • The reply step will not publish

    Asking the bot and then sending the answer is a multi-step Zap. The free plan stops at one trigger and one action, so this flow needs a paid plan.

  • A flood of questions gets held back

    If the trigger app suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold those items back.
Need help

Need help automating Perfect Wiki with Zapier?

A person reads every message.

FAQ

Perfect Wiki Zapier integration: questions people ask

01Is the Perfect Wiki Zapier integration free?
Yes, the app itself is. Perfect Wiki is not one of the apps Zapier keeps for paid plans, so it runs on the free plan with 100 tasks a month. The limit is elsewhere: the free plan builds two-step Zaps only, one trigger and one action. Asking the bot already uses that action, so passing its answer to anyone else needs a second action, which makes the Zap multi-step and calls for a paid plan.
02How many tasks does a Perfect Wiki Zap use?
One task for each successful question to the bot, plus one for each other action that succeeds. The trigger never costs anything, whichever app it comes from. A Zap that asks the bot and then posts the answer spends two tasks per question. An action that fails is not counted against your plan. On a busy help channel, those tasks add up, so a filter that keeps only real questions can help, even though it makes the Zap multi-step.
03Can Perfect Wiki start a Zap in real time?
No, Perfect Wiki has no trigger on Zapier at all, so it never starts a Zap by itself. Your Zap starts in another app, and that app's trigger decides the speed. If it is an instant trigger, the app reports the event to Zapier straight away, whatever your plan. If it is a polling trigger, Zapier checks on a timer: every 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise.
04What does it take to connect Perfect Wiki to Zapier?
An existing Perfect Wiki account, with access to the content the bot should draw on. You connect once from the Apps page of Zapier: add a connection, choose Perfect Wiki, sign in on the tab that opens, and grant access. Every later Zap reuses that connection. You will also need a connection for the app that starts the Zap, since Perfect Wiki cannot be the trigger. Both connections are made the same way.
05Why would a Perfect Wiki Zap keep replying to its own answers?
Because the answer was posted where the trigger is listening. To the trigger, the bot's reply looks like one more new message, so the Zap runs again, asks the bot about its own answer, posts again, and so on. Each round costs tasks. The fix is simple: send the answer to a different channel, inbox or thread than the one the trigger watches, or filter out the Zap's own messages.
06What if the Perfect Wiki operation you need is not on Zapier?
Then Zapier cannot do it for now. The integration has a single action, Query Knowledge Bot, and no trigger or search: reacting to new wiki pages, creating or editing pages, or looking up a page directly is not available from a Zap. What does work is asking the bot from any app Zapier connects and sending the answer onward. Everything else is done inside Perfect Wiki. The bot only ever answers; it never writes to the wiki.
07Zapier, Make or n8n for Perfect Wiki?
Decide on criteria, not on a ranking. On Zapier, Perfect Wiki offers one action and no trigger, so it only ever answers questions that start elsewhere, and a useful question-and-reply flow needs a paid plan. For another tool, check whether it connects to Perfect Wiki at all, whether it can react to wiki changes, and how it bills a flow of three steps. Those answers matter more here than a general verdict.
Same platform

Other docs you might need on this stack.

Browse all integrations