Resources · Zapier integration

Placker Zapier integrationAutomate Placker with Zapier.

Placker Zapier integration: 3 triggers, 4 actions and 3 searches. All three Placker triggers are instant, so a card, comment or label event starts your Zap right away, even on the free plan. Here is what each operation does, what it costs and where it breaks.

See the 10 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Placker Zapier integration actually does

The Placker Zapier integration links your Placker boards to the other tools you use, without code. Something happens on a board (a card moves, a comment lands, a label changes), and Zapier reacts by creating, labelling or updating cards, or by sending that information to another app. Placker is a planning and tracking tool; Zapier is the glue around it.

Three outcomes cover most of what people build. First, a triage lane: a label added to a card fires Label Related Events, and the Zap answers with Update Card or Add Label to Card, so one tag sets off the rest of the routine. Second, cards born elsewhere: a form, an inbox or a CRM starts the Zap, and Create Card drops a new card on the list you chose. Third, a comment feed: Comment Related Events picks up each comment added, edited or deleted, and passes it to whatever tool your team reads.

The good news for anyone on the free plan: every Placker trigger is instant. The plan's checking interval never applies to them.

What Zapier does not do here: there is no action to delete or archive a card, none to create a board, a list or a label, and no action that writes a comment. Watching those events is possible, changing them is not. The searches read cards and board labels, nothing more.

If you are still weighing the platform itself, the Zapier review is a good place to start.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on every line of this page. Here they are in plain English.

Zap
The automation you build in Zapier: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event and nothing else.
Action
What the Zap does after it starts: the step that writes, sends or moves something on your behalf, such as creating a card.
Task
The unit Zapier bills. One task is one action your Zap carried out successfully; your plan counts those, nothing else.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment the event happens.
Filter
A step that lets the Zap continue only when the incoming data meets a condition you set, and quietly stops it otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can reuse what it found.
Cost

What a Placker Zap really costs

Placker is not reserved for paid plans: it works on the free plan from day one.

  • Free plan100 tasks a month
  • Steps on the free plan2 (one trigger, one action)
  • Trigger0 task
  • Placker triggers3 instant, 0 polling

The trigger never costs a task, and neither does Zapier listening for new events. Only an action that went through is billed, one task per successful action, so a Zap with three actions costs three times more per run than a Zap with one. An action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap stays at two steps: one trigger, one action. Add a filter, a search or a second action and the Zap becomes multi-step, which needs a paid plan. The interval grid on the right only matters for polling triggers; Placker has none.

Connect

Connect Placker to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A connection is your Placker account linked once to Zapier, then reused by every step that touches Placker.

  2. 02

    Find Placker

    Type Placker in the search box of the dialog, pick it from the results, then click Add connection. A new tab then opens on the Placker side, where you finish the sign-in.

  3. 03

    Sign in and grant access

    Log in to Placker in that tab and allow Zapier to reach the account. You need a Placker account, plus read or write access on any board you do not own and want the Zap to touch.

First Zap

Your first Placker Zap, step by step

GoalWhen a label is added to a card on your board, keep only the label you care about, then update that card.

  1. 01

    Build: pick the trigger

    Create a Zap, choose Placker as the app that starts it and Label Related Events as the event. Select your Placker connection.

  2. 02

    Set the board

    Pick the Board to watch: the field is required. The trigger covers labels added and labels removed, which is why the next step matters.

  3. 03

    Test the trigger

    Run the test. Zapier brings back the three most recent label events of that board, so you map the next steps on a real one rather than on a guess.

  4. 04

    Add the filter

    Add a Filter step from the plus icon and set the condition that matches your label. This makes the Zap multi-step, so it needs a paid plan.

  5. 05

    Add Update Card

    Add the action Update Card, map the Card's id from the trigger, then set what should change. Test the step and read what came back.

  6. 06

    Publish

    Click Publish to switch the Zap on. From that point on, each label event that passes the filter updates its card and uses one task.

Triggers

Placker triggers

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

1

Card Related Events

Instant trigger

In Zapier“Triggers when card is created, removed, archived, unarchived or card status is changed. You can fetch card details to retrieve more card data.”

