Resources · Zapier integration

Planview AgilePlace Zapier integrationAutomate Planview AgilePlace with Zapier.

The Planview AgilePlace Zapier integration gives you 5 triggers, 23 actions and 1 search to drive your boards, cards and tasks from other tools. Every trigger is checked on a timer, it runs on the free plan, and here is what it costs and where it breaks.

See the 29 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Planview AgilePlace Zapier integration actually does

It links your Planview AgilePlace account to Zapier so that something happening on a board (a card created, moved or updated) starts a chain of steps elsewhere, and so that other tools can create, move, tag, block or assign cards for you. No code, and the app is not reserved for paid plans: it works from the free one.

Three results people build with it. A board that keeps itself tidy: when a card reaches your review lane, Card Entered a Specific Lane fires and Assign User puts the right reviewer on it. Intake without copy and paste: a request arriving in another tool becomes a card through Create Card, already tagged with Add Tags to a Card (Or Task). Portfolio boards that follow the work: Move Parent Cards Based on Status of Children pushes a parent card into its active lane once the first child starts, then into its done lane once every child is finished.

What Zapier does not do here. None of the 5 triggers is instant: Zapier goes and checks the board at an interval set by your plan, so a card moved now shows up in your Zap at the next check, not before. There is no trigger for a new comment, a blocked card or a finished task, only for cards created, moved, updated or entering a lane. And a Zap never picks up the cards that were already on the board before you switched it on.

If you are still choosing a tool, two comparisons sit elsewhere on the site: n8n vs Zapier and Make vs Zapier. For the platform itself, see the Zapier review.

Vocabulary

Zapier vocabulary, in plain words

Eight words come back on every line of this page. Here is what each one means for a Planview AgilePlace board.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event in an app that starts the Zap, such as a card created on a board. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once it has started: the step that writes, moves or changes something for you, like moving a card to a lane.
Task
The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan is a count of those.
Polling vs instant
A polling trigger is checked on a timer: Zapier asks the app for new items. An instant trigger is reported by the app itself, with no wait.
Filter
A step that lets the Zap carry on only when what arrived meets a condition you set, and stops it there otherwise.
Search step
A step that looks up something that already exists, say a card by its title, so the next steps can use what it found.
Connection
Your Planview AgilePlace account linked to Zapier once, then reused by every step of every Zap that touches the app.
Cost

What it really costs in tasks

The trigger costs nothing, however often Zapier checks your board. You pay in tasks, and only for actions that went through.

  • Trigger check0 tasks
  • Successful action1 task each
  • Free plan100 tasks a month, 2-step Zaps
  • App reserved for paid plansNo

Every action that succeeds counts once, so a Zap that tags a card then assigns someone eats two tasks per card. An action that fails is not counted. The free plan gives 100 tasks a month and Zaps of two steps only: one trigger, one action. Add a second action, a filter or a search and the Zap becomes multi-step, which needs a paid plan. Planview AgilePlace itself is not reserved for paid plans, so none of this needs an upgrade.

Connect

Connect Planview AgilePlace to Zapier in 3 steps

  1. 01

    Open your Apps page

    In your Zapier account, go to Apps and click + Add connection. You need an existing Planview AgilePlace account: Zapier does not create one for you along the way.

  2. 02

    Pick Planview AgilePlace

    Type the app name in the dialog, select Planview AgilePlace from the results, then click Add connection. A new tab opens on the Planview AgilePlace sign-in.

  3. 03

    Sign in and grant access

    Log in with the account whose boards you want to automate and grant Zapier access. The connection is then saved, and every Zap that touches Planview AgilePlace reuses it.

First Zap

Your first Zap: comment and assign when a card reaches a lane

