Trigger Mapping logo

Trigger Mapping

Community
kenny589
trigger-mapping

Map business events to outreach triggers. Define which events warrant immediate contact, what to say when they happen, and how to build event-driven outbound campaigns.

Overview

Publisherkenny589
Repositorygtm-flywheel
Skill nametrigger-mapping
Stars
71
Forks
26
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by kenny589 on GitHub. Read the source before you install it.

Installation

Install the Trigger Mapping AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/kenny589/gtm-flywheel/tree/main/signal-scoring/trigger-mapping
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/kenny589/gtm-flywheel.git /tmp/gtm-flywheel
mkdir -p .claude/skills
cp -r /tmp/gtm-flywheel/signal-scoring/trigger-mapping .claude/skills/trigger-mapping
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Trigger Mapping in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Trigger Mapping on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Trigger Mapping is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Trigger Mapping

When to Use

  • Designing event-driven outbound campaigns (vs. list-based batch sending)
  • Building automation rules for when to contact a prospect
  • Creating playbooks for SDRs on which events to act on and how
  • Setting up n8n, Zapier, or custom workflows that fire outreach on specific triggers

Framework

Trigger-Based vs. List-Based Outbound

ApproachHow It WorksReply RateScalability
List-basedBuild a list → Write copy → Send to everyone2-5%High volume, lower quality
Trigger-basedDetect event → Match to angle → Send targeted message8-20%Lower volume, higher quality
HybridBuild qualified list → Wait for trigger → Send signal-matched message10-25%Medium volume, highest quality

The hybrid approach is the gold standard. You pre-qualify the list (ICP match), then monitor for triggers that tell you WHEN to reach out. This gives you the best of both worlds: targeted copy with perfect timing.


The Trigger Map: 12 Core Business Events

Every trigger needs four components defined: the event, the detection method, the message angle, and the urgency window.

