• Features
  • Pricing
  • Migration
  • Integrations
  • Resources

Get new subscriber notifications with Omnisend MCP

Quick sign up | No credit card required

Drive sales on autopilot with ecommerce-focused features

See Features

Want to know when someone signs up through one of your forms? With Omnisend MCP, you can set up notifications for new subscribers and choose how often you want to check for updates.

This guide covers two approaches: a no-code option using Claude Cowork, and a more flexible workflow in n8n that can send notification emails automatically.

What is MCP?

MCP stands for Model Context Protocol, an open standard that connects AI assistants to your tools and data. Once you’ve connected the Omnisend MCP server to your AI assistant, it can read your subscriber data and use it in workflows like the ones below.

Option 1: Scheduled notifications with Claude Cowork

Claude Cowork lets you schedule a recurring task that checks for new subscribers and creates an email draft with a summary. You can run the task daily, hourly, or weekly.

Image via Omnisend

How to set it up

Open Claude Cowork and create a new task using a prompt like this:

Prompt example

Use the Omnisend MCP. Once a customer subscribes to my form named [form name], create a Gmail draft with a summary of the new subscriber details. Remind me daily.

You can customise a few things:

  1. Choose all forms or specify one form by name
  2. Choose your email provider, such as Gmail or Outlook
  3. Set how often you want the task to run, such as daily, hourly, or weekly

When Claude finishes, you’ll see a scheduled chat that runs on your chosen cadence.

Subscriber notifications with Omnisend MCP: A pop-up window titled Edit scheduled task displays fields for Name, Description, and Notes, with options for Frequency and Time. The interface includes buttons for saving or canceling the task at the bottom.
Image via Claude

Good to know

Subscriber notifications with Omnisend MCP: Screenshot of a Gmail inbox with the Drafts folder selected, showing 36 drafts. The highlighted draft email is titled 1 new subscriber(s) from... with other drafts listed below, some with no subject.
Image via Gmail

Direct sending from Gmail isn’t supported in this setup. Instead, Claude creates a draft email that summarises the new subscribers collected during the selected period.

You can set up the task so you only receive a draft when there are new subscribers.

Subscriber notifications with Omnisend MCP: A screenshot of an email notification showing a new subscriber alert, including a table with the subscribers email (hello@lokalus.lt), subscription date (2026-05-29 13:56 UTC), and blank name fields.
Image via author

Option 2: Automated emails with an n8n workflow

Subscriber notifications with Omnisend MCP: A dark-themed workflow diagram showing steps: Schedule Trigger, AI Agent, decision (If), and Send a message (Gmail). There are branches for Anthropic Chat, Simple Memory Model, and MCP Client under the AI Agent step.
Image via author

Use n8n if you want notification emails to be sent automatically. This setup takes more configuration than Claude Cowork, but it gives you more control over the schedule, logic, and email content.

Here’s how to set up a workflow that checks for new subscribers on a schedule and emails you the details.

Nodes you’ll need

NodePurposeConfiguration Detail
Schedule TriggerInterval ManagementSet to execute every 30 minutes.
AI AgentData Retrieval and AnalysisSet up a prompt, connect a model and add memory for the agent so it can see if there are new contacts since the last check.
If NodeLogic FilterProceed only if the subscriber count is greater than 0.
Gmail NotificationSend an email with contact details to the recipient.

The prompt for the AI Agent

Use a prompt like this in the AI Agent node:

Check your memory for the latest contact. Use the MCP tools to get contacts and check whether any new contacts were created since the last run.

In the output, list the new contacts and their details, such as phone number and email. The message must contain nothing else — only the new contacts and their details, in plain, human-readable language. If there are no new contacts, the output must be exactly “N/A”.

Then update the memory with the latest contact.

Because the agent stores the most recent contact in memory, each run only reports people who signed up since the previous check. This helps you avoid duplicate notifications.

Watch it in action

See a walkthrough of the n8n workflow here: View the demo video.

Which option should you choose?

Use Claude Cowork if you want a simple scheduled check and don’t mind reviewing a draft before sending. Use n8n if you want notification emails to send automatically, and you need more control over the workflow.

Both options use Omnisend MCP to check for new subscribers, so you can stay informed without manually reviewing your form data.

Subscribe and don’t miss any updates!

No fluff, no spam, no corporate filler. Just a friendly letter, twice a month.