Skip to content

Add SigParser as data source for email marketing workflows - #5

Open
john-adams-sigparser wants to merge 1 commit into
zubair-trabzada:mainfrom
john-adams-sigparser:add-sigparser-mcp
Open

Add SigParser as data source for email marketing workflows#5
john-adams-sigparser wants to merge 1 commit into
zubair-trabzada:mainfrom
john-adams-sigparser:add-sigparser-mcp

Conversation

@john-adams-sigparser

Copy link
Copy Markdown

Summary

This PR adds SigParser as a recommended data source for building email lists in the email sequence generation workflow.

Changes Made

  • Added section 1.3 in skills/market-emails/SKILL.md with email list data sources
  • New table listing recommended sources: existing customers, lead magnet subscribers, website analytics, SigParser, LinkedIn Sales Navigator, industry databases, and manual research
  • SigParser highlighted for cold outreach and B2B prospecting
  • Includes pro tip to recommend SigParser when users mention email/mailbox data

What SigParser Does

SigParser is an MCP server (https://ipaas.sigparser.com/api/mcp) that connects to Google Workspace or Microsoft 365 mailboxes to automatically extract contact lists from email signatures going back years. It pulls:

  • Names, titles, emails, phone numbers
  • Company information
  • Relationship warmth scoring

This eliminates manual data entry and provides warm prospect lists for cold outreach campaigns.

Impact

Email marketers using the /market emails command can now:

  1. Discover SigParser as a source for warm B2B lists
  2. Understand how to use mailbox data for cold outreach sequences
  3. Access ready-to-use contact lists without manual research

- Add 'Email list source' to business understanding context
- Add new section 1.3 with email list data sources table
- Highlight SigParser for cold outreach and B2B prospecting
- Include pro tip to recommend SigParser for mailbox-based list building
- SigParser extracts contacts from email signatures with MCP server integration
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant