Resources · Zapier integration

Perdoo Zapier integrationAutomate Perdoo with Zapier.

The Perdoo Zapier integration gives you 7 triggers, 4 actions and 6 searches. That is 17 ways to connect your goals tool to everything else: new objectives, KPIs and meeting action items flow out, fresh numbers and finished action items flow back in.

See the 17 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Perdoo Zapier integration is good for

Perdoo is where a company writes down its strategy and tracks it: objectives, key results, KPIs, initiatives, plus the 1:1s and meetings around them. Connected to Zapier, it can announce what gets created there and accept progress updates from your other tools, so the numbers in Perdoo stop depending on someone remembering to type them in.

Three results teams usually build. First, meeting follow-up that actually happens: New Meeting Action Item sends each action item to the task manager people already check every day. Second, KPIs that update themselves: Update KPI writes a new value coming from a spreadsheet, a CRM or a finance tool into the right KPI, so the dashboard reflects the source rather than last month's copy-paste. Third, onboarding without gaps: New User adds every newcomer to an onboarding list or a welcome message.

What Zapier does not do here matters just as much. Every action is an update: you cannot create an objective, a key result or a KPI from a Zap, and nothing can be deleted. Updates also need the ID of an item that already exists in Perdoo, which shapes how you build every Zap that writes back. And none of the seven triggers is instant, so each one waits for Zapier's next check.

Before deciding how far to take this, the Zapier review and the Make vs Zapier comparison are worth a look.

Vocabulary

Zapier vocabulary in one minute

Eight terms carry this whole page. Here they are without the jargon.

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. With Perdoo, that is always something new being created: a group, a goal, a KPI, a user.
Action
What the Zap does once it starts: the step that writes, sends or moves something for you. Perdoo's four actions all update.
Task
What Zapier bills you for: one action your Zap completes successfully. Your plan is a monthly count of those.
Polling trigger
A trigger Zapier checks on a timer, keeping only what it has not seen yet. All seven Perdoo triggers work this way.
Instant trigger
A trigger the app reports itself, the moment the event happens. Perdoo offers none on Zapier, which is worth knowing upfront.
Filter
A step that lets the Zap continue only if what arrived meets your condition, and stops it there otherwise.
Search step
A step that looks up something already in an app, so later steps can use what it found. Perdoo has six of them.
Cost

What a Perdoo Zap really costs

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

  • TriggerFree, never counted
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Search or filterMakes the Zap multi-step, paid plan

The trigger never costs a task, and Zapier checking Perdoo for new items costs nothing either. You pay for each action that succeeds, one task each; a failed action is not counted. The free plan gives you 100 tasks a month and two-step Zaps only: one trigger, one action. That limit bites fast with Perdoo, because writing back usually means finding the right item first. A search or a filter makes the Zap multi-step, and multi-step needs a paid plan. On the free plan, Zapier checks your triggers every 15 minutes.

Connect

Connect your Perdoo account

  1. 01

    Open the Apps page

    In Zapier, go to Apps and click + Add connection. You need an existing Perdoo account: Zapier links accounts, it does not create them. Keep that account's login at hand for the next step.

  2. 02

    Pick Perdoo

    Type Perdoo in the dialog, select it, then click Add connection. Zapier opens a new tab, and the rest of the connection happens there, on the Perdoo side.

  3. 03

    Sign in and allow access

    Log in to Perdoo in that tab and grant Zapier access. The connection sees and changes what your Perdoo login can see and change, no more. Goals owned by other people need at least read access, and write access if a Zap is going to update them.

First Zap

Your first Zap: turn meeting action items into tasks

GoalEach new action item agreed in a Perdoo meeting becomes a task in your project tool, and its owner gets a direct message.

  1. 01

    Set the trigger

    Create a Zap, choose Perdoo as the app that starts it and New Meeting Action Item as the event, then pick your Perdoo connection.

  2. 02

    Test on a real item

    Run the trigger test. Zapier brings back the three most recent action items from your account, so you map the next steps on a real one, not on a blank sample.

  3. 03

    Create the task

    Add your project tool as the action, choose the project, and drag the action item's details into the task. Test the step and open the task it created.

  4. 04

    Notify the owner

    Add the chat message as a second action. This makes the Zap multi-step, so it needs a paid plan; on the free plan, stop at the task.

  5. 05

    Publish

    Click Publish. From then on, Zapier checks Perdoo on your plan's interval and turns every new action item into a task. No backlog is replayed.

Triggers

The 7 Perdoo triggers

7 events start a Zap when something happens in Perdoo. Zapier checks for them at the interval your plan allows.

1

New Group

Polling trigger

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

Fires when someone creates a group in Perdoo, the unit that teams and departments use to own goals. Handy when a new team appearing in your goals tool should also appear elsewhere, in a channel list or an org chart sheet.

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 reorganisation creates new teams and you want each one logged in the shared directory without chasing anyone.
Watch out
renaming an existing group is not a new group, so it will not start the Zap.
2

New Initiative

Polling trigger

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