Trigger 1: New Funding Round
ComponentDetail
EventCompany raises Seed, Series A, B, C, or PE investment
DetectionCrunchbase alerts, TechCrunch, LinkedIn announcements, press releases
Why it mattersNew capital = growth mandate. Board expects 2-3x growth. Sales/marketing investment imminent.
Urgency windowContact within 2 weeks of announcement. After 30 days, the signal is stale.
Message angle"Post-{{round}}, most teams invest in [your category] within 90 days. Here's what works."
Persona to targetCEO (Seed), VP Sales/CRO (Series A+), RevOps (Series B+)
Trigger 2: Hiring for Target Role
ComponentDetail
EventCompany posts job opening for a role your product/service supports
DetectionLinkedIn Jobs, Indeed, Glassdoor, company careers page, PredictLeads
Why it mattersHiring = active investment in that function. They're building the team that needs your solution.
Urgency windowContact within 1 week of posting. After 4 weeks, the role may be filled or paused.
Message angle"Hiring {{role}} usually means you're building the {{function}} engine. Here's what teams at your stage do first."
Persona to targetThe hiring manager (listed on job post) or their boss
Trigger 3: Leadership Change
ComponentDetail
EventNew executive hired in your target department (VP Sales, CMO, CRO, etc.)
DetectionLinkedIn profile changes, press releases, company announcements
Why it mattersNew leaders have a 90-day mandate to make changes. They're evaluating everything, including vendors.
Urgency windowContact between day 14-60 of their new role. Too early = they're still onboarding. Too late = they've already decided.
Message angle"Most new {{title}}s in the first 90 days need to [outcome you help with]. Here's what we see working."
Persona to targetThe new executive directly
Trigger 4: Tech Stack Change
ComponentDetail
EventCompany adds, removes, or switches a technology in their stack
DetectionBuiltWith, Wappalyzer, job description requirements, G2 reviews
Why it mattersTech changes indicate a strategic shift. Adjacent purchases often follow.
Urgency windowContact within 2 weeks of detection. Stack changes take 3-6 months to settle.
Message angle"Teams migrating to {{newTool}} usually also rethink their {{yourCategory}} approach."
Persona to targetThe person who owns the stack (RevOps, VP Sales, CTO depending on category)
Trigger 5: Competitor Churn
ComponentDetail
EventCompany stops using a competitor's product
DetectionBuiltWith (tech removal), G2 negative reviews, LinkedIn posts about switching
Why it mattersThey had the need, spent the budget, and are now actively looking for alternatives.
Urgency windowImmediate. This is the highest-urgency trigger. Contact within 48 hours if possible.
Message angle"Teams moving off {{competitor}} typically care most about {{differentiator}}. Here's how we handle that."
Persona to targetThe person who made the original purchase decision
Trigger 6: Product Launch
ComponentDetail
EventCompany launches a new product, feature, or service
DetectionPress releases, Product Hunt, company blog, social media
Why it mattersNew products mean new go-to-market motions, new ICPs, and new pipeline needs.
Urgency windowContact 1-4 weeks after launch. During launch week, they're too busy.
Message angle"New product launches usually mean new audience, new pipeline targets. How's the GTM plan?"
Persona to targetVP Marketing, VP Sales, or Product Marketing lead
Trigger 7: Earnings/Revenue Event
ComponentDetail
EventMissed targets, layoffs, reorgs, or strong growth quarter
DetectionSEC filings, press releases, Glassdoor, LinkedIn
Why it mattersRevenue pressure creates urgency. Growth creates opportunity. Both open doors.
Urgency window1-3 weeks after announcement
Message angle (miss)"When the board is asking about pipeline, efficiency becomes the priority."
Message angle (growth)"Scaling from ${{X}}M to ${{Y}}M usually means outbound becomes a must-have."
Trigger 8: Conference/Event Attendance
ComponentDetail
EventProspect is attending, speaking, or sponsoring a relevant conference
DetectionEvent websites, speaker lists, LinkedIn posts about attending
Why it mattersThey're investing time and money in the topic. They're in learning mode.
Urgency windowContact 1-2 weeks BEFORE the event or within 1 week after.
Message angle (before)"Ahead of {{event}} — thought you'd want to see this relevant to {{topic}}."
Message angle (after)"Hope {{event}} was great. Based on the sessions, you might find this useful."
Trigger 9: Content Publication
ComponentDetail
EventProspect publishes a LinkedIn post, blog article, or podcast episode on a relevant topic
DetectionLinkedIn feed monitoring, Google Alerts, podcast directories
Why it mattersThey're actively thinking about this topic. Your email arrives in a moment of relevance.
Urgency windowWithin 48 hours of publication. Reference stale content and you look like a stalker, not a peer.
Message angle"Your [post/article] about {{topic}} resonated. We're seeing the same pattern across our clients."
Trigger 10: Award or Recognition
ComponentDetail
EventCompany or individual wins an award, makes a "Top X" list, or receives public recognition
DetectionPress releases, industry publications, LinkedIn
Why it mattersPositive momentum. They're growing and feeling good — receptive to investment conversations.
Urgency windowWithin 1-2 weeks. Congratulations expire quickly.
Message angle"Congrats on {{award}}. Companies at your trajectory usually need {{what you offer}} next."
Trigger 11: M&A Activity
ComponentDetail
EventCompany acquires, is acquired, or merges with another company
DetectionPress releases, SEC filings, Crunchbase, news alerts
Why it mattersM&A creates chaos and opportunity. Integration needs, new targets, efficiency mandates.
Urgency window30-90 days post-announcement (integration planning phase)
Message angle"Post-acquisition teams usually need to consolidate tools and scale faster. Here's what helps."
Trigger 12: Regulatory/Market Change
ComponentDetail
EventNew regulation, market shift, or industry disruption affects the prospect
DetectionIndustry news, regulatory filings, analyst reports
Why it mattersExternal forces create urgency that wasn't there before. "We need to adapt" = buying energy.
Urgency window2-8 weeks after the change is announced
Message angle"With {{regulation/change}}, most {{industry}} teams are rethinking {{category}}. Here's what we're seeing."

