Basin and Laposta Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Keep Basin and Laposta matched by integrating their events and actions. When marketing events happen in Basin, update the Laposta automatically - without any line of code in visual workflow builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Basin and Laposta

Detailed info you need to know about Basin and Laposta integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Basin

    • Marketing
    • 1 trigger
    • 13 searches
    • 18 actions

    Form backend that collects submissions, filters spam and forwards them to your tools.[5]

  • Laposta

    • Marketing
    • 2 triggers
    • 15 searches
    • 22 actions

    Email marketing from the Netherlands: manage lists, subscribers and campaigns.[6]

How to connect Basin to Laposta

Set up your Basin and Laposta integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Basin and Laposta work in WEXTL?

WEXTL exposes actions and triggers for Basin and Laposta that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

Basin triggersLaposta actions

Basin modules

  • Create a Form Sets up a Basin form from a Name. Use Redirect URL to send visitors elsewhere after a submission, Notification Emails to alert your team and Autoreply to answer the submitter.
  • Create a Form Webhook Makes Basin post every submission of a Form to a web address. Set Format to choose the payload type and turn on Run for Spam to include spam-marked entries.
  • Create a Mail Template Saves a reusable email template under a Project, from its Name and raw HTML Body.
  • Create a Project Adds a project that groups forms and mail templates.
  • Delete a Form Removes a form together with all of its submissions. This cannot be undone.
  • Delete a Form Webhook Removes a webhook so submissions stop being posted to its address.
  • Delete a Mail Template Removes a saved email template from Basin.
  • Delete a Project Deletes a project. Basin does not document what happens to the forms in it.
  • Delete a Submission Deletes a single form submission, and the action cannot be undone.
  • Get a Form Reads one form to get its UUID, Timezone, Project Name and Redirect URL.
  • Get a Form View Shows one recorded visit to a form, with the Form UUID it belongs to and its Created At time.
  • Get a Form Webhook Reads a webhook with its URL, Format, Enabled state and Trigger When Spam setting.
  • Get a Mail Template Returns a template by Mail Template ID, along with the Project ID it sits in and the Body markup.
  • Get a Project Looks up one project to read its Name and when it was created or last changed.
  • Get a Submission Finds one submission by Submission ID. Returns the sender Email and Payload Params, plus flags for Spam, Read and Trash.
  • List Domains Shows the domains registered to your Basin account. Use Query to match text, Page to move through results and Limit to cap the count.
  • List Form Views Returns recorded views of your forms. Use Query to filter by id, uuid, form id or form uuid and Limit to set how many to read.
  • List Form Webhooks Gathers the webhooks configured across your forms, one item each. Use Query to narrow the set.
  • List Forms Pulls your forms, each with its Name and Project Name. Filter them by id, name, uuid or project id through Query.
  • List Mail Templates Finds the email templates of one Project. Use Page to step through them and Limit to cap how many are read.
  • List Projects Fetches your projects, each with a Name and a Created At time. Use Query to find one by text.
  • List Submissions Browses form submissions. Use Form to limit it to one form, Status and Date From to narrow the range and Order By to sort them.
  • Make an API Call Calls the Basin REST API directly with a free-form request under your saved credential.
  • Re-fire Webhooks for a Submission Sends the webhooks of one submission out again, so receivers may see it a second time.
  • Re-fire Webhooks for Several Submissions Replays webhooks for a batch of Submission IDs in a single call. Receivers may see those submissions again.
  • Submit a Form Posts an entry to a Basin form as a visitor would, with one row of Fields per value. Set Client IP to record the visitor address.
  • Update a Form Edits an existing form, such as its Name, Redirect URL, Notification Emails or spam checks. Use Clear Fields to empty a value.
  • Update a Form Webhook Edits a webhook to change its URL, switch Enabled on or off, or move it to another Form. Changing the URL of a webhook created by Watch New Submissions stops that trigger.
  • Update a Mail Template Replaces the Name or Body of a mail template. Add the ETag (If-Match) of the version you read and Basin refuses the write if it changed since.
  • Update a Project Retitles an existing project with a new Name.
  • Update a Submission Flags a submission as spam or not with Spam, as read with Read, or moves it to the trash with Trash.
  • Watch New Submissions Starts the workflow the moment Basin receives a form submission, through an instant webhook. Each run gets the Submission ID, Email and Attachments.

Laposta modules

  • 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.
  • 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.
  • 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.
  • 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.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Basin and Laposta integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Basin and Laposta on WEXTL®

Claim your 3-day trial to build Basin with Laposta integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Basin and Laposta.

How do I connect Basin and Laposta?

Connect your Basin and Laposta accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between Basin and Laposta?

Example: when the "Watch New Submissions" trigger in Basin fires, WEXTL can "Create a Campaign" in Laposta. Basin has 1 trigger (including Watch New Submissions). Laposta has 37 actions (including Create a Campaign, Create a Field, and Create a List). Add filters and transforms between steps when you need them.[1]

Can Basin trigger actions in Laposta, and Laposta in Basin?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Basin and Laposta?

No. Basin-to-Laposta automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Basin integrate with Laposta in real time?

Yes. Trigger-based automations start the moment Basin (or Laposta) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Basin + Laposta integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Basin with Laposta?

You can build your Basin + Laposta automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Basin and Laposta integration.

  1. Basin and Laposta integration source code, module specs and credentials implementation.
  2. Our Basin and Laposta integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Basin and Laposta, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Basin integration information
  6. Laposta integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Basin and Laposta integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Basin and Laposta, or get started