Resources · Zapier integration

Pipeless Recommendations Zapier integrationAutomate Pipeless Recommendations with Zapier.

0 triggers, 2 actions, 8 searches. The Pipeless Recommendations Zapier integration feeds user behavior into Pipeless and reads back feeds and suggestions. Here: what it costs in tasks, how to connect it, a first Zap, every operation, and what breaks.

See the 10 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Pipeless Recommendations Zapier integration is for

Pipeless builds personalized recommendations and activity feeds from who did what to which object. The integration lets a Zap (an automation on Zapier: a starting event, then the steps that follow) record those interactions in Pipeless and ask it for suggestions, without writing code.

Three concrete results. A behavior log in Pipeless: each time a member likes an article or buys a product in another tool, Create Event records that relationship between the user and the item. A batch of interactions in one step: an order with several lines becomes several events at once through Create Events (With Line Item Support). Suggestions handed to the next step: Get Recommended Content (For User) or Get Related Content returns items a following step can drop into an email or a page.

What Zapier does not do here: nothing starts from Pipeless. The app has no trigger, so every Zap opens on an event in another tool. Pipeless never pushes a recommendation by itself; a Zap has to ask for one through a search. And since a search adds a step, any Zap that reads from Pipeless is multi-step and needs a paid plan.

If you are still choosing a platform, read Make vs Zapier, or get trained on the basics with Zapier training.

Vocabulary

Zapier vocabulary, in one minute

Eight words you will see in the editor, each in plain English.

Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. Pipeless has none, so it comes from another app.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you. Pipeless has two.
Task
The unit Zapier bills: one action your Zap completed successfully. Your plan's allowance is counted in tasks.
Polling trigger
A trigger Zapier checks on a timer, asking the app for new items at a fixed interval and keeping only what it has not seen.
Instant trigger
A trigger the app reports itself: it calls Zapier the moment the event happens, so nothing waits for the next check.
Filter
A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can use what it found.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search makes one, and it needs a paid plan.
Cost

What it really costs

Pipeless Recommendations is not reserved for paid plans: it works from the free plan up.

  • Free plan100 tasks a month, unlimited Zaps
  • Free plan Zap sizeTwo steps: one trigger, one action
  • Cost of a recorded event1 task per successful action
  • Using any searchMakes the Zap multi-step: paid plan

The trigger in the other app never costs a task, and Zapier checking for new data is free too. Each Create Event or Create Events that succeeds counts as one task; a failed one is not counted. The free plan gives 100 tasks a month and Zaps of two steps only, so a trigger plus one Pipeless action fits. Add one of the eight searches, or a filter, and the Zap becomes multi-step: paid plan required. Paid plans also check polling triggers more often.

Connect

Connect your Pipeless account

  1. 01

    Open the Apps page

    In Zapier, go to the Apps page of your account. You need a Pipeless account, plus write access to the data set the Zap will feed if somebody else owns it.

  2. 02

    Add Pipeless

    Click + Add connection, type Pipeless Recommendations in the dialog's search box and pick it from the results. Then click Add connection to open the sign-in tab.

  3. 03

    Sign in and allow access

    Sign in to Pipeless in the tab that opens and grant Zapier access to the account. The connection is saved once, and every Pipeless step of every Zap reuses it.

First Zap

Your first Zap: log each interaction in Pipeless

GoalEvery new row of an interaction log becomes a Pipeless event between a user and an item.

  1. 01

    Choose the starting event

    Pipeless has no trigger, so pick the tool where interactions are logged and its event, here a new row. Whether it fires instantly or on a timer is decided by that tool.

  2. 02

    Test the trigger

    Run the test: Zapier brings back the three most recent items of the connected account. Map the next steps on one of those real rows, not on an empty sample.

  3. 03

    Add the filter

    Add a filter so half-filled rows stop here, letting through only rows with both IDs. A filter turns the Zap into a multi-step one, so this needs a paid plan.

  4. 04

    Add Create Event

    Pick Pipeless Recommendations, then Create Event. Map the start object (the user), the relationship type, and the end object (the item), with the same types as in Pipeless.

  5. 05

    Test, then publish

    Test the action once and read what came back. If it looks right, publish the Zap to switch it on. Only rows added after that moment will be sent.

Actions

Pipeless Recommendations actions

Pipeless Recommendations gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Event

Action

In Zapier“Create a Pipeless Event”

Records one interaction in Pipeless: a start object, such as a user, linked to an end object, such as an article, by a relationship type like a like or a purchase.

When to use it
one action in another tool equals one signal for the recommendations.
Watch out
each ID is capped at 40 characters, and with Relationship Single left on its default, the same relationship between the same two objects is kept only once.
2

Create Events (With Line Item Support)

Action

In Zapier“Create up to 10 events in one API call. If there are more than 10 events provided, the excess events will be truncated.”

Sends several interactions to Pipeless in a single step, using line items, so a cart with five products becomes five events instead of five Zap runs.

When to use it
orders, playlists or reading lists where one trigger carries many items.
Watch out
the step takes 10 events at most; anything beyond the tenth is cut off.
Searches

Pipeless Recommendations searches

8 search steps look for data that already exists in Pipeless Recommendations, so a later step can use it.

A search step reads from Pipeless and passes the result to the next step. In the editor, the eight Pipeless searches sit at the bottom of the Action event list, under the SEARCH heading. Each of them needs an object type and an object ID. Three settings decide what happens when the answer is not a single clean match.

1

Get Activity Actions Feed

Search

In Zapier“Fetch the activity feed for a user (or any other object type). This activity feed format will return acted upon entities as the main result. Ex. one item per post, article, product, etc. Each single item has associated actions.”

