Lupper

Delete a draft automation. Running or paused automations cannot be deleted here.

Create a draft automation from a template. It is never started here. The reply lists problems, missing pieces, and whether it is ready. Start it with lupper_automations_activate (API key only), or in the app.

Get one automation: name, status, trigger, who is in the flow, opens, clicks, and revenue. Does not edit the flow.

Pause a running automation. People already in the flow wait until it is resumed.

List automation templates that can be created with lupper_automations_from_template. Filtered to the company industry. Each template shows its trigger, steps, and what it needs (a segment, a URL, an email). Start here.

Change the name, steps, or settings of an automation. Only drafts and paused automations can change. Pause a running one first. Send the full nodes and edges when you change steps.

Check a flow without saving it. Returns problems and what would block it from starting. Saves nothing. Needs write access because it is sent as a POST.

Runs every check a send would run (verified sending domain, spam score, footer and legal info, billing, quota, audience, content, compliance) for one email or SMS campaign draft, and tells you what blocks it. Sends nothing and changes nothing.

List campaigns synced from connected tools (such as Rule) and paid ads, with reporting fields. For email that Lupper sent, use lupper_email_campaigns. from and to limit the list to campaigns sent in that range, for example 2026-03-01. Does not send.

Get one synced or paid-ads campaign with reporting fields. For email that Lupper sent, use lupper_email_campaign_report. Does not send.

Companies this connection may use. Pass one of these ids as company on other tools when more than one is listed.

Permanently delete one customer profile by id. This cannot be undone. An API key is required.

Where the Lupper public API is documented, and what this MCP connection can do. Read covers campaigns, reporting (account email/SMS, automation analytics, conversions), segments, profiles (timeline, orders, consent, GDPR export), templates, onsite, SMS drafts/analytics, and send-request status. Write (OAuth lupper:write or API key) can update profiles/events/suppressions, save email or SMS drafts, create/update segments and members, and create a send approval request. An API key is required to delete profiles, manage webhooks, read audit logs (admin), or otherwise destroy data. No tool sends email or SMS directly: use lupper_campaign_preflight then lupper_request_send; a human must approve in the Lupper UI.

Email performance for the whole account over a date range: sent, delivered, opened, clicked, bounced, complained and unsubscribed totals, rates, a day-by-day trend, top campaigns, inbox providers and email clients. Rates are percentages from 0 to 100. Defaults to the last 30 days of marketing email. Read-only; does not send.

Purchases and revenue attributed to one email campaign sent by Lupper: conversions, revenue, average order value, conversion rate (percent of clicks), currency, and a short sample of orders without customer details. For synced campaigns from other tools use lupper_synced_campaign_conversions. Read-only.

Links clicked in an email campaign, with unique and total clicks per link. Use lupper_email_campaign_recipients with url to see who clicked one link.

Who received an email campaign and what they did: opened, clicked (with links), bounced, complained, or unsubscribed. Filter by status or by one clicked link. Paginated. For a full export, call the API with format=csv.

Report for one email campaign or automation email that Lupper sent: delivered, unique and total opens and clicks, bounces, complaints, unsubscribes, rates, and clicked links. Rates are fractions from 0 to 1. Open and click rates use delivered as the base.

Day-by-day results of one email campaign that sends repeatedly, newest first: sent, delivered, opened, clicked, bounced and open/click rates in percent per day. Defaults to the last 30 days; capped at 60 days. Read-only.

Report for one email campaign: audience size, sent count, deliverability, most clicked links, A/B test results, list and inbox-provider breakdown. Condensed: leaves out warm-up and forecast detail. For the full report with every recipient, use lupper_email_campaign_report. Read-only.

List email campaigns and automation emails that Lupper has sent or is sending, with sent, opened, and clicked counts. Use the id with lupper_email_campaign_report. Leaves out drafts. Does not send.

Save a new email draft as blocks in the visual editor. Needs write access. Does not send. A person reviews it in the editor.

List email drafts. Does not create or send them.

Sender and deliverability health for the account: status ok, warning or paused, the reason, how many warnings in the last 90 days, and recent bounce and complaint counts. Read-only. Does not change sending status.

List email templates so a draft can start from one. Returns id, name, and subject. Does not send.

The people who opened or clicked the most email in a date range. Returns personal data: each row has the person's email address and name. Rates are percentages from 0 to 100. Defaults to the last 30 days, top 20 by clicks. Read-only.

Record one event. Needs write access. Does not delete events.

List recent events. Does not create events.

List onsite campaigns: name, type, status, and conversions. Does not create, edit, or publish them. Use lupper_onsite_stats for views and conversions over time.

Daily onsite views and conversions. from and to are dates such as 2026-03-01. Omit them for the last 30 days. Does not publish.

List orders for the company. Cap is 50.

List catalog products.

Automation runs for one profile, newest first: which automation, what step, and the outcome. Returns at most 100 per call (default 25). Does not start, stop, or edit automations.

Switch email or SMS marketing consent on or off for one existing profile. The change is recorded on the profile's timeline with this connection as the source. Switching consent OFF is always allowed and needs no confirmation. Switching it ON is only for a person who has actually agreed: set consent_basis_confirmed to true to say so. Someone who unsubscribed, opted out, or whose address bounced cannot be switched back on. To block an address from every send, use lupper_suppressions_create instead. Needs write access. It does not delete the profile.

Create a profile. Needs write access. Does not delete.

Everything held about one person, for a data access request: the full profile (including consent), and their events, site visits, orders, customer records, identity links, and list memberships. Each long section shows the newest rows up to per_section (default 25, max 100) with the true counts; for a complete export of a large history, pull GET /api/v1/profiles/{id}/export through the API. Every export is written to the audit log. It contains personal data: share it only with the person it is about. Does not change or delete anything.

Get one profile by id. Does not change it.

Import profiles from CSV text. The first line must be a header row with an "email" column; other columns such as first_name, last_name, and phone are matched by name. Up to 1000 rows per call; repeat for more. Existing profiles are updated unless duplicate_strategy is "skip". An API key is required. Rows are processed one by one, so check imported_count and error_samples in the answer. Only include a consent column set to true for people who agreed; the import does not check this. It does not delete profiles or send email.

List profiles. Does not create, update, or delete.

Orders for one profile, newest first, with status, total, and the line items. Open carts are included. Returns at most 100 per call (default 20). Does not change anything.