otherapi_key

Laposta

Dutch newsletter app (email marketing) that makes it exceptionally easy to send professional newsletters.

Verdict

Laposta is an email marketing platform that lets your team manage subscriber lists, custom fields, and webhooks through Switchy. @mention it to create mailing lists, add or remove subscribers in bulk, define custom fields for segmentation, and set up event webhooks — all without leaving the conversation. Marketing ops and growth teams get the most value: you can script list hygiene, sync subscriber data from other tools, and automate campaign prep. The MCP requires an API key from your Laposta account, which grants full read-write access to lists and members. It won't send campaigns or design emails — it's purely for list management and subscriber data.

Common use cases

  • Bulk-add webinar signups to a list
  • Clear inactive subscribers before a campaign
  • Sync CRM contacts to email segments
  • Set up webhooks for real-time unsubscribe alerts
  • Create custom fields for lead scoring

Integration

Vendor
Laposta
Category
other
Auth
API_KEY
Tools
24
Composio slug
laposta

Tools

  • Clear All Members From List

    Tool to clear all active members from a list. Use when you need to remove all active member relationships while preserving the list itself. The operation is permanent and cannot be undone.

  • Create Custom Field

    Tool to create a custom field for a mailing list to define subscriber attributes. Use when you need to add custom fields like text, numeric, date, or select fields to a list. For select fields (select_single or select_multiple), you must pr

  • Create Mailing List

    Tool to create a new mailing list in Laposta to manage email subscribers. Use when you need to create a new list with zero members.

  • Create Member

    Tool to add a new subscriber relationship to a list with custom fields and tracking info. Use when you need to create a new member in a list or update an existing member if upsert is enabled.

  • Create Webhook

    Tool to register a new webhook for list events in Laposta. Use when you need to receive real-time notifications for subscriber events like subscriptions, modifications, or deactivations.

  • Delete Field
    destructive

    Tool to permanently remove a custom field from a mailing list. Use when you need to delete a field that is no longer needed.

  • Delete List
    destructive

    Tool to permanently remove a mailing list from Laposta. Use when you need to delete a list that is no longer needed. The list cannot be recovered after deletion.

  • Delete Member
    destructive

    Tool to permanently remove a member from a list. Use when you need to delete a member by their ID or email address.

  • Delete Webhook
    destructive

    Tool to permanently remove a webhook. Use when you need to delete a webhook from a list. Pending webhook requests are completed before deletion.

  • Get All Campaign Reports

    Tool to retrieve performance metrics for all campaigns. Use when you need campaign statistics including opens, clicks, bounces, complaints, and unsubscribes.

  • Get All Campaigns

    Tool to retrieve all campaigns from Laposta account. Use when you need to list all email campaigns with their configuration and delivery status.

  • Get All Fields

    Tool to retrieve all fields for a specific list in Laposta. Use when you need to see all field definitions, metadata, and settings for a list.

  • Get All Lists

    Tool to retrieve all mailing lists from your Laposta account. Use when you need to view all lists including both active and deleted ones.

  • Get All Members

    Tool to retrieve all members from a specified Laposta mailing list. Use when you need to list or view all contacts in a list. Optionally filter by member state (active, unsubscribed, or cleaned).

  • Get All Segments

    Tool to retrieve all segments from a mailing list. Use when you need to list or browse segments within a specific list.

  • Get All Webhooks

    Tool to retrieve all webhooks for a specific list. Use when you need to view all webhooks configured for a particular list.

  • Get Field Details

    Tool to retrieve specific field details by field_id. Use when you need to fetch complete information about a custom field including its configuration, data type, and available options.

  • Get List Details

    Tool to retrieve specific list details by list_id. Use when you need to fetch complete information about a mailing list including its metadata, state, notification settings, and member statistics.

  • Get Member

    Tool to retrieve specific member details by member_id or email. Use when you need to get comprehensive information about a member from a list, including their status, registration details, and custom field values.

  • Get Webhook Details

    Tool to retrieve specific webhook details by webhook_id. Use when you need to inspect webhook configuration including event type, URL, and status.

  • Update Field

    Tool to modify field configuration in a Laposta list. Use when you need to update field properties such as name, datatype, required status, or display settings. WARNING: Modifying datatype removes all data from that field.

  • Update Mailing List

    Tool to modify list properties such as name, remarks, or notification emails. Use when you need to update an existing mailing list's configuration.

  • Update Member

    Tool to modify member data, status, or custom fields in a Laposta list. Use when updating existing member information or managing subscription state. Supports partial updates (only modified fields need to be included).

  • Update Webhook

    Tool to modify webhook configuration including URL, event type, or blocked status. Use when you need to update an existing webhook's settings.