Starts the Zap whenever a card on the chosen board goes through a lifecycle change: it is created, removed, archived, brought back from the archive, or its status changes. One trigger for the whole life of a card, which keeps your Zap list short.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you want a status change on a delivery board to show up in your reporting tool or your client channel without anyone copying it.
Watch out
the Board field is required, and the event covers several kinds of change at once, so a filter is often needed to keep only the one you want.
2

Comment Related Events

Instant trigger

In Zapier“Triggers when a comment is added, updated or deleted. You can fetch card details to retrieve more card data.”

Fires on the conversation layer of your board: a comment added to a card, edited later, or deleted. The Zap receives the comment event and can then fetch the full card with a search if it needs more than what came in.

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 client or a teammate comments on a card and the account manager should see it in the tool they actually check.
Watch out
edits and deletions start the Zap too, not just new comments, and a Board must be chosen before the test can run.
3

Label Related Events

Instant trigger

In Zapier“Triggers when label is added or removed from a card. You can fetch card details to retrieve more card data.”

Reacts when a label is put on a card or taken off it. Labels are often how a team flags urgency, ownership or a stage, so this trigger turns a single click on a tag into the start of a whole routine.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
tagging a card as blocked should alert the lead and update the card in one go.
Watch out
removing a label fires it as well. If your Zap adds or removes labels on the same board, it can set itself off again.
Actions

Placker actions

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

1

Add Label to Card

Action

In Zapier“This action allows to add selected label to card”

Sticks one of your board labels on a card. Zapier highlights it as the featured Placker action, and it is the quickest way to make another tool's event visible on the board.

When to use it
an overdue invoice in accounting should tag the client card so the project lead spots it.
Watch out
it needs the Card's id and the Label's id; Get Board Labels gives you the second one.
2

Create Card

Action

In Zapier“This action allows to create card on a selected list”

Puts a new card on the list you select, with the title you give it. This is the entry door for work that starts outside Placker: a form reply, a support request, a signed deal.

When to use it
every new lead from your form should become a card on the intake list of your sales board.
Watch out
both the List and the Card's title are required, so map a title that is never empty.
3

Remove Label From Card

Action

In Zapier“This action allows to remove selected label from card”

Takes a label off a card, the mirror of Add Label to Card. Useful to clear a flag automatically once the reason for it is gone.

When to use it
a ticket closed in your helpdesk should lift the waiting label from the related card.
Watch out
this change fires Label Related Events, so a Zap watching labels on the same board can loop.
4

Update Card

Action

In Zapier“This action allows to update a selected card”

Changes an existing card that you point to by its id. Nothing is created, the card stays where it is and keeps its history.

When to use it
a payment confirmed in your billing tool should update the matching card on the project board.
Watch out
the Card's id is required. If no earlier step carries it, add Get Card Details or Search Cards first.
Searches

Placker searches

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

A search step finds something that already exists in Placker and hands it to the next steps. In the editor, Placker searches sit at the bottom of the Action event list, under SEARCH. Adding one makes the Zap multi-step. Three settings decide what happens when the result is not what you expected. Placker offers no find-or-create variant.

1

Get Board Labels

Search

In Zapier“Get labels available on Board.”

Reads the labels available on a board, so later steps can pick the right one by name instead of hard-coding it.

When to use it
before Add Label to Card or Remove Label From Card, to get the Label's id they require.
Watch out
it asks for the Board's id, not the board name you see on screen.
2

Get Card Details

Search

In Zapier“Get single card details by id.”

Fetches one card in full from its id. The three triggers suggest exactly this: start from the event, then pull the whole card when the event alone is too thin.

When to use it
a comment arrives and your message to the team needs the card's title and context.
Watch out
the Card's id is required; without it there is nothing to look up.
3

Search Cards

Search

In Zapier“Search cards by given criteria.”

Looks for cards matching the criteria you give, when you do not have an id at hand but know what the card should contain.

When to use it
an email from a client should find their existing card before Update Card runs.
Watch out
several cards can match, so check the multiple-results setting before you publish.