GoalWhen a card enters your review lane, leave a comment on it and assign the reviewer.

  1. 01

    Pick the trigger

    Create a Zap, choose Planview AgilePlace as the app that starts it and Card Entered a Specific Lane as the event, then select the connection you saved earlier.

  2. 02

    Set the Board and the Lane

    Choose the Board from the dropdown, or enter its ID by hand, then the Lane to watch. Both are required: without the lane, the trigger has nothing to look at.

  3. 03

    Test the trigger

    Run the test. Zapier brings back the three most recent cards of the connected account, so pick a real one to map the next steps on rather than a blank sample.

  4. 04

    Add the comment

    Add Add Comment to Card (Or Task), map the card ID from the trigger into Card/Task ID and write the Comment. Test it: a real comment appears on that card.

  5. 05

    Assign the reviewer

    Add Assign User, map the same card ID and pick the user. This second action makes the Zap multi-step, so it needs a paid plan. On the free plan, keep only one action.

  6. 06

    Publish

    Publish the Zap to switch it on. From then on, each card entering the lane gets its comment and reviewer at the next check, and each Zap run costs two tasks.

Triggers

Planview AgilePlace triggers

5 events start a Zap when something happens in Planview AgilePlace. Zapier checks for them at the interval your plan allows.

1

Card Entered a Specific Lane

Polling trigger

In Zapier“Triggers when a card enters a specified lane.”

Starts your Zap each time a card lands in the one lane you point it at, whether it was dragged there or moved by another automation. It is the trigger Zapier puts forward for this app, and the most precise of the five.

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
notify a reviewer or open a follow-up card once work reaches a review or ready-to-ship lane, without reacting to every other move on the board.
Watch out
both the Board and the Lane are required, so the connected account must be able to see that board before the lane list fills in.
2

Card Created in a Specific Lane

Polling trigger

In Zapier“Triggers when a card is created in a specific lane.”

Fires on brand-new cards only, and only those created straight into the lane you chose. A card that arrives in that lane from somewhere else on the board does not count here.

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 team drops incoming requests into an intake lane and you want each new one copied into a tracking sheet or announced to the person on duty.
Watch out
if cards reach that lane by being moved rather than created, this trigger stays silent; Card Entered a Specific Lane is the one that catches moves.
3

Card Created on Board

Polling trigger

In Zapier“Triggers when a card is created anywhere on a board.”

Watches a whole board and runs the Zap for each new card, whatever lane it was created in. Zapier lists it among the featured triggers of the app.

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
keep a log of everything that enters a board, or tag and assign every new card the same way so nobody starts from a bare title.
Watch out
on a busy board this runs for every single card, so each action behind it costs a task per card; add a filter if only some of them matter, knowing a filter needs a paid plan.
4

Card Moved on a Board

Polling trigger

In Zapier“Triggers when a card moves to/from any lane on a board.”

Reacts to movement: any card leaving one lane for another anywhere on the board starts the Zap, with no need to name a lane in advance.

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
record the flow of work across a board, for example to mirror each move in another project tool used by a client or a partner team.
Watch out
a Zap that moves cards on this same board will set itself off again with every move it makes; aim its actions at another board or filter them.
5

Card Updated on Board

Polling trigger

In Zapier“Triggers when a card is updated anywhere on a board.”

The broadest of the five: an edit to any card on the board, anywhere, is enough to wake the Zap. Zapier features it on the app page.

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
push card changes out to a reporting sheet or another tool so the people who never open the board still see current information.
Watch out
pairing it with Update Card (Or Task) on the same board is the classic loop: each update made by the Zap counts as a new update, and tasks drain fast.
Actions

Planview AgilePlace actions

Planview AgilePlace gives you 23 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add a Card Type to a Board

Action

In Zapier“Adds a card type to a board if it doesn't already exist”

Gives a board a new card type, and does nothing if a type with that name is already there.

When to use it
you spin up boards for new projects and want each one to carry the same set of card types.
Watch out
it needs a Board ID and a Card Type Name, and the connected account needs write access on that board if it does not own it.
2

Add Comment to Card (Or Task)

Action

In Zapier“Add a Comment to a Card or Task”

Writes a comment on a card or a task, so context from another tool shows up where the team already looks.

When to use it
a customer replies by email and the reply should sit on the card that tracks their request.
Watch out
both the Comment and the Card/Task ID are required, so map the ID from an earlier step.
3