Setup

Setup guide

  1. 11. In Switchy, open your workspace settings and navigate to the MCP integrations panel. 2. Select 'Add Integration' and choose Laposta from the directory. 3. Log into your Laposta account in a separate tab and go to Account Settings, then API Keys. 4. Generate a new API key (or copy an existing one) and paste it into the Switchy connection dialog. 5. Click 'Connect' — Switchy will validate the key and confirm the connection. 6. Open any Space and type '@Laposta' followed by a command like 'list all my mailing lists' to test the connection. 7. If you see a response with your lists, the integration is live and ready to use. 8. To invoke a specific tool, @mention Laposta and describe the task in plain language — for example, '@Laposta create a new list called Q1 Webinar Leads' or '@Laposta add this email to the newsletter list with custom field role set to manager'.

What teammates see: by default, memories from Laposta are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Spaces have used this MCP together with a given model.

How Switchy teams use it

Not enough Spaces yet to publish anonymised usage stats (we require ≥ 50 Spaces per week).

Starter prompts

List All Mailing Lists

@Laposta show me all my mailing lists with their current member counts and when they were created
Open in a Space →

Add Subscriber With Custom Data

@Laposta add sarah@example.com to the 'Product Updates' list with custom fields: first_name Sarah, company Acme Corp, role Product Manager
Open in a Space →

Create Segmentation Field

@Laposta create a select-type custom field called 'interest' on the Newsletter list with options: product_news, case_studies, events
Open in a Space →

Clear List for Fresh Import

@Laposta clear all active members from the 'Q4 Campaign' list so I can re-import the latest contacts
Open in a Space →

Register Event Webhook

@Laposta create a webhook for the Newsletter list that posts to https://myapp.com/webhooks/laposta on subscribe, modify, and deactivate events
Open in a Space →

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@Laposta show me all active subscribers on our monthly newsletter list and their signup dates

Output

Based on the list data, you have 1,247 active members on the 'Monthly Newsletter' list. The most recent signups include: Sarah Chen (joined March 15, 2024), Marcus Johnson (March 14, 2024), and Elena Rodriguez (March 13, 2024). The oldest active subscriber is David Park, who joined on January 8, 2022. Average signup rate over the past 30 days is 42 new members per week. This is an illustrative example showing how the MCP retrieves and summarizes member data from your Laposta account.

Notes

This example demonstrates read-only list querying. Requires API key with read permissions for the specified list. Response time depends on list size — large lists (10k+ members) may take several seconds to fetch. The MCP returns raw member data that the AI then summarizes into human-readable insights.

Prompt

@Laposta add a new custom field called 'Industry' to our B2B contacts list with options: SaaS, Healthcare, Finance, Retail, Other

Output

Custom field 'Industry' has been created on the 'B2B Contacts' list as a select-type field with five options: SaaS, Healthcare, Finance, Retail, and Other. The field is now available for all new and existing members. Existing members will have this field set to empty until you update their records. You can now use this field for segmentation in campaigns or update member records to populate it. This is an illustrative example of how the MCP modifies list structure.

Notes

This write operation is permanent and immediately affects list schema. All future member additions must account for this field. If you later delete this field, all stored values are lost. Requires API key with write permissions. Consider testing schema changes on a duplicate list first before applying to production lists with active campaigns.

Prompt

@Laposta create a webhook that notifies our Slack channel whenever someone unsubscribes from any list, and summarize what events we should monitor

Output

Webhook created successfully. It will POST to your Slack webhook URL whenever a 'deactivated' event occurs on any monitored list. Laposta supports these event types: 'subscribed' (new opt-ins), 'modified' (profile updates), and 'deactivated' (unsubscribes or bounces). For churn monitoring, you should track 'deactivated' events. For engagement analysis, combine 'subscribed' and 'modified' events. Each webhook payload includes member email, list ID, timestamp, and the specific action taken. This illustrative example shows how the MCP configures real-time integrations.

Notes

Webhooks fire immediately and cannot be paused — only deleted. Test your endpoint's response handling before going live, as Laposta expects a 200 status within 5 seconds or it will retry. You'll need your destination system's webhook URL ready. Webhook creation requires write permissions and affects all future list events matching the configured triggers.

