Resources · Zapier integration

LoopedIn Zapier integrationAutomate LoopedIn with Zapier.

LoopedIn Zapier integration: 0 triggers, 9 actions, 0 searches. LoopedIn never starts an automation by itself, but any other app can feed it. Ideas, roadmap cards and announcements get created, updated or deleted from what happens elsewhere.

See the 9 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the LoopedIn Zapier integration actually does

The LoopedIn Zapier integration lets another app write into your LoopedIn workspace. Zapier watches a tool you already use, and when something happens there, it creates, updates or deletes an idea, a roadmap card or an announcement in LoopedIn. Traffic only goes one way: LoopedIn receives, it never sends.

Three results come out of it. Feedback that lands on the board by itself: each entry collected in another tool becomes an idea through Create Idea, with its value and effort scores already filled in. A roadmap that follows the work: Create Roadmap Card opens a card in the column you pick, and Update Roadmap Card changes its title, column or objective later. A changelog with less copy-paste: Create Announcement drafts the post, Update Announcement changes its status or visibility, and Delete Announcement takes it down.

What Zapier does not do here matters just as much. LoopedIn has no trigger on Zapier, so nothing that happens inside LoopedIn can start an automation. It has no search either. To update or delete an item, the automation needs that item's ID from an earlier step: it cannot look it up by its title.

Picking the tool is a separate question. For the criteria that set Zapier apart from the other two big names, read n8n vs Zapier and Make vs Zapier.

Vocabulary

Zapier words, in plain English

Eight words come back on every line below. Here is what each one means in practice.

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 in an app that starts the Zap. Once the Zap is on, Zapier waits for it. LoopedIn has none, so another app provides it.
Action
What the Zap does once started: the step that writes something for you. All nine LoopedIn operations are actions.
Task
The unit Zapier bills: one action your Zap completes successfully. The number on your plan counts those, nothing else.
Polling vs instant
A polling trigger is checked on a timer for new items. An instant trigger is reported by the app the moment the event happens.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Connection
Your LoopedIn account linked to Zapier once, then reused by every step that writes into LoopedIn.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes it one, and it then needs a paid plan.
Cost

What a LoopedIn Zap really costs

LoopedIn is not a premium app, so it works on the free plan. The bill is counted in tasks, and only the LoopedIn actions that succeed are counted.

  • Trigger0 task
  • Each successful LoopedIn action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo

The trigger of the other app costs nothing, however often Zapier checks it. Each LoopedIn action that goes through costs one task, and an action that fails is not counted. The free plan gives 100 tasks a month and builds Zaps of two steps only: one trigger, one action. Add a filter or a second LoopedIn action and the Zap becomes multi-step, which needs a paid plan. The grid below applies to the trigger of the app that starts the Zap, never to LoopedIn, which has no trigger.

Connect

Connect LoopedIn 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 LoopedIn account first, with write access to any workspace you do not own yourself.

  2. 02

    Pick LoopedIn

    Type LoopedIn in the search box of the dialog, select it in the list of results, then click Add connection. A new browser tab opens on the LoopedIn side.

  3. 03

    Sign in and allow access

    Sign in to LoopedIn in that tab and grant Zapier access to the account. The connection then shows up in Apps, and every LoopedIn step of every Zap reuses it.

First Zap

Your first Zap: form entries become ideas

GoalEach new entry in your form tool lands in LoopedIn as an idea, once it passes a filter you define.

  1. 01

    Start from the form tool

    Build the Zap from its first step: pick your form tool and its new-entry event as the trigger. LoopedIn cannot start a Zap itself, so it comes second.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent entries of the connected account, so you map the next steps on a real one instead of a guess.

  3. 03

    Add the filter

    Add a Filter step from the plus icon and fill its three boxes: the field to look at, the rule, the value. This step makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add Create Idea

    Pick LoopedIn and Create Idea. Choose the workspace, map the entry into Title, then set Value and Effort on the scale the field help gives.

  5. 05

    Test, then publish

    Test the action and check the new idea in LoopedIn. If it looks right, click Publish: from then on, each new entry that passes the filter becomes an idea.

Actions

The 9 LoopedIn actions

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

1

Create Announcement

Action

In Zapier“Create a Announcement to your Workspace in loopedin.”

Drafts a new post in a LoopedIn workspace, with its title, its category and its visibility set from the Zap.

When to use it
a release noted in another tool should become a changelog entry without anyone retyping it.
Watch out
Category Id and Public are both required, so the category has to exist in LoopedIn before the first run.
2

Create Idea

Action

In Zapier“Creates a new idea to loopedin.”

Adds a fresh idea to the workspace of your choice, scored for value and effort straight away.

When to use it
feedback collected outside LoopedIn should join the board where the team already sorts requests.
Watch out
Value expects a number from 1 to 5 and Effort a number from 0 to 5, and the field help says a blank one counts as 0.
3

Create Roadmap Card

Action

In Zapier“Create a Roadmap Card to you workspace in loopedin.”

Opens a card on a LoopedIn roadmap, placed in a column and tied to an objective.

When to use it
a piece of work approved elsewhere should show up on the public roadmap in the right column.
Watch out
Workspace Id, Column, Objective and Title are required, so the column and the objective have to exist in LoopedIn before the first run.
4

Delete Announcement

Action

In Zapier“Delete Announcement from you workspace in loopedin.”

Removes an announcement from the workspace for good, picked by its ID.

When to use it
a release cancelled in another tool should take its changelog post down as well.
Watch out
there is no search on LoopedIn, so the Announcement ID must come from an earlier step or be typed in by hand.
5

Delete Idea

Action

In Zapier“Deletes a idea in loopedin.”

Erases one idea, named by its Idea Id, which is the only field the step asks for.

