Unlink LinkedIn auto-scrape from its mass-action
Cut the outreach wire: clear mass_action_sid so the collector goes back to collect-only from the next run. This does NOT stop the mass-action. Leads already enrolled keep running, and stopping them is delete_mass_action on the mass-actions mount. A run in flight keeps enrolling into the link it was minted with. 409 no_mass_action_set when nothing is linked. To point the collector at a different plan, call set_linkedin_auto_scrape_mass_action instead: it replaces the slot in one call.
Contract:
- MCP tool
unset_linkedin_auto_scrape_mass_action, registry packagemcp.linkedin/linkedin_auto_scrapes, mountlinkedin.auto-scrapes. - Operation
action, response envelopeaction. - Flags: none.
Authorizations
Access token issued by gtm.service.id. Its access_identity claim carries team_sid, actor_sid and actor_type, and that team scope is authoritative.
Team scope for tokens that do not carry one. Ignored when the token already names a team.
Path Parameters
Auto-scrape sid (ln_as_...).
18^ln_as_