Add Custom Field Choice Item to Dropdown

Action

In Zapier“Add Custom Field Choice Item to Dropdown”

Puts one more option into a dropdown custom field on a board, so the list grows with your data.

When to use it
a new client signed in your CRM should become a choice in the board's client dropdown.
Watch out
it changes the board's settings, not a card, and asks for the Board ID and the Custom Field Id.
4

Add Tags to a Card (Or Task)

Action

In Zapier“Add tags to an existing card (or task).”

Stamps one or more tags on an existing card or task, separated by commas.

When to use it
label every card that comes from a given source, such as a web form, so filters on the board pick them out.
Watch out
the Card/Task ID is required; it shows in the address bar when you open the card.
5

Assign User

Action

In Zapier“Assign a User to a Card (Or Task)”

Puts a person on a card or task, chosen by email or user ID.

When to use it
the owner of a deal in your sales tool should automatically own the delivery card.
Watch out
the user list only fills in once you select a board; without one, enter the email or ID through 'Use a Custom Value'.
6

Block a Card (Or Task)

Action

In Zapier“Block a Card (Or Task)”

Marks a card or task as blocked and records why, so the board shows the hold-up at a glance.

When to use it
an invoice goes overdue in your billing tool and the matching delivery card should stop.
Watch out
the Block Reason is required; write it so the team understands it without opening another tool.
7

Create Card

Action

In Zapier“Creates a new card.”

Adds a new card to a board from whatever started the Zap: a form reply, an email, a row in a sheet.

When to use it
turn requests that arrive outside the board into cards, so the backlog lives in one place.
Watch out
the Board ID is required and is found in the address bar when you view the board.
8

Complete a Task

Action

In Zapier“Moves a task into it's taskboard 'done' lane”

Moves a task into the 'done' lane of its task board, closing it without anyone opening the card.

When to use it
a delivery confirmed in another tool should tick off the matching task on the card.
Watch out
like Start a Task, it wants both the Task ID and the Card ID of the containing card.
9

Create a Parent/Child Connection

Action

In Zapier“Creates a parent/child relationship between two cards”

Links two cards as parent and child, so the hierarchy is set without dragging connections by hand.

When to use it
each new feature card created by a Zap should hang under the epic it belongs to.
Watch out
it needs both the Parent Card ID and the Child Card ID; mixing them up reverses the link.
10

Create Task

Action

In Zapier“Create a Task Card.”

Places a task inside an existing card, with its own title and task type, so the card carries its checklist of work.

When to use it
every new client card should come with the same set of onboarding tasks.
Watch out
you need the Card ID of the parent card, and the task type list only fills in once a board is selected.
11

Duplicate a Card (Or Task)

Action

In Zapier“Duplicate a Card (Or Task)”

Copies an existing card or task, which saves rebuilding a template card by hand each time.

When to use it
a piece of work that comes back often starts from a model card you keep on the board.
Watch out
it only asks for the Card/Task ID of the one to copy, so keep that model card where it is.
12

Get Card by ID

Action

In Zapier“Gets a Card by ID”

Fetches one card from its Card ID and hands its details to the next steps of the Zap.

When to use it
a trigger from another tool carries a card ID and you need the card's content further down.
Watch out
it is an action, not a search step, so a successful run counts as a task on your plan.
13

Move Card to a Lane

Action

In Zapier“Moves a card to a different lane.”

Sends a card to another lane, one of the actions Zapier features for this app.

When to use it
a contract signed elsewhere should push the project card from proposal to in progress.
Watch out
it asks for a Lane ID, not a lane name, so note the ID of each target lane before building the Zap.
14

Move Parent Cards Based on Status of Children

Action

In Zapier“Move a parent based on children (1st child moved to an active lane moves the parents into the specified active lane. Once all children are complete, moves the parents to the specified 'done' lane)”

Lets the children drive the parent: once the first child card enters an active lane, the parent moves to the active lane you set, and once all are complete, to the done lane.

