activity-signals-run-2026-04-07

Partnership activity signals — ingest run

Date (local): 2026-04-07
Skill: partnership-activity-signals
Source order: Gmail → Slack → HubSpot + manual (per skill)

Summary

This run aggregates observable signals used for the pulse draft and EOD payload prep. Full Gmail/HubSpot depth requires live MCP/API access in-session; items below include repo + recent Slack MCP pulls used for the 2026-04-07 orchestrator pass.

Evidence by source

Slack (sample — partner-relevant channels)

Partner	Channel	Recency	Signal
Amplitude	#partnership-amplitude	Apr 2026	Contact transition (Hugo → Victoria); blog/event thread
Mixpanel	#partnership-mixpanel	Feb 2026	Event debrief, testimonial ask, Austin follow-ups
MotherDuck	#partner-motherduck	Mar–Apr 2026	OH cancel (0 reg); case-study drops
Polytomic	#vendor-polytomic	Mar–Apr 2026	Connector support, Calendly ask

#sales-partnerships (internal ops)

• Talisma / CorralData / tiering / capacity threads (Jan–Mar 2026) — used for Talisma + Corral narrative.

HubSpot / Gmail

• Not fully replayed in this automated doc. EA + EOD flow should attach timeline links per partner on approval.

Manual (declared)

• Snowflake: doc refresh 2026-04-06 in vault (PARTNER_CONTROL_CENTER.md).

Deduplication

• Single attribution per thread where Slack + email overlap (none duplicated in this summary).

Next

• Feed structured evidence[] into eod-payload-2026-04-07.json after Robert’s review of proposed notes/tasks.