Resources · Zapier integration

Laposta Zapier integrationAutomate Laposta with Zapier.

The Laposta Zapier integration gives you 3 triggers, 2 actions and 0 searches. Every change to a subscriber on a Laposta list can start a Zap the moment it happens, and your other tools can add, update or remove subscribers in return, on the free plan.

See the 5 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Laposta Zapier integration actually does

Laposta is a newsletter tool, and on Laposta a subscriber is called a relation. The integration keeps those relations in step with the rest of your stack through a Zap (an automation on Zapier: one event that starts it, then one or more steps that follow), in both directions.

Three results come back again and again. First, a CRM that knows every new subscriber: A New Relation Has Been Added fires as soon as someone joins a list, and the contact is created in your sales tool. Second, clean unsubscribes everywhere: A Relation Has Been Removed tells your other tools to stop treating that person as a reader, and A Relation Has Been Edited carries profile changes along. Third, lists fed from the outside: Add or Edit a Relation puts someone who filled a form in another tool into the right Laposta list, and Delete Relation takes them out when they leave.

What Zapier does not do here matters as much. There is no search on Laposta, so a Zap cannot check whether a relation exists before acting; Add or Edit a Relation handles both cases instead. Nothing sends or schedules a newsletter, and nothing creates a list: campaigns stay inside Laposta. If you are weighing platforms, start with n8n vs Zapier.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on every screen of the editor. Here they are in plain English, once.

Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it; here, a relation added, edited or removed.
Action
What the Zap does after it starts: the step that writes, sends or deletes something in an app on your behalf.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
Instant trigger
A trigger the app reports itself: Laposta calls Zapier the moment the change happens, so nothing waits for a scheduled check.
Polling trigger
The other kind, where Zapier checks an app on a timer. None of the three Laposta triggers works this way.
Filter
A step that lets the Zap go on only when the incoming data meets your condition, and stops it quietly otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes one, and it then needs a paid plan.
Cost

What a Laposta Zap really costs

Zapier bills completed actions, never the event that starts the Zap. With three instant triggers, that is good news.

  • Free plan100 tasks a month
  • Free plan Zap size1 trigger + 1 action
  • Premium appNo
  • Instant triggers3 of 3

The three Laposta triggers never cost a task. Each action that succeeds counts once: a Zap that adds a relation to Laposta and posts in a chat uses two tasks per signup. A failed action is not counted. Laposta is not a premium app and works on the free plan: 100 tasks a month, unlimited Zaps, each one limited to two steps, a trigger and one action. Since all triggers are instant, the interval grid below never slows them down, whatever the plan.

Connect

Connect Laposta to Zapier in three steps

  1. 01

    Open your apps page

    In Zapier, open Apps and click + Add connection. Use a Laposta account that can read and change the lists your Zaps will touch, not a restricted colleague account.

  2. 02

    Pick Laposta

    Search for Laposta in the dialog, select it, then click Add connection. A new browser tab opens on the Laposta side; leave it open until the sign in is finished.

  3. 03

    Sign in and allow access

    Log in to Laposta in that tab and grant Zapier access to the account. The connection is saved once, then every trigger and action of every Laposta Zap reuses it.

First Zap

Your first Zap: copy every new subscriber into your CRM

GoalEach time someone joins a Laposta list, create the matching contact in your CRM so sales sees them straight away.

  1. 01

    Pick the trigger

    Create a Zap, choose Laposta as the app that starts it and A New Relation Has Been Added as the event, then select your Laposta connection.

  2. 02

    Choose the list

    Pick the Laposta list to watch. If several look alike, check the List ID in the list properties in Laposta to be sure it is the live one.

  3. 03

    Test the trigger

    Run the test. Zapier brings back the three most recent relations added to that list, so pick a real subscriber to map your fields against.

  4. 04

    Add and test the action

    Add the CRM step, map the email from Laposta into the contact fields, then run it once and open the CRM to check the contact.

  5. 05

    Publish

    Click Publish to switch the Zap on. From now on, each new subscriber reaches the CRM the moment Laposta records them, on any plan.

Triggers

Laposta triggers

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

1

A New Relation Has Been Added

Instant trigger

In Zapier“Triggers when een new relation has been added to the list in your Laposta account.”

Starts the Zap when someone lands on the Laposta list you picked, however they got there.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
creating the contact in a CRM, sending a welcome message from another tool, or alerting sales about a fresh signup.
Watch out
one Zap watches one list; a second list needs a second Zap with its own List setting.
2

A Relation Has Been Removed

Instant trigger

In Zapier“Triggers when a relation of your Laposta list has been removed.”

Fires when a subscriber disappears from the chosen Laposta list, which is the signal your other tools need to stop treating that person as a reader.

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 the contact in your CRM, so nobody keeps writing to a person who left.
Watch out
removals made before the Zap is published never come through, so clean old records by hand once.
3