Use-case deep-dives

Event signup list cleanup

When Laposta MCP handles post-event subscriber hygiene

A 6-person events team runs quarterly webinars and needs to archive attendee lists after each session without deleting the list structure. The Laposta MCP's Clear All Members From List tool removes all active subscribers in one call while preserving custom fields and webhook configs for the next event cycle. This works when your team reuses list templates across events and needs fast bulk cleanup between campaigns. The trade-off: the operation is permanent with no undo, so you need a pre-flight export step if historical attendee data matters for reporting. If your team runs more than 8 events per quarter or needs granular member segmentation, you'll hit the limits of manual list management and should look at a dedicated event platform. For teams running 2-4 recurring campaigns per year with under 5,000 subscribers per list, this MCP gives you programmatic list hygiene without leaving your AI workspace.

Customer onboarding drip setup

Laposta MCP for SaaS trial-to-paid email sequences

A 3-person SaaS startup onboards 40-60 trial users per month and triggers email sequences based on product usage milestones. The Laposta MCP's Create Member and Create Webhook tools let you add subscribers with custom fields (trial_start_date, feature_flags, account_tier) and listen for deactivation events when users churn. This setup works when your onboarding logic lives in a single codebase and you need real-time sync between product events and email campaigns. The boundary: Laposta's 24 tools cover list and member CRUD but lack advanced automation like conditional splits or A/B testing, so you're building sequence logic in your app, not the email platform. If your sequences branch on more than 3 conditions or you need visual campaign builders for non-technical teammates, you'll outgrow this fast. For early-stage teams sending linear drip campaigns to under 500 active trials, the MCP keeps email ops in the same workspace as product work.

Newsletter subscriber import from CRM

When Laposta MCP bridges CRM-to-newsletter sync gaps

A 5-person content team publishes a weekly newsletter and manually exports 1,200 subscribers from HubSpot every Monday to sync opt-in status and custom tags. The Laposta MCP's Create Custom Field and Create Member tools automate the import by mapping CRM fields (industry, company_size, content_preferences) to Laposta list attributes in a scheduled workflow. This wins when your CRM is the source of truth for subscriber metadata but lacks native Laposta integration, and your team can't justify a Zapier seat for one weekly sync. The catch: the MCP handles create and update operations but doesn't diff existing members, so you're doing full-list upserts unless you build deduplication logic upstream. If your subscriber base grows past 5,000 or you need bidirectional sync (email engagement back to CRM), the manual orchestration overhead makes a dedicated integration tool the better call. For small teams syncing under 2,000 subscribers weekly with one-way data flow, this MCP closes the gap without adding another SaaS bill.

Frequently asked

What does the Laposta MCP do in Switchy?

It connects your Laposta email marketing account so AI agents can manage subscriber lists, custom fields, and webhooks without switching apps. Agents can create lists, add or remove members, define custom subscriber attributes, and set up event notifications. Useful when you're building automated workflows that need to sync contacts or trigger campaigns based on other data sources.

Do I need admin access to connect Laposta?

You need a Laposta API key, which typically requires account owner or admin permissions to generate. The key grants full access to your lists, members, and webhooks, so only connect accounts you control. If you're on a team plan, check with your Laposta admin before generating keys—Laposta doesn't offer granular read-only API access.

Can the MCP send actual email campaigns through Laposta?

No. The MCP manages lists, subscribers, custom fields, and webhooks—it doesn't trigger campaigns or send emails. You still create and send campaigns through Laposta's web interface or their separate campaign API. Use this integration to keep subscriber data in sync, not to replace your email sending workflow.

How is this different from using Laposta's web dashboard?

The MCP lets AI agents perform bulk operations and cross-reference Laposta data with other tools in your workspace without manual CSV uploads or form-filling. For example, an agent can pull contacts from your CRM, create a Laposta list, add members with custom fields, then set up a webhook—all in one prompt. The dashboard is still better for designing emails and reviewing analytics.

Who on the team should connect this integration?

Whoever owns your Laposta account and understands your list structure. The MCP can permanently delete lists and members, so connect it in a workspace where team members know which lists are production versus test. If multiple people manage email marketing, consider creating a dedicated Switchy workspace for Laposta operations to avoid accidental deletions.

Data last verified 607 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.