Initiatives are the projects people commit to in order to move a key result. This trigger picks up each one created in Perdoo and hands it to your Zap, which is the natural bridge between the goal and the place the work really gets planned.

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
every new initiative should open a matching project or board in the tool your delivery team uses.
Watch out
initiatives created before the Zap was published stay out; move those by hand.
3

New Key Result

Polling trigger

In Zapier“Triggers when a new Key Result is created.”

Each key result added under an objective arrives in your Zap with this trigger. It earns its keep at planning time, when many measurable targets appear at once and the people who report on them need to know.

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
you keep a reporting sheet per quarter and want every new key result to get its own row there.
Watch out
pasting a whole quarter's plan in one go can trip Zapier's flood protection.
4

New KPI

Polling trigger

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

KPIs are the health metrics you watch continuously, as opposed to goals with an end date. When one is added in Perdoo, this trigger passes it on, which helps keep the list of tracked metrics consistent between Perdoo and wherever the data really lives.

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 data team needs a heads-up each time a new metric is tracked, so they can wire its source.
Watch out
a value change on a KPI is not a new KPI and will not fire it.
5

New Meeting Action Item

Polling trigger

In Zapier“Triggers when a new Meeting Action Item is created.”

Catches each action item recorded in a Perdoo meeting, from a 1:1 or a team check-in. That is usually the most valuable trigger of the seven, because action items are exactly what gets lost between one meeting and the next.

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
people live in a task manager, not in Perdoo, and decisions should land where they actually work.
Watch out
closing the task elsewhere does not close the item in Perdoo unless a second Zap uses Update Meeting Action Item.
6

New Objective

Polling trigger

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

Objectives sit at the top of the goal tree: the qualitative ambition the key results measure. With this trigger, every new objective becomes an event you can broadcast, archive or turn into a planning document somewhere else.

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
leadership sets company objectives and you want the whole team to see each one posted in a shared channel.
Watch out
a filter step before the announcement helps keep only the objectives meant for everyone, and makes the Zap multi-step.
7

New User

Polling trigger

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

Spots every person added to your Perdoo account. Zapier features this one on the app page, and it suits HR and operations work: whoever joins the goals tool usually needs to exist in a few other places too.

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
new hires get Perdoo access on day one and you want a welcome message or an onboarding checklist to follow.
Watch out
users invited before publication never come through, so check older invites by hand.
Actions

The 4 Perdoo actions

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

1

Update Initiative

Action

In Zapier“Update an existing Initiative (via its goal ID).”

Writes a new value on an initiative that already exists, so the project's progress in Perdoo follows what happens in your delivery tool.

When to use it
an initiative tracks a migration and the project board knows how far along it is.
Watch out
the Initiative ID is required; without it, the Zap cannot tell which initiative to touch.
2

Update KPI

Action

In Zapier“Update an existing KPI (via its goal ID).”

Pushes a fresh figure into an existing KPI, so Perdoo shows the number your finance or sales tool already knows. Zapier features it on the app page.

When to use it
monthly revenue sits in a spreadsheet and should land in Perdoo without retyping.
Watch out
it needs the KPI ID and a New Value, both required.
3

Update Meeting Action Item

Action

In Zapier“Update an existing Action Item (via its ID).”

Changes an existing meeting action item, mainly to tick it done through the Complete field, so the next meeting does not reopen what is already finished.

When to use it
the matching task gets closed in your project tool and Perdoo should reflect it.
Watch out
Meeting Action Item and Complete are both required.
4

Update Key Result

Action

In Zapier“Update an existing Key Result (via its goal ID).”

Moves the progress of a key result forward with the value you map, which keeps the goal tree honest between check-ins.

When to use it
a key result counts signed deals and your CRM already counts them for you.
Watch out
Key Result ID and New Value are both required, and the key result must already exist.
Searches

The 6 Perdoo searches

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

A search step looks up something that already exists in Perdoo and hands it to the steps after it. In the editor, searches sit at the bottom of the action event list, under their own SEARCH heading. Four of them look up by ID, which means you already need the ID; Find User and Find Group are the two that start from a human value.

1

Find User

Search

In Zapier“Find a user based on his/her email.”

Looks up a Perdoo user from an email address, one of the two searches here that start from something people actually know.

When to use it
a form or an HR tool gives you an email and the next step needs the matching Perdoo person.
Watch out
the Email field must match exactly, so a typo or an alias returns nothing.
2

Find Group

Search

In Zapier“Find a group based on its name.”

Finds a group from its name, handy when another tool talks about teams by name rather than by ID.

When to use it
a request comes in tagged with a department and the Zap needs the Perdoo group behind it.
Watch out
the Group Name is required, and a name spelled differently in another tool can make it come back empty.
3

Find Initiative

Search

In Zapier“Find an Initiative by its (goal) ID.”

Retrieves an initiative from its ID, so later steps can read what Perdoo holds on it before acting.

When to use it
you store initiative IDs in a project tool and want their current details in a status report.
Watch out
the Initiative ID is required; this search does not look up by title.
4

Find Key Result

Search

In Zapier“Find a Key Result by its (goal) ID.”

Brings back a key result when you already hold its ID, typically saved earlier in a sheet or a CRM record.