A Relation Has Been Edited

Instant trigger

In Zapier“Triggers when a relation of your Laposta list has been edited.”

Runs each time the details of a relation change on the selected Laposta list, for example a detail someone corrected on that subscriber.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
keeping the same person's profile identical in Laposta and in your CRM or support tool.
Watch out
if the same Zap writes back into Laposta with Add or Edit a Relation, it edits the relation again and starts itself in a loop.
Actions

Laposta actions

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

1

Delete Relation

Action

In Zapier“Delete an existing relation.”

Takes a subscriber off a Laposta list, identified by their email address.

When to use it
someone asks to be forgotten through a form, and the list should follow without anyone logging in to Laposta.
Watch out
List and Email are both required, so the earlier step has to say which list and which address.
2

Add or Edit a Relation

Action

In Zapier“Edit an existing relation, or add a new relation, in your Laposta list.”

Puts a subscriber on a Laposta list: if the email is new, the relation is created; if it is already there, the existing relation is updated.

When to use it
a lead fills a form on another tool and should land on the right list, whether or not Laposta already knows them.
Watch out
List and Email are both required, so the earlier step has to carry an email address.
When it breaks

When a Laposta Zap breaks

Zapier lists no help article and no rate limit specific to Laposta. What goes wrong comes from the List setting and from general Zapier behavior.

Four situations account for most surprises. Check them before blaming the connection; if a Zap still misbehaves, move on to Zapier troubleshooting, then to a Zapier agency if you would rather hand it over.

  • The Zap watches the wrong list

    Every trigger and action is tied to one List. If signups land on another list, nothing happens. Check the List ID in the list properties in Laposta.

  • Edits loop forever

    A Zap started by A Relation Has Been Edited that writes back with Add or Edit a Relation edits the relation again, and sets itself off over and over.

  • Old subscribers never arrive

    A Zap only reacts to changes after you switch it on. Relations already on the list stay where they are; moving them is a separate job.

  • A bulk import stalls

    Importing a large file into a list can fire a huge batch of events at once, and Zapier's flood protection can hold them back.
Need help

Need help automating Laposta with Zapier?

A person reads every message.

FAQ

Laposta Zapier integration: frequent questions

01Is the Laposta Zapier integration free?
Yes. Laposta is not a premium app, so it runs on the free plan: 100 tasks a month and unlimited Zaps. The limit nobody announces is the size of a free Zap, two steps only, one trigger and one action. A filter, for instance to let only some subscribers through, or a second action makes it a multi-step Zap, which needs a paid plan. Copying each new subscriber into one tool stays free.
02How many tasks does a Laposta Zap use?
One task per action that succeeds, and nothing for the trigger. A new, edited or removed relation never costs a task by itself. A Zap that copies each signup into a CRM uses one task per signup, so a hundred signups a month use the whole free allowance. A Zap with two actions doubles that. Failed actions are not counted, so an error costs nothing, but the subscriber is not copied either.
03Does Laposta trigger Zaps in real time?
Yes, all three triggers are instant. Laposta tells Zapier the moment a relation is added, edited or removed, and the Zap starts at once. The plan intervals, 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise, only apply to polling triggers, and Laposta has none. That is the strongest point of this app on a free plan: a welcome or a sales alert goes out right after the subscriber joins.
04What does it take to connect Laposta to Zapier?
A Laposta account, a Zapier account, and access to the lists the Zap will use. The connection is done once from the Apps page of Zapier, by signing in to Laposta in a new tab. After that, each trigger and action asks which List to use. The List ID shows in the properties of the list inside Laposta, which helps when two lists carry similar names. Pick the list carefully once and every step after it follows.
05Why does a Laposta Zap keep running on its own?
Most likely it writes where it listens. A Zap that starts on A Relation Has Been Edited and then updates the same list with Add or Edit a Relation changes the relation again, which fires the trigger again, and so on, burning a task each round. Split the flow so the action writes to a list the trigger does not watch, or start the Zap from another app instead. Test the Zap once with a real edit before publishing.
06What if the Laposta operation you need is not on Zapier?
Then the Zapier app cannot do it today. It covers five operations: three triggers on relations added, edited or removed, and two actions, Add or Edit a Relation and Delete Relation. It does not send campaigns, create lists or look up a relation. For those, the work stays inside Laposta, or another tool that talks to it directly, or a request to Laposta to extend the Zapier app. Check the operation list above before planning around it.
07Zapier, Make or n8n for Laposta?
It depends on your criteria, not on a single winner. Zapier is quick to set up, its three Laposta triggers are instant and everything works on the free plan, which suits a small team syncing one list with one CRM. Its constraints are the two step free Zap and the short list of operations. If you need heavy volume, branching logic or hosting the automation yourself, compare the platforms on those points first.
Same platform

Other docs you might need on this stack.

Browse all integrations