When to use it
a duplicate flagged somewhere else should vanish from the board too.
Watch out
deleting is not archiving. If the idea should stay visible as done, Update Idea with Archive is the softer move.
6

Delete Roadmap Card

Action

In Zapier“Delete Roadmap Card to you workspace in loopedin.”

Pulls a card off the roadmap entirely, using the Roadmap Card Id you hand it.

When to use it
work dropped in your planning tool should not linger on the roadmap readers follow.
Watch out
nothing on Zapier finds a card by its title, so the ID has to come from an earlier step or be typed in.
7

Update Announcement

Action

In Zapier“Update announcement to loopedin.”

Rewrites an existing announcement: its title, category, status and whether the public sees it.

When to use it
the status or visibility of an announcement should follow what changes in another tool, without anyone editing it by hand.
Watch out
all five fields are required, including the ID. Leave one unmapped and the step will not run, so carry the current values along.
8

Update Idea

Action

In Zapier“Updates a idea to loopedin.”

Changes an idea already on the board, down to marking it completed or sending it to the archive.

When to use it
work closed in another tool should close the matching idea on the board too.
Watch out
every field is required, Completed and Archive included. The field help says a blank Value or Effort falls back to 0, which can wipe a score you set by hand.
9

Update Roadmap Card

Action

In Zapier“Create a Update Roadmap Card to lopedin.”

Moves or renames a roadmap card by its ID: another column, another objective, another title, or a change in visibility.

When to use it
a status change elsewhere should push the card one column further on the roadmap.
Watch out
the workspace, column, objective, title and Public setting are asked again on every update, not only the part that changed.
When it breaks

When a LoopedIn Zap breaks

Zapier ties no help article to LoopedIn, and no limit specific to the app is documented. What breaks comes from how Zapier itself works.

Four cases come back most often. Each one has its fix, and the Zapier troubleshooting page goes further when a Zap stops for a reason not listed here.

  • Old entries never arrive

    A Zap only reacts to what happens after you publish it. Ideas or cards that should have existed before need a separate one-off import.

  • The Zap keeps firing itself

    If a later step writes back into the tool whose trigger starts the Zap, each write sets it off again and burns through tasks fast.

  • A big batch is held back

    After a bulk import into the starting app, the trigger can return a huge batch at once, and Zapier's flood protection can hold it back.

  • The same item seems ignored

    On a polling trigger, Zapier remembers what it has already seen. An entry edited after its first run will not start the Zap a second time.
Need help

Need help automating LoopedIn with Zapier?

A person reads every message.

FAQ

LoopedIn and Zapier: common questions

01Is the LoopedIn Zapier integration free?
Yes, as long as the Zap stays at two steps. LoopedIn is not a premium app, so the free plan accepts it, with 100 tasks a month. The catch is the step count: the free plan builds one trigger plus one action, nothing more. A Zap that receives a form entry and creates an idea fits. Add a filter to keep only some entries, or a second LoopedIn action, and the Zap becomes multi-step, which only runs on a paid plan. The trigger of the starting app never costs a task.
02How many tasks does a LoopedIn Zap use?
One task per LoopedIn action that succeeds, per run. A Zap that only creates an idea uses one task each time it runs. A Zap that creates an announcement and then updates a roadmap card uses two. An action that fails is not counted against your plan, and the trigger costs nothing however often Zapier checks it. Since all nine LoopedIn operations are actions, every one of them is billed when it goes through. Note that a few apps and actions on Zapier take more than one task when they complete.
03Does LoopedIn work in real time with Zapier?
That depends on the other app, since LoopedIn has no trigger of its own. If the starting app has an instant trigger, it reports the event the moment it happens and the Zap runs straight away, whatever the plan; the editor shows a lightning bolt on such Zaps. If its trigger is polling, Zapier checks on a timer: every 15 minutes on Free, every 2 on Professional, every minute on Team and Enterprise. The LoopedIn action then runs as soon as the trigger hands over the item.
04What does connecting a LoopedIn account take?
A LoopedIn account, plus write access to any workspace that is not yours. In Zapier, open Apps, click + Add connection, search for LoopedIn and click Add connection. A tab opens where you sign in to LoopedIn and grant Zapier access. The connection is then reused by every LoopedIn step. Before the first test, make sure the workspace has what the actions ask for: a category for announcements, a column and an objective for roadmap cards. Without them, the required fields have nothing to offer.
05Why does Update Idea reset value and effort scores?
Because the step asks for every field again, Value and Effort included, and the field help says a blank one falls back to 0. Update Idea is not a patch: title, category, Public, Value, Effort, Completed and Archive are all required. If your Zap only meant to mark an idea completed and left the scores empty, the idea loses them. The fix is to carry the current values into the step, or to type them in, so the update rewrites them as they were.
06What if the LoopedIn operation for the job is missing?
Then the Zap has to be built around what exists. Zapier offers nine actions on LoopedIn and nothing else: no trigger and no search. An event that happens inside LoopedIn, like a new idea, cannot start a Zap, and a Zap cannot read an item back to find its ID. The workable pattern is to start from the app where the event really happens and let LoopedIn receive. Any later update or deletion then needs the item's ID from an earlier step.
07Zapier, Make or n8n for LoopedIn?
Judge it on three criteria rather than on a name. Direction first: on Zapier, LoopedIn only receives, so if the plan needs LoopedIn to start an automation, check whether the other tool offers a trigger for it. Then depth: updates and deletions need an ID, and with no search step on Zapier the ID has to travel through the Zap. Last, volume: Zapier counts one task per successful action, so estimate how many ideas, cards and announcements a month the Zap would write.
Same platform

Other docs you might need on this stack.

Browse all integrations