Trigger Prioritization Matrix

When multiple triggers fire simultaneously, prioritize by:

PriorityTrigger TypeWhy
1Competitor churnActive buyer, proven budget, immediate need
2Hiring for target roleBudget allocated, timeline set
3First-party signals (website visit, content download)Direct engagement with your brand
4Leadership change (< 60 days)Evaluation window open
5Funding round (< 30 days)Capital available, growth mandate
6Tech stack changeStrategic shift underway
7Content/social signalsProblem is top of mind
8Events/conferencesLearning mode, networking mindset
9Product launchNew GTM needs
10Awards/recognitionPositive momentum

Building Trigger-Based Campaigns

Campaign Architecture
TRIGGER CAMPAIGN: {{triggerName}}

Trigger: {{event description}}
Detection: {{how you find out}}
Filter: {{ICP criteria that must also be true}}
Volume estimate: {{expected triggers per month}}

Sequence:
Step 1 (Day 0): Trigger-specific email
Step 2 (Day 3): New value angle (resource, case study)
Step 3 (Day 7): Social proof or different angle
Step 4 (Day 14): Breakup / referral

Personalization requirement:
- Step 1: Must reference the specific trigger + company
- Steps 2-4: Can use bucket personalization

Success metrics:
- Target reply rate: 10-20% (trigger campaigns should beat list-based by 2-3x)
- Target positive reply rate: 5-12%

Templates

Trigger Map Document

# Trigger Map: {{Company/Product Name}}
# Updated: {{date}}

| # | Trigger | Detection Source | Urgency Window | Message Angle | Target Persona | Est. Monthly Volume |
|---|---------|-----------------|----------------|---------------|----------------|---------------------|
| 1 | ___ | ___ | ___ | ___ | ___ | ___ |
| 2 | ___ | ___ | ___ | ___ | ___ | ___ |
| 3 | ___ | ___ | ___ | ___ | ___ | ___ |

Trigger Playbook (For SDR Team)

TRIGGER: {{trigger name}}

When you see this:
{{description of the event}}

Do this immediately:
1. Verify the lead passes ICP filter (size, industry, stage)
2. Find the right contact ({{suggested title}})
3. Check if they're already in an active campaign
4. If clear → Add to {{campaign name}} sequence
5. If in existing campaign → Flag for review

Template to use:
Subject: {{subject line template}}
Body: {{body template with variables}}

DON'T:
- {{common mistake 1}}
- {{common mistake 2}}

Tips

  • Build trigger campaigns for your top 3 triggers first. Don't try to monitor everything. The Pareto principle applies: 3 triggers will generate 80% of your signal-based pipeline.
  • Trigger-based campaigns should always outperform list-based campaigns. If they don't, either your signal detection is lagging (stale triggers) or your message doesn't connect the trigger to your value.
  • The urgency window is real. A "congrats on the funding round" email 3 months after the announcement isn't relevant — it's lazy. Set up monitoring so you catch triggers within 48 hours.
  • Combine trigger-based outreach with ongoing list-based campaigns. Trigger campaigns are your high-ROI sniper shots. List campaigns are your air cover. You need both.
  • Track trigger-to-meeting conversion by trigger type. This data is gold — it tells you exactly which business events create the most pipeline for your specific product.

Progressive disclosure: load trigger automation workflows and integration configs only when building a specific trigger campaign.

Frequently asked questions

What does the Trigger Mapping AI skill do?

Map business events to outreach triggers. Define which events warrant immediate contact, what to say when they happen, and how to build event-driven outbound campaigns.

Why use Trigger Mapping on TypingMind?

Because you install it once and use it with any model. Trigger Mapping is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Trigger Mapping in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/kenny589/gtm-flywheel/tree/main/signal-scoring/trigger-mapping. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Trigger Mapping?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Trigger Mapping?

As many as you like. As long as a model supports skills, you can use Trigger Mapping with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Trigger Mapping AI skill free?

Yes. It is published on GitHub by kenny589 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