The three settings every search exposes

  1. Successful if no search results are found?
    Left as is, a search that finds nothing stops the Zap there and the dependent steps are skipped. Turned on, the Zap carries on with nothing in hand.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Placker has none, so you will not see it on these three searches.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or pass all of them on together.
When it breaks

When a Placker Zap breaks

Zapier links no help article to Placker, so the known failure points are the ones every Zap shares. With Placker, two of them hit harder than usual.

Most breakdowns come from the Zap's own design, not from Placker going down. Read the four cases below before publishing, and keep the Zapier troubleshooting page at hand.

  • No backfill of existing cards

    A Zap only reacts to what happens after you switch it on. Cards, comments and labels already on the board are never picked up; moving that backlog is a separate job.

  • The label loop

    A Zap that adds or removes labels on the board its label trigger watches fires itself again and again, and burns through your tasks fast. Watch one board, write on another, or filter.

  • Card changes that feed back

    Create Card on a board watched by Card Related Events starts that trigger. Two Zaps built that way can keep restarting each other.

  • Bulk changes get held back

    After an import or a big cleanup, a sudden batch of events can be paused by Zapier's flood protection instead of running in one burst.
Need help

Need help automating Placker with Zapier?

A person reads every message.

FAQ

Placker Zapier integration: FAQ

01Is the Placker Zapier integration free?
Yes, Placker works on the free Zapier plan, since Zapier does not reserve it for paid plans. The free plan gives you 100 tasks a month and as many Zaps as you like. The catch is the shape of those Zaps: on the free plan each one is limited to two steps, a single trigger and a single action. Once you add a filter, a search such as Get Card Details, or a second action, the Zap becomes multi-step and needs a paid plan. A simple Label Related Events to Update Card Zap stays free.
02How many tasks does a Placker Zap use?
One task per action that completes successfully, and nothing for the trigger. A Zap that fires on Card Related Events and then runs Create Card in another tool uses one task per run. A Zap with three actions uses three. An action that fails is not billed, and Zapier listening for Placker events costs nothing either. The real risk is volume from loops: a Zap that changes labels on the board its own label trigger watches can run again and again, and each run costs tasks.
03Do Placker triggers run in real time?
Yes. All three Placker triggers are instant: Placker tells Zapier when the event happens, and the Zap starts right away. The plan's checking interval, which runs from 15 minutes on Free down to 1 minute on Team and Enterprise, only applies to polling triggers, and Placker has none. So on the free plan, a Placker Zap reacts as fast as on a paid one. In the editor, a Zap built on an instant trigger shows a lightning bolt.
04What does it take to connect Placker to Zapier?
A Placker account, and access to the boards the Zap will read or change. If a board belongs to someone else, your account needs read or write rights on it, otherwise the Zap cannot reach it. The connection itself is made from the Apps page of Zapier with + Add connection, then a sign-in to Placker in the tab that opens, where you grant Zapier access. The connection is then reused by every Placker step.
05Why does a Placker label Zap keep running on its own?
Because Label Related Events fires on labels added and removed, and Add Label to Card or Remove Label From Card produce exactly those events. If the Zap writes labels on the board its trigger watches, every action starts the Zap again. The fix is in the design: watch one board and act on another, or add a filter so the Zap only goes on for a specific label it never writes itself. A filter makes the Zap multi-step, so it needs a paid plan.
06What if the Placker operation you need is not in Zapier?
Then it is not available through this integration, and no setting will reveal it. Zapier offers 3 triggers, 4 actions and 3 searches for Placker: there is no action to archive or delete a card, to write a comment, or to create a board, a list or a label. Two routes remain. Combine what exists, for example Search Cards then Update Card. Or handle that part by hand in Placker, and let the Zap cover the rest of the routine.
07Zapier, Make or n8n for Placker?
Judge on criteria, not on brand. On Zapier, Placker offers 3 instant triggers, which start the Zap right away even on the free plan, 4 actions centred on cards and labels, and 3 searches. Check that the operations you need are in that list, count the actions per run since each successful one is a task, and check whether your Zaps need a filter or a search, which requires a paid plan. Then compare those same three points on the other platforms.
Same platform

Other docs you might need on this stack.

Browse all integrations