Connect Laposta integrations
VerifiedEmail marketing from the Netherlands: manage lists, subscribers and campaigns, connected to WEXTL workflows and AI agents. Link Laposta campaigns and audiences to your CRM, ad and analytics workflows. When Watch Events (Instant) arrives, continue with Get a Campaign or Get a Field.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Supported triggers and actions for Laposta integration
Triggers can detect changes in Laposta and run actions that can create, search or modify data inside Laposta automatically[3], exactly how you set them.
- Watch Events (Instant) Fires the moment Laposta reports a subscriber event through a webhook. Each run tells you the Event and Action, with the Source and the Subscriber.
- Watch New Subscribers Polls one list every run and fires once per subscriber found, with the Email and Signup Date. Use Limit to set how many are taken per check.
- Get a Campaign Gets the settings of one campaign, such as its Campaign ID and creation date.
- Get a Field Fetches a single custom field of a list, returning the Field ID and List ID.
- Get a List Retrieves one Laposta list and returns its List ID and the time it was last modified.
- Get a Report Gets the statistics of one campaign: how many mails were Sent, Accepted, Cleaned or reported as Complained.
- Get a Segment Reads a saved segment, showing its Name and Definition.
- Get a Subscriber Looks up one person on a list and returns the Email, State and Signup Date.
- Get Campaign Content Reads what a campaign says in both Plaintext and HTML, plus the Import URL if it was imported from a page.
- Get Campaign History Shows the events logged for a campaign, such as the Type and Event Date of each. Use Events From and Events To to cover a time window, and Order to flip the sorting by date.
- Get Subscriber History Lists what one subscriber did, such as opens and clicks. Use Campaign ID to look at a single campaign, or Events From and Events To to bound the dates.
- List Campaigns Lists the campaigns in your account, each with its Campaign ID. Use Limit to trim how many are returned.
- List Fields Shows the custom fields defined on one list, including the Field ID of every field. Use Limit to cap how many appear.
- List Lists Collects the subscriber lists in your account, with List ID values that later steps can use. Use Limit to restrict the count.
- List Reports Returns the sending statistics of the campaigns in your account, counting what was Sent, Accepted or Cleaned for each. Use Limit to trim the result.
- List Segments Lists the segments defined for one list, giving the Segment ID, Name and Definition of each.
- List Subscribers Browses the subscribers of a list. Use State to keep one status only, Search to match text in their email or fields, Label to keep those with one label, and Order By with Order to sort them.
- Create a Campaign Sets up an email campaign from its Name, Subject, Sender Name, Sender Email and the Lists it goes to. Use Segment IDs to reach parts of those lists, and Link Google Analytics adds tracking to the links.
- Create a Field Adds a custom field to a list under a Name and Data Type. Use Options to define choices, Default Value to prefill it and Required to make subscribers fill it in.
- Create a List Makes a new subscriber list in Laposta from a Name. Add Remarks for notes, and set Subscribe Notification Email or Unsubscribe Notification Email to get a message on each signup or exit.
- Create a Segment Saves a named rule that groups the subscribers of one list. Write the rule with Definition and use the Segment ID to target the group in a campaign.
- Create a Subscriber Signs an Email address up to a list together with its IP Address. Fill Custom Fields to store extra data, turn on Skip Double Opt-In to skip the confirmation mail, or Update If Exists to refresh a known subscriber.
- Delete a Campaign Removes a campaign from Laposta altogether.
- Delete a Field Removes a custom field from a list in Laposta.
- Delete a List Deletes a Laposta list. Laposta cannot undo it.
- Delete a Segment Deletes a saved segment from a list. This cannot be undone.
- Delete a Subscriber Deletes a subscriber from the chosen Laposta list.
- Make an API Call Calls the Laposta REST API directly with a free-form request under your saved credential.
- Remove All Subscribers from a List Empties a list by removing every subscriber on it. Set Confirm to go ahead with the removal.
- Schedule a Campaign Schedules a campaign to go out later. Use Send At to set the date and time, which carries the offset of the workflow time zone.
- Send a Campaign Sends a campaign right now to the lists it targets.
- Send a Test Email Mails a preview of a campaign to one Email address before it reaches subscribers.
- Set Campaign Content Writes the message of a campaign from HTML, or pulls it from a page with Import URL. Turn on Inline CSS to move the styles into the markup.
- Sync Subscribers in Bulk Adds, edits or unsubscribes many people on a list in one request. Returns a Report of how many were Added, Edited or Skipped, plus any Errors.
- Update a Campaign Edits a campaign: the Name, Subject, Preview Text, Sender Name, Sender Email or Lists. Use Clear Fields to blank settings you no longer want.
- Update a Field Adjusts a list field. Rename it, change the Data Type or Default Value, and use Add Options, Rename Options or Remove Options for choice fields.
- Update a List Gives a list a new Name, turns Locked on or off, or edits its Remarks and notification addresses. Use Clear Fields to empty values.
- Update a Segment Renames a saved segment, or replaces its rule with a new Definition.
- Update a Subscriber Gives a subscriber a New Email, a changed State or new Custom Fields. Use Clear Fields to empty chosen values.
How to integrate Laposta in automation workflow?
Laposta in three steps: start with "Watch Events (Instant)", connect one credential, then add your next step.
STEP 1
Select Laposta in workflow
Add the "Watch Events (Instant)" trigger from Laposta to the canvas[4].
STEP 2
Connect Laposta
Fill in the Laposta credential once. All 38 Laposta modules use it[3].
STEP 3
Build a workflow
Add "Get a Campaign" or "Get a Field" after it, then connect any app[5] or the HTTP node.
How Laposta connects and integrates with WEXTL
Save and approve your credentials once. WEXTL® stores authorization information encrypted and reuses the authentication whenever Laposta app is called in workflows. That allows your marketing automations to run without your attention, per defined schedule[7]. See the integration guide[6] for a detailed list of fields that Laposta supports.
Full Laposta API documentationThe following table illustrates what fields Laposta integration require during authorization flow inside our workflow builder[4].
Connect Laposta
API Key*Text
••••••••
| Field | Type | Help |
|---|---|---|
API KeyRequired | password | In Laposta open Access & Subscription, then Links - API, and copy an API key. Each key belongs to one account. |
Connect Laposta to popular apps on WEXTL
Enter a name of the other app you want to sync with Laposta below. Click on selected app to explore integration options with Laposta. If the app you search for is not available in WEXTL yet, you can use HTTP node[10] instead to integrate it directly.
Example automation with Laposta integration
Select Watch New Subscribers trigger from Laposta - this will be a starting point in your automation. Whenever event happens in Laposta, workflow will start[7] from Watch New Subscribers node.
Search for Delete a Subscriber, connect it as the next step of integration sequence. You can use filters between Watch New Subscribers and Delete a Subscriber, so only important data pass from Watch New Subscribers to the next step. WEXTL gives you full control over the process of Laposta automation. All parts of workflow are visible on the canvas[4].
Laposta on WEXTL has 39 modules for combining marketing automations. Explore Laposta documentation for more.
- LapostaWatch New Subscribers
- GatherUpPerforms action
OR
- GatherUpTriggers
- LapostaDelete a Subscriber
Frequently asked questions
Common questions about automating Laposta in your workflows.
What triggers does Laposta support?
Laposta has 2 triggers, including "Watch Events (Instant)" and "Watch New Subscribers". Triggers are start points of the workflow, and automations may start from them.
What actions can I run in Laposta?
Integration has 37 actions, including "Get a Campaign", "Get a Field", and "Get a List", and more. Refer to our Laposta Documentation for detailed inputs and outputs.
Do I need to write code to build automations?
No. The 38 Laposta modules, like "Get a Campaign", are forms on the canvas: pick a field, map data from an earlier step. Code is optional[4].
Is the integration secure?
Yes. You fill in the Laposta credential once. WEXTL encrypts it at rest, and only your team can use it.
How does WEXTL integrate with Laposta?
Through the official Laposta API: 38 modules, plus "Make an API Call" for any endpoint they don't cover[3].
Can I use webhooks with Laposta?
Yes. "Watch Events (Instant)" is instant: Laposta pushes each event, so there is no polling delay.
Why use WEXTL platform for Laposta automation?
WEXTL is an AI-first visual canvas: describe the Laposta flow in plain words and AI wires the nodes[4].
References
List of sources used to gather information about the Laposta integration.
- Laposta integration source code, module specs and credentials implementation.
- Internal Laposta integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official Laposta vendor API documentation, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® Visual Workflow Builder, anonymized data from our technical support team.
- WEXTL® Apps Library
- WEXTL® Laposta App Documentation
- WEXTL® Workflow Scheduler
- WEXTL® HTTP node documentation
How we write and maintain Laposta app documentation
Explore how WEXTL® crafted Laposta integration page documentation. Used sources, the role of AI, and how the team validates the result.





















