Sendlane
Sendlane is a cloud-based marketing automation platform that helps eCommerce businesses engage customers through personalized email and SMS campaigns.
Verdict
Common use cases
- Create segmentation lists during campaign planning
- Audit custom field schemas before data imports
- Spin up event-specific subscriber lists quickly
- Map CRM fields to Sendlane custom fields
- Prep list infrastructure for product launches
Integration
- Vendor
- Sendlane
- Category
- other
- Auth
- API_KEY
- Tools
- 2
- Composio slug
sendlane
Tools
- Create List
Tool to create a new list. use when you need to add a brand-new mailing list before sending campaigns.
- Get custom fields list
Tool to retrieve a list of custom fields. use when you need to list all custom fields with optional pagination.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations page. 2. Search for Sendlane in the MCP directory and click Connect. 3. You'll need a Sendlane API key — generate one by logging into your Sendlane account, going to Account Settings, then API Keys, and creating a new key with list and custom field read/write permissions. 4. Paste the API key into Switchy's connection dialog and click Authorize. 5. Once connected, open any Space and type '@Sendlane create a list called Q1 Webinar Leads' to test — the MCP should confirm the list was created and return its ID. 6. To verify custom fields work, try '@Sendlane show me all custom fields' and check that it returns your account's field definitions.
What teammates see: by default, memories from Sendlane 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
Starter prompts
Create Launch List
@Sendlane create a new list called 'Product Launch May 2024 Early Access' so we can start collecting signups for the beta program.Open in a Space →
Audit Custom Fields
@Sendlane get the complete list of custom fields in our account. I need to map our Salesforce fields before the import tomorrow.Open in a Space →
Event Attendee List
@Sendlane create a list named 'June Webinar Registrants' for our upcoming customer education session on the 15th.Open in a Space →
Check Field Pagination
@Sendlane retrieve all custom fields with pagination starting at page 1. We have over 50 fields and I need the full inventory.Open in a Space →
Segment Prep
@Sendlane create a list called 'Enterprise Trial Users - 30 Days' so we can send tailored onboarding content to this cohort.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Sendlane show me all custom fields we have set up for subscriber segmentation, paginated if there are more than 20
Retrieved 8 custom fields from your Sendlane account: 'Purchase History' (text), 'Loyalty Tier' (dropdown), 'Last Engagement Date' (date), 'Product Interest' (multi-select), 'Lifetime Value' (number), 'Preferred Channel' (dropdown), 'Birthday' (date), and 'Referral Source' (text). All fields are active and available for use in campaigns and automations. No additional pages exist.
This example demonstrates read-only access to account metadata. Requires a valid API key with read permissions for custom fields. Useful for auditing segmentation setup before building campaigns, but won't show field usage stats or subscriber counts per field value.
@Sendlane create a new list called 'Q1 2025 Webinar Registrants' so we can segment attendees for follow-up campaigns
Successfully created list 'Q1 2025 Webinar Registrants' in your Sendlane account (List ID: 47392). The list is now active and ready to receive subscribers. You can add contacts manually, via API, or through form integrations. No subscribers are currently assigned to this list.
This is a write operation that permanently adds a list to your Sendlane account. The MCP cannot delete or archive lists, so confirm naming conventions before running. Newly created lists require separate steps to import subscribers or connect opt-in forms — list creation alone doesn't populate contacts.
@Sendlane review our custom fields and suggest which ones would be most useful for a cart-abandonment campaign targeting high-value customers
Based on your 8 custom fields, I recommend using 'Lifetime Value' (to filter for high-value customers above a threshold like $500), 'Last Engagement Date' (to exclude recently active users who may convert without prompting), and 'Product Interest' (to personalize abandoned-cart messaging with relevant product categories). The 'Purchase History' text field could add context but may require parsing if it's unstructured. Consider adding a 'Cart Value' numeric field if you track individual cart amounts separately.
This synthesis example pairs the MCP's field-retrieval capability with the AI's campaign strategy reasoning. The recommendations depend on what custom fields actually exist in your account — the AI infers use cases from field names and types but cannot see subscriber data or campaign performance metrics.
Use-case deep-dives
When Sendlane MCP makes sense for one-off campaign prep
A 3-person e-commerce team launching a product drop needs to create a new subscriber list and check which custom fields exist before importing leads from a spreadsheet. The Sendlane MCP handles this in two calls: create the list, pull the custom field schema, then hand off to a CSV import tool. This works because the setup is infrequent—maybe once a quarter—and the team already uses Sendlane for sends. If you're doing this daily or need to update subscriber tags in real-time, the 2-tool limit means you'll hit the Sendlane web UI for anything beyond list creation. The MCP is a time-saver for launch prep, not ongoing list management.
Why this MCP falls short for CS workflow integration
A 6-person customer success team wants to auto-create Sendlane lists when a new enterprise client signs, then map CRM fields to email custom fields for personalized onboarding sequences. The Sendlane MCP can create the list, but it can't add subscribers, trigger automations, or update contact data—those actions aren't in the 2-tool set. You'd need to chain this with Sendlane's API directly or use Zapier for the subscriber sync. If your workflow stops at 'make a list and check field names,' this MCP works. If you need to populate or act on that list, you're building around a gap. For CS teams, the juice isn't worth the squeeze here.
When the custom fields tool solves a specific reporting pain
A solo marketing ops person at a 20-person SaaS company needs to audit which custom fields are live in Sendlane before a data migration from HubSpot. The 'Get custom fields list' tool pulls the schema in one call, no need to click through Sendlane's UI or export a CSV. This is a perfect fit: the task is a one-time lookup, the MCP requires only API key auth, and the output feeds directly into a migration plan doc. If you're doing this audit monthly or need to create/delete fields programmatically, the MCP won't help—it's read-only on fields. For the once-a-year schema check, though, it's faster than logging into Sendlane.
Frequently asked
What does the Sendlane MCP let me do in Switchy?
It connects your Sendlane email marketing account so AI agents can create mailing lists and retrieve custom field definitions. You can automate list setup before campaigns or pull field schemas for data mapping tasks. It doesn't send emails directly — it handles the structural setup work that normally requires logging into Sendlane's dashboard.
Do I need admin access to connect Sendlane?
You need a Sendlane API key, which typically requires account-level permissions to generate. Most Sendlane plans let any user create API keys from their account settings, but check with your account owner if you're on a team plan with restricted access. The key stays in Switchy's encrypted vault once you connect.
Can the Sendlane MCP send email campaigns or manage subscribers?
No. It creates lists and reads custom field definitions, but it can't send campaigns, add subscribers, or trigger automations. If you need to send emails or manage contacts, use Sendlane's native API or their dashboard. This MCP is for structural setup tasks, not campaign execution or subscriber management.
Why use this instead of Sendlane's API directly?
The MCP wraps Sendlane's API in a format AI agents understand without custom code. If you're already writing scripts or using Zapier, the API is more flexible. If you want agents to prep lists during a workflow — say, creating a segment list based on a Notion database query — the MCP saves you from writing integration glue.
Who on my team should connect the Sendlane account?
Whoever owns your Sendlane account or has API key access. Once connected, any Switchy workspace member can invoke the tools in their agent workflows. The API key permissions apply globally, so if your key can create lists, any agent using it can too. Treat it like a shared service account.