sales-skills/sales-trigify

Trigify Platform Help

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated platform knowledge.

Ask the user:

1. What do you need help with?

   • A) Setting up social listening searches (keywords, profiles, accounts)
   • B) Building or debugging AI workflows
   • C) CRM integration (HubSpot, Attio, Apollo)
   • D) Outreach sequencing (Instantly, HeyReach, La Growth Machine, Smartlead)
   • E) Credit management and optimization
   • F) Competitor monitoring or signal analysis
   • G) API or webhook integration
   • H) Something else — describe it

2. Which Trigify plan are you on?

   • A) Starter ($40/mo — 25 searches, 4K credits)
   • B) Max ($199/mo — unlimited searches, 40K credits, Social Actions)
   • C) Enterprise (custom)
   • D) Free trial / not sure

Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.

Step 2 — Route or answer directly

| If the question is about... | Route to... | |---|---| | Social listening strategy, choosing tools | /sales-social-listening [question] | | Buyer intent signals beyond LinkedIn | /sales-intent [question] | | CRM selection or comparison | /sales-crm-selection [question] | | Cold email sequence strategy | /sales-cadence [question] | | Contact enrichment strategy | /sales-enrich [question] | | Prospect list building strategy | /sales-prospect-list [question] |

When routing, provide the exact command: "This is a {problem domain} question — run: /sales-{skill} {user's original question}"

Step 3 — Trigify platform reference

Read references/platform-guide.md for the full platform reference — capabilities, pricing, data model, integration recipes, code examples.

Answer the user's question using only the relevant section. Don't dump the full reference.

Step 4 — Actionable guidance

Focus on the user's specific situation:

1. Signal noise — tighten keyword Boolean queries, use profile monitoring for high-value targets, set up If Condition nodes to filter low-intent signals
2. Workflow design — start with a template, then customize triggers → enrichment → routing. Use Jarvis AI for natural language workflow creation
3. Credit optimization — monitor credit usage in Account Settings, reduce search frequency on Starter, use Multi Post Trigger to batch signals
4. Integration debugging — check API key permissions, verify CRM field mapping, test with simple workflows first

If you discover a gotcha, workaround, or tip not covered in references/learnings.md, append it there.

Gotchas

Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.

• Social Actions and Social Engagement require Max plan ($199/mo). Starter users cannot engage with posts from workflows — they can only listen and route data. Budget for Max if you need automated engagement.
• Credits burn faster than you expect. Every workflow step consumes credits. A workflow with enrichment + CRM push + Slack notification costs 3-4x what a simple alert costs. Monitor usage weekly on Starter.
• Job change signals can lag 2-4 weeks. LinkedIn doesn't expose real-time job updates. Trigify depends on profile updates appearing in the social graph, which often delays.
• CRM sync can break after platform updates. Both Trigify and CRM updates can break field mappings. Test integrations after any update and keep a simple "ping" workflow to catch breakage early.
• API is minimal — workflows are the primary automation surface. Don't expect a full CRUD API. The single documented endpoint returns leads; everything else runs through workflows and native integrations.
• LinkedIn engagement context is thin. A "liked a competitor's post" signal doesn't tell you if the prospect has budget, authority, or timing. Layer Trigify signals with firmographic enrichment (Clay, Prospeo) before outreach.
• BYOK and SSO/SAML are Enterprise-only. No workaround for Starter/Max plans.

Related skills

• /sales-social-listening — Social listening strategy — brand monitoring, sentiment analysis, competitive intelligence, tool comparison
• /sales-clearcue — Clearcue — GTM signal engine with signal stacking, AI qualification, MCP server (closest competitor)
• /sales-intent — Buyer intent signals and prioritization
• /sales-catchintent — CatchIntent — AI intent detection across Reddit, X, HN, Bluesky with MCP server
• /sales-octolens — Octolens — developer-first social listening with MCP server and REST API
• /sales-buska — Buska — social listening for lead gen across 30+ platforms with intent scoring
• /sales-do — Not sure which skill to use? The router matches any sales objective to the right skill. Install: npx skills add sales-skills/sales --skill sales-do

Examples

Example 1: Track competitor LinkedIn engagement

User says: "I want to know who's engaging with my competitor's LinkedIn posts so I can reach out to them" Skill does:

1. Sets up Profile Monitoring on the competitor's LinkedIn company page
2. Creates a workflow: New Post Trigger → Get Post Likes → Get Post Comments → Person Enrichment → If Condition (filter by ICP) → Push to HubSpot
3. Explains credit cost per workflow run Result: Automated pipeline of competitor-engaged prospects flowing into CRM

Example 2: Build a signal-to-outreach workflow

User says: "How do I automatically add people who engage with AI-related posts to my Instantly sequence?" Skill does:

1. Creates a keyword listening search for AI-related terms
2. Builds workflow: New Post Trigger → Sentiment Agent (filter positive) → Person Enrichment → Prospeo Email Enrichment → Instantly integration → add to sequence
3. Notes credit consumption and suggests batching with Multi Post Trigger Result: Warm leads automatically enrolled in cold email sequence

Example 3: Debug CRM sync issues

User says: "My Trigify workflow stopped pushing leads to HubSpot after I updated my HubSpot plan" Skill does:

1. Checks workflow logs for error messages
2. Verifies HubSpot API key is still valid (plan changes can revoke scopes)
3. Tests with a minimal workflow (trigger → HubSpot push only)
4. Suggests re-authenticating the HubSpot integration in Trigify settings Result: CRM sync restored with clear debugging steps

Troubleshooting

Too many low-intent signals drowning useful alerts

Symptom: Dashboard flooded with LinkedIn engagement signals that aren't worth acting on Cause: Keywords too broad, no intent filtering in workflow, monitoring too many profiles Solution: Narrow keyword Boolean queries (use AND/NOT operators). Add an If Condition node after the trigger to filter by engagement count (e.g., >3 interactions in 30 days). Use Profile Monitoring for high-value target accounts instead of broad keyword searches. On Starter plan (25 searches), prioritize quality over quantity.

Credits running out before month end

Symptom: Credit quota exhausted mid-month, workflows stop processing Cause: Too many enrichment steps per workflow, high search frequency, unused workflows still active Solution: Audit credit usage in Account Settings → Credit Usage. Disable or pause inactive workflows. Reduce enrichment to only leads that pass intent filters. Use Scheduled Trigger instead of real-time for non-urgent monitoring. Consider Max plan ($199/mo) for 40K credits if Starter's 4K is consistently insufficient.

Workflow not triggering on new LinkedIn posts

Symptom: Created a workflow with New Post Trigger but it never fires Cause: Listening search not connected to workflow, search frequency too low, platform data delay Solution: Verify the listening search is active and linked to the workflow trigger. Check search frequency settings — daily searches may miss fast-moving conversations. LinkedIn data typically arrives within 24 hours. Test with a manual trigger first to confirm the rest of the workflow works.