When to use it
portfolio or epic boards that should reflect team boards without manual updates.
Watch out
it requires four values: a child Card ID, the parent's Board ID and both Lane IDs.
15

Move Card to Another Board

Action

In Zapier“Move a card to another board”

Hands a card over to a different board, which suits work that passes from one team to the next.

When to use it
a request validated by sales moves to the delivery team's board.
Watch out
the account needs access to the destination board; the Board ID required here is the one you move the card to.
16

Remove Custom Field Choice Item From Dropdown

Action

In Zapier“Remove Custom Field Choice Item From Dropdown”

Takes an option out of a dropdown custom field, if it is there, keeping the list clean.

When to use it
a product is retired and should stop appearing as a choice on new cards.
Watch out
the value must match the existing option; anything else leaves the list as it was.
17

Remove Parent/Child Connection

Action

In Zapier“Removes a parent/child connection between two cards”

Breaks the link between a parent and a child card while keeping both cards.

When to use it
a piece of work is moved out of an epic's scope and should stop counting toward it.
Watch out
it removes only the connection between the two Card IDs you give, never the cards themselves.
18

Remove Tags From a Card (Or Task)

Action

In Zapier“Remove tags from an existing card (or task).”

Strips the tags you list from a card or task, leaving the others in place.

When to use it
a temporary tag like a waiting status should disappear once the client answers.
Watch out
list the tags separated by commas, and map the Card/Task ID from an earlier step: both are required.
19

Start a Task

Action

In Zapier“Moves a task card into the 'doing' lane”

Pushes a task into the 'doing' lane of its card's task board, marking it as under way.

When to use it
a time entry or a calendar event in another tool means the task has really begun.
Watch out
it needs two IDs, the Task ID and the Card ID of the card holding the task.
20

Unassign User

Action

In Zapier“Unassign a User from a Card (Or Task)”

Takes a person off a card or task without touching anyone else assigned to it.

When to use it
someone leaves a project and their open cards should be freed for reassignment.
Watch out
it needs both the user (email or ID) and the Card/Task ID; a user who is not on the card leaves nothing to remove.
21

Unblock a Card (Or Task)

Action

In Zapier“Unblock a Card (Or Task)”

Lifts the block on a card or task, with a reason that stays on record.

When to use it
the payment that held the work back comes through and the card can move again.
Watch out
the Unblock Reason is required too, so plan a short text or map one from the step that triggered the Zap.
22

Update Card (Or Task)

Action

In Zapier“Updates an existing card (or task card).”

Changes an existing card or task card, picked by its Card/Task ID. Zapier features it among the app's actions.

When to use it
a status changes in your CRM or ticketing tool and the matching card on the board should follow.
Watch out
paired with Card Updated on Board on the same board, it triggers itself in a loop.
23

Update Custom Field Value on a Card

Action

In Zapier“Update Custom Field Value on a Card”

Sets one custom field on a card to the value you give it, rather than touching the whole card.

When to use it
a budget, a client name or a score lives elsewhere and should show on the card without anyone retyping it.
Watch out
the custom field list appears once you select a board; otherwise enter the field ID by hand.
Searches

Planview AgilePlace search

1 search step looks for data that already exists in Planview AgilePlace, so a later step can use it.

A search step finds a card that already exists so later steps can work on it. On Planview AgilePlace there is one, listed under SEARCH at the bottom of the Action event list, and three settings decide what happens when the result is not what you expected.

1

Find First Matching Card

SearchFind or create

In Zapier“Finds the first matching card on a board by searching Title and Header (Custom ID).”

Looks through one board for a card whose title or header (the custom ID) matches what you type, and returns the first hit.

When to use it
before updating or commenting, find the card that carries a client's reference so you never create a duplicate.
Watch out
the editor also shows Find or Create Card; it is this same search with the create box ticked, not a separate operation, and the Zap becomes multi-step.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds no card stops the Zap there and skips what depended on it. Switched on, the Zap carries on empty-handed.
  2. Create Card if it doesn't exist yet?
    Ticking it turns the search into Find or Create Card: the setting above disappears and Zapier asks for the fields needed to create the missing card.
  3. If multiple search results are found?
    Several cards match: keep the first one (the default), stop the Zap, or hand all of them on to the next steps.