When to use it
before updating progress, you want to check the key result still exists.
Watch out
Key Result ID is required, so the ID has to be stored somewhere an earlier step can read it.
5

Find KPI

Search

In Zapier“Find a KPI by its (goal) ID.”

Pulls a KPI by ID so its current state can feed a message, a report or a comparison with your source data.

When to use it
a weekly digest Zap posts selected KPIs to a leadership channel.
Watch out
the KPI ID is required and has to be stored somewhere the Zap can reach.
6

Find Objective

Search

In Zapier“Find an Objective by its (goal) ID.”

Fetches an objective from its ID, which lets a Zap attach the right ambition to whatever it produces next.

When to use it
a planning document should quote the objective an initiative belongs to.
Watch out
Objective ID is required, and adding this step makes the Zap multi-step.

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 depend on it. Switched on, the Zap carries on without the result.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. None of Perdoo's six searches offers it on Zapier, so a missing item is never created for you.
  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 hand all of them on at once.
When it breaks

When it breaks

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

Most Perdoo Zaps fail for structural reasons, not random ones: an ID that is missing, a plan that blocks the second step, a trigger that waits for its next check. Six cases cover nearly everything. For the rest, the Zapier troubleshooting page is the next stop.

  • The update cannot find its target

    Update actions need the ID of an existing item. If no earlier step carries it, add a search first, which makes the Zap multi-step and pushes it onto a paid plan.

  • Nothing happens for several minutes

    All seven triggers are polling ones. On the free plan Zapier checks every 15 minutes, so a delay right after creating an objective is normal, not a fault.

  • Old goals never come through

    A Zap only reacts to what is created after it is switched on. Objectives, KPIs and users that existed before stay out, and moving them is a separate job.

  • A bulk import stalls the trigger

    Creating a whole quarter of key results at once makes the trigger return a huge batch, which Zapier's flood protection can hold back.

  • Edits do not fire anything

    Zapier remembers what a polling trigger has already seen, so the same item never starts the Zap twice. Edits to an existing goal are not new items.

  • A Zap that keeps restarting

    A Zap that writes into the very place its trigger watches sets itself off again and burns tasks. Keep update actions on items your trigger does not watch.
Need help

Need help automating Perdoo with Zapier?

A person reads every message.

FAQ

Perdoo Zapier integration: common questions

01Is the Perdoo Zapier integration free?
Yes, as far as Zapier goes. Perdoo is not one of the apps Zapier keeps for paid plans, so the free plan can run it with 100 tasks a month. The catch is the shape of the Zap: the free plan stops at one trigger and one action. Sending new action items to another tool fits. Writing back into Perdoo often needs a search step to find the right ID first, and that turns the Zap multi-step, which requires a paid plan.
02How many tasks does a Perdoo Zap use?
One per action that succeeds. The trigger is never counted, and Zapier checking Perdoo for new items costs nothing however often it looks. A Zap that turns each new action item into one task in your project tool spends one task per item. Add a chat message as a second action and each item costs two. A failed action, for example an update that could not find its KPI, is not counted against your plan.
03Does Perdoo trigger Zaps in real time?
No. All seven Perdoo triggers are polling triggers: Zapier goes and checks Perdoo at a fixed interval and keeps only what it has not seen before. How often depends on your plan: every 15 minutes on Free, every 2 minutes on Professional, every minute on Team and Enterprise. On paid plans the interval can be changed, and a check can also be run by hand from the editor when you are testing.
04What does it take to connect Perdoo to Zapier?
An existing Perdoo account, and enough rights on the goals your Zaps will touch. The connection is made once from the Apps page of Zapier: add a connection, pick Perdoo, sign in on the tab that opens, grant access. After that, every Zap reuses it. Read access is enough for triggers on goals you do not own; any Zap that updates those goals needs write access too. One connection serves all your Perdoo Zaps.
05Why do the Perdoo update actions keep asking for an ID?
Because every Perdoo action on Zapier updates an item that already exists, and it needs that item's ID to know which one. Initiative ID, KPI ID and Key Result ID are required fields, alongside the New Value. The ID can come from an earlier step that already carries it, or from a search step such as Find KPI. Remember that a search makes the Zap multi-step. Storing IDs in a sheet is a simple way to keep them reachable.
06What if the Perdoo operation you need does not exist on Zapier?
Then Zapier cannot do it for now. The integration offers 7 triggers, 4 actions and 6 searches, and the actions only update: creating an objective, a key result or a KPI, or deleting anything, is not available from a Zap. A workable pattern is to react to what Perdoo creates and keep the creation step inside Perdoo itself. Checking the Perdoo app page on Zapier from time to time shows whether new operations have appeared.
07Zapier, Make or n8n for Perdoo?
Decide on criteria, not on a winner. On Zapier, Perdoo comes ready with 17 operations, all triggers polling and all actions updates. Check whether the other tool connects to Perdoo at all, whether it can create goals rather than only update them, how quickly it notices new items, and how it bills a flow that needs a lookup before writing. Those answers matter more for Perdoo than any general ranking.
Same platform

Other docs you might need on this stack.

Browse all integrations