Returns a feed built around the things being acted on: one entry per post, article or product, each carrying the actions attached to it.

When to use it
a digest showing which items drew activity from the people a user follows.
Watch out
by default, a feed asked for an object that does not exist ends in a 404 error; Allow Missing Object returns an empty feed instead.
2

Get Activity Feed

Search

In Zapier“Fetch the activity feed for a user (or any other object type). This activity feed format will return events in sequential descending order - there will be one activity item for each found action.”

Pulls a chronological feed for a user or any other object, newest first, with one line for every action found.

When to use it
a timeline of what happened, in order, rather than a list grouped by item.
Watch out
the user you ask about can show up in their own feed; set Exclude Self Object to true to keep them out.
3

Get Activity on Object

Search

In Zapier“Gets recent activity on any object”

Looks at one specific object, a product page or a post for instance, and brings back the recent activity on it.

When to use it
checking how much attention a single item gets before a later step decides whether to promote it.
4

Get Recommended Content (For User)

Search

In Zapier“For a given user (or any object type), get a list of recommended content, based on their behavior/tastes.”

Asks Pipeless which content suits a given user, based on their behavior and tastes, and lets you choose the kind of object to recommend.

When to use it
filling a personal suggestion block in an email.
Watch out
Include Content Authors and Exclude Content From Followed both stay off by default, and switching either on requires a content-created relationship type too.
6

Get Related Content

Search

In Zapier“Gets related content objects based on a specific piece of content of any type.”

Starting from one piece of content, of any type, this search finds other content objects that Pipeless considers related.

When to use it
a "read next" list attached to a newly published article, without a user in the picture.
Watch out
the starting piece needs both its ID and its type, exactly as stored in Pipeless.

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 relied on it. Switch it on and the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Pipeless offers no such variant on any of its eight searches, so you will not see it here.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or hand all of them on at once.
When it breaks

When it breaks

Zapier links no help article to Pipeless Recommendations, so these cases come from how Zapier works overall and from the limits written into the fields themselves.

Most failures are about data, not about the connection: a wrong type, a missing object, a batch that is too big. When a Zap stops for no clear reason, start from Zapier troubleshooting.

  • Past interactions never reach Pipeless

    A Zap only reacts to what happens after it is switched on. Rows or orders that existed before stay out of Pipeless; loading that history is a separate job.

  • Events after the tenth disappear

    Create Events (With Line Item Support) accepts 10 events per run. Extra line items are cut off, so a big order loses part of its signal.

  • Unknown object, 404 error

    Several searches fail with a 404 error when the object asked about does not exist. Allow Missing Object turns that into an empty result the Zap can live with.

  • A bulk import gets held back

    When the starting app suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold it back rather than run every event.
Need help

Need help automating Pipeless Recommendations with Zapier?

A person reads every message.

FAQ

Pipeless Recommendations Zapier integration: common questions

01Is the Pipeless Recommendations Zapier integration free?
Partly. Pipeless Recommendations is not one of the apps Zapier keeps for paid plans, so it works on the free plan, which gives 100 tasks a month and unlimited Zaps. The catch is the two-step limit: one trigger and one action. A trigger in another tool followed by Create Event fits. Once you add a search to read recommendations, a filter or a second action, the Zap becomes multi-step and needs a paid plan.
02How many tasks does Pipeless use on Zapier?
One task for each action that succeeds. A Create Event that goes through costs one task; one that fails is not counted. Create Events (With Line Item Support) is still one action in the Zap, which is why it beats running the Zap once per item. The trigger in the other app is free, and so is Zapier checking it for new data, however often that happens. Two successful actions in one run mean two tasks.
03Does Pipeless Recommendations on Zapier run in real time?
It depends on the app that starts the Zap, since Pipeless has no trigger of its own. If that app offers an instant trigger, it tells Zapier straight away whatever your plan. If it is a polling trigger, Zapier checks on a timer: every 15 minutes on Free, 2 minutes on Professional, 1 minute on Team and Enterprise. The searches and actions that follow run within that same Zap run.
04What does connecting Pipeless Recommendations to Zapier take?
A Pipeless account, plus write access to the data you want to touch if it belongs to someone else. On the Apps page of your Zapier account, click + Add connection, search for Pipeless Recommendations and select it, then click Add connection. Sign in to Pipeless in the new tab and grant Zapier access. From then on, the connection is stored once and every Zap that uses a Pipeless step picks it up without asking again.
05Why does a Pipeless search stop a Zap with a 404 error?
Because the object you asked about does not exist in Pipeless. On Get Activity Actions Feed, Get Activity Feed and Get Recommended Users to Follow (For User), the Allow Missing Object option is off by default, and a missing object then returns a 404 error. Switch it on and the search returns an empty feed with no error instead. Pair that with the Successful if no search results are found? setting if the rest of the Zap should still run.
06What if the Pipeless operation you need is not listed?
Then Zapier does not offer it today. The visible catalog holds two actions, Create Event and Create Events (With Line Item Support), and eight searches that read feeds, recommendations and related items. There is no trigger, so Pipeless cannot start a Zap, and no visible step to remove an event. Anything beyond that has to be done inside Pipeless or another way. The Pipeless page on Zapier stays the reference, since a catalog can change.
07Zapier, Make or n8n for Pipeless Recommendations?
Pick by criteria, not by ranking. With Zapier, ask three things. Do you only need to send events to Pipeless? A two-step Zap on the free plan covers that. Do you want to read recommendations and push them somewhere? That means searches and a paid plan. Do you need Pipeless itself to start the automation? Zapier has no trigger for it. Check what the other platforms list for Pipeless against those same three needs.
Same platform

Other docs you might need on this stack.

Browse all integrations