When it breaks

When the Planview AgilePlace Zap breaks

Zapier attaches no help article and no documented limit to this app. What goes wrong comes from how Zapier itself works.

These four cases cover what you will meet on a board automation. If a Zap still misbehaves, the Zapier troubleshooting page is the next stop.

  • Old cards are never picked up

    A Zap only reacts to what happens after you publish it. Cards already on the board stay untouched; moving that backlog is a separate job.

  • The Zap feeds itself

    Card Updated on Board with Update Card (Or Task), or Card Moved on a Board with Move Card to a Lane, on the same board: each change restarts the Zap and burns tasks.

  • A bulk import gets held back

    Load hundreds of cards at once and the trigger suddenly returns a huge batch. Zapier's flood protection can hold it back instead of running them all.

  • A card does not run twice

    Zapier remembers what a polling trigger has already seen, so the same new card will not start the Zap a second time, even if it reappears in a check.
Need help

Need help automating Planview AgilePlace with Zapier?

A person reads every message.

FAQ

Planview AgilePlace Zapier integration: FAQ

01Is the Planview AgilePlace Zapier integration free?
Yes, Planview AgilePlace is not reserved for paid plans, so it works on the free Zapier plan. That plan gives you 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger and one action. The moment you add a second action, a filter or a search step, the Zap becomes multi-step and needs a paid plan. Commenting on a card and assigning a user in the same Zap is already two actions, so plan for that before you build.
02How many tasks does a Planview AgilePlace Zap use?
One task per action that succeeds, and nothing for the trigger. Zapier can check your board as often as your plan allows without spending anything, because looking for new cards is free. Only completed actions are billed. A Zap that tags a card, assigns a user and adds a comment uses three tasks for every card it handles. An action that fails is not counted. Get Card by ID is an action too, so each successful run of it costs a task.
03Is the Planview AgilePlace trigger real time?
No. All 5 Planview AgilePlace triggers are polling triggers: Zapier goes to check the board at an interval set by your plan. That interval is 15 minutes on Free, 2 minutes on Professional and 1 minute on Team and Enterprise. On paid plans you can also run a check by hand from the editor. The type of trigger is decided by the app, so no setting in Zapier turns one of these into an instant trigger.
04What does connecting Planview AgilePlace to Zapier require?
An existing Planview AgilePlace account, plus access to the boards the Zap will touch. Read access is enough to watch a board, and write access is needed on any board you do not own if the Zap changes cards there. The connection itself happens from the Apps page of Zapier: add a connection, pick the app, sign in to Planview AgilePlace in the tab that opens and grant Zapier access.
05Why does a Card Updated on Board Zap keep running?
Most likely because it writes back to the board it watches. If the action updates, moves or tags a card on that same board, the change counts as a new update, the trigger picks it up at the next check, and the Zap runs again. Each round costs tasks. Point the action at another board, or add a filter that lets through only the updates you care about, keeping in mind that a filter needs a paid plan.
06What if the Planview AgilePlace operation you need is not listed?
Combine what exists. The app offers 29 operations, and several gaps close by chaining them: Find First Matching Card or Get Card by ID to fetch a card, then Update Card (Or Task) or Update Custom Field Value on a Card to change it. There is no trigger for a new comment or a blocked card, so a Zap cannot start on those. If a step truly does not exist, Zapier cannot do it for this app today.
07Zapier, Make or n8n for Planview AgilePlace?
Decide on criteria rather than names. On Zapier, check three things against your use: whether the 23 actions cover what you want to change on your boards, whether reacting at the next check (15 minutes on Free, 1 to 2 minutes on paid plans) is fast enough, and whether your Zaps fit in two steps or justify a paid plan. Then hold the other tools to the same three questions, using their own documentation for Planview AgilePlace.
Same platform

Other docs you might need on this stack.

Browse all integrations