<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>GTM Tech Index: LinkedIn &amp; Social Selling changes</title>
    <link>https://gtmtechindex.com/categories/linkedin-social-selling</link>
    <atom:link href="https://gtmtechindex.com/feeds/linkedin-social-selling.xml" rel="self" type="application/rss+xml" />
    <description>Material product changes at LinkedIn &amp; Social Selling vendors, tracked by GTM Tech Index. Every entry is dated and cited to a public source.</description>
    <language>en-us</language>
    <copyright>Free to reuse with a visible link to gtmtechindex.com. Terms: https://gtmtechindex.com/use-this-data</copyright>
    <lastBuildDate>Fri, 25 Sep 2026 12:00:00 GMT</lastBuildDate>
    <ttl>720</ttl>
    <image>
      <url>https://gtmtechindex.com/icon-192.png</url>
      <title>GTM Tech Index: LinkedIn &amp; Social Selling changes</title>
      <link>https://gtmtechindex.com/categories/linkedin-social-selling</link>
    </image>
    <item>
      <title>DM Faster published version 1.6.0 of its Agent 1.0 CLI and local MCP server, which widens the top 'full' access profile from campaign…</title>
      <link>https://gtmtechindex.com/changelog/dm-faster</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6ab94d1abae534b71b03efad</guid>
      <pubDate>Fri, 25 Sep 2026 12:00:00 GMT</pubDate>
      <category>Safety / governance</category>
      <category>LinkedIn &amp; Social Selling</category>
      <category>Sales Engagement &amp; Outreach</category>
      <category>Data &amp; Enrichment</category>
      <description><![CDATA[<p>DM Faster published version 1.6.0 of its Agent 1.0 CLI and local MCP server, which widens the top 'full' access profile from campaign launch and pause to also cover inbox replies, pipeline updates and follow up cancellation under the owner's one time grant and explicit instructions. The same release lets agents edit unstarted social campaign drafts, including channel toggles, LinkedIn invite mode and note, and follow up sequences.</p><p><strong>Why it matters:</strong> Connected agents such as Claude Code or Codex can now act on prospect conversations and pipeline, not only campaign setup, so admins need to decide who holds the full profile. The agent docs still state the interface cannot send replies while listing a conversation_reply tool that queues a human confirmed reply, so buyers should confirm the review step.</p><p>Impact: Medium. Verification: Partially Verified. Type: Safety / governance.</p><p>Evidence: <a href="https://registry.npmjs.org/@dmfaster/cli">Vendor documentation</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/dm-faster">GTM Tech Index change log</a>. Free to reuse with a link back. <a href="https://gtmtechindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Woodpecker.co: Woodpecker added a Campaign API v2 endpoint, POST /v2/campaigns/create_and_run_simple_campaign, that creates and starts a one prospect…</title>
      <link>https://gtmtechindex.com/changelog/woodpecker</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6ab94d1abae534b71b03efab</guid>
      <pubDate>Thu, 24 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Sales Engagement &amp; Outreach</category>
      <category>LinkedIn &amp; Social Selling</category>
      <category>Data &amp; Enrichment</category>
      <description><![CDATA[<p>Woodpecker added a Campaign API v2 endpoint, POST /v2/campaigns/create_and_run_simple_campaign, that creates and starts a one prospect, one email campaign in a single request. It reuses or creates the prospect by email address, supports CC, BCC and optional open tracking, and queues the send through the chosen mailbox's normal sending limits.</p><p><strong>Why it matters:</strong> CRMs, internal tools and AI agents can now trigger a one to one email from a connected mailbox without building a full campaign first, while still inheriting Woodpecker's per mailbox sending limits. Teams should note the mailbox footer is not added automatically, so opt out text must be included in the message body.</p><p>Impact: Medium. Verification: Verified. Type: Product / capability.</p><p>Evidence: <a href="https://developers.woodpecker.co/docs/changelog/">Vendor documentation</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/woodpecker">GTM Tech Index change log</a>. Free to reuse with a link back. <a href="https://gtmtechindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Skylead introduced the AI List Assistant, opened from Actions &gt; Enrich with AI on a contact or company list, which answers questions about…</title>
      <link>https://gtmtechindex.com/changelog/skylead</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6ab94d1abae534b71b03efaa</guid>
      <pubDate>Thu, 24 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>LinkedIn &amp; Social Selling</category>
      <category>Sales Engagement &amp; Outreach</category>
      <category>Data &amp; Enrichment</category>
      <description><![CDATA[<p>Skylead introduced the AI List Assistant, opened from Actions &gt; Enrich with AI on a contact or company list, which answers questions about the list and proposes enrichment actions when data is missing. Each suggestion card shows what the enrichment does and its price per row, with options to save the column without running it or save and run it on the first 10 rows.</p><p><strong>Why it matters:</strong> The assistant never creates a column without user approval and shows per row cost before any credits are spent, so teams get AI driven enrichment planning with a human gate on spend and data changes.</p><p>Impact: Medium. Verification: Partially Verified. Type: Product / capability.</p><p>Evidence: <a href="https://help.skylead.io/hc/en-us/articles/51240243804305-How-to-Use-the-AI-List-Assistant">Vendor documentation</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/skylead">GTM Tech Index change log</a>. Free to reuse with a link back. <a href="https://gtmtechindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Trigify announced that its team is joining HubSpot and that the standalone Trigify platform is being retired.</title>
      <link>https://gtmtechindex.com/changelog/trigify</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6ab94d1abae534b71b03efa6</guid>
      <pubDate>Wed, 23 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product sunset</category>
      <category>Intent &amp; Signals</category>
      <category>LinkedIn &amp; Social Selling</category>
      <category>Data &amp; Enrichment</category>
      <description><![CDATA[<p>Trigify announced that its team is joining HubSpot and that the standalone Trigify platform is being retired. For customers on the standard notice period, account access, integrations, API access, monitoring and signal collection end at 11:59pm BST on 22 October 2026. Accounts will not be migrated to HubSpot and the product will not continue inside HubSpot.</p><p><strong>Why it matters:</strong> Teams that route Trigify signals into CRM, Clay or outreach workflows have under a month to export data and rebuild those automations elsewhere. Trigify states customer data will not be used by HubSpot and will be retained or deleted under Trigify's own contractual, privacy and legal obligations.</p><p>Impact: High. Verification: Verified. Type: Product sunset.</p><p>Evidence: <a href="https://www.trigify.io/">Vendor announcement</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/trigify">GTM Tech Index change log</a>. Free to reuse with a link back. <a href="https://gtmtechindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>SuperSend now allows a contact to be active in a campaign only once, across every path that adds, restores or moves contacts.</title>
      <link>https://gtmtechindex.com/changelog/supersend</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6ab94d1abae534b71b03ef9e</guid>
      <pubDate>Tue, 22 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Sales Engagement &amp; Outreach</category>
      <category>LinkedIn &amp; Social Selling</category>
      <description><![CDATA[<p>SuperSend now allows a contact to be active in a campaign only once, across every path that adds, restores or moves contacts. Bulk unarchive and transfer skip people already active in the target campaign and report restored and skipped counts, restoring or moving via PUT /v1/contact/:id returns 409 contact_already_exists, and CSV, Apollo, HubSpot and LinkedIn post interaction imports now match existing contacts case insensitively. Existing duplicates were cleaned up, keeping the enrollment that is stopped or furthest along.</p><p><strong>Why it matters:</strong> Duplicate enrollments mean the same prospect can receive a sequence twice, which drives complaints and hurts sender reputation at high volume. Teams importing from several sources (Apollo, HubSpot, CSV) get this protection without writing their own dedup logic.</p><p>Impact: Medium. Verification: Verified. Type: Product / capability.</p><p>Evidence: <a href="https://docs.supersend.io/docs/changelog">Vendor documentation</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/supersend">GTM Tech Index change log</a>. Free to reuse with a link back. <a href="https://gtmtechindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Breakcold's REST API and MCP inbox read endpoints now enforce conversation level access for user actors.</title>
      <link>https://gtmtechindex.com/changelog/breakcold</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6ab94d1abae534b71b03ef9a</guid>
      <pubDate>Tue, 22 Sep 2026 12:00:00 GMT</pubDate>
      <category>Security / compliance</category>
      <category>LinkedIn &amp; Social Selling</category>
      <category>Sales Engagement &amp; Outreach</category>
      <description><![CDATA[<p>Breakcold's REST API and MCP inbox read endpoints now enforce conversation level access for user actors. Record conversation lists filter out conversations the authenticated user cannot read, and message list and detail requests reject inaccessible conversations, while application actors keep organization scoped inbox access.</p><p><strong>Why it matters:</strong> AI agents and scripts connected through MCP or the API as a user can no longer read inbox threads that user is not permitted to see, which narrows what an assistant can pull from shared LinkedIn, email and WhatsApp conversations.</p><p>Impact: Medium. Verification: Verified. Type: Security / compliance.</p><p>Evidence: <a href="https://docs.breakcold.com/api/changelog#september-22-2026">Vendor documentation</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/breakcold">GTM Tech Index change log</a>. Free to reuse with a link back. <a href="https://gtmtechindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Snov.io added Generect as a data provider for its Pull LinkedIn profile enrichment action, fetching prospect data directly from LinkedIn…</title>
      <link>https://gtmtechindex.com/changelog/snov-io</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6ab94d1abae534b71b03ef95</guid>
      <pubDate>Mon, 21 Sep 2026 12:00:00 GMT</pubDate>
      <category>Integration / interoperability</category>
      <category>Sales Engagement &amp; Outreach</category>
      <category>Data &amp; Enrichment</category>
      <category>LinkedIn &amp; Social Selling</category>
      <description><![CDATA[<p>Snov.io added Generect as a data provider for its Pull LinkedIn profile enrichment action, fetching prospect data directly from LinkedIn at the moment enrichment runs and returning 30+ data points such as personal and company information, experience and skills. Generect costs 4 tokens per prospect versus 1 token for Snov.io's own database, which the enrichment guide says is updated monthly, and it returns profile data only, not emails or phone numbers.</p><p><strong>Why it matters:</strong> Teams get current LinkedIn profile data for personalization at four times the token cost of the stored database, and because the data is pulled live from LinkedIn through a third party, buyers should ask how that sourcing sits with LinkedIn's user agreement.</p><p>Impact: Medium. Verification: Verified. Type: Integration / interoperability.</p><p>Evidence: <a href="https://snov.io/release-notes">Vendor documentation</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/snov-io">GTM Tech Index change log</a>. Free to reuse with a link back. <a href="https://gtmtechindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>HeyReach released workspace blacklists that hold up to 1,000 people and 1,000 companies, with CSV import and additions through the API and…</title>
      <link>https://gtmtechindex.com/changelog/heyreach</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6aaf42546b90df6660784c08</guid>
      <pubDate>Wed, 16 Sep 2026 12:00:00 GMT</pubDate>
      <category>Safety / governance</category>
      <category>LinkedIn &amp; Social Selling</category>
      <category>Sales Engagement &amp; Outreach</category>
      <category>Data &amp; Enrichment</category>
      <description><![CDATA[<p>HeyReach released workspace blacklists that hold up to 1,000 people and 1,000 companies, with CSV import and additions through the API and MCP of up to 100 entries per request. New campaigns turn on both exclusion checks by default, and an excluded lead never enters the sequence.</p><p><strong>Why it matters:</strong> A reusable suppression list is basic outreach hygiene that LinkedIn tools have been slow to offer. Note the limits: lists belong to one workspace, are capped at 1,000, and a user can switch the exclusions off for a campaign.</p><p>Impact: Medium. Verification: Verified. Type: Safety / governance.</p><p>Evidence: <a href="https://www.heyreach.io/blog/blacklist-is-live">Vendor announcement</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/heyreach">GTM Tech Index change log</a>. Free to reuse with a link back. <a href="https://gtmtechindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>HeyReach introduced AI voice notes, which generate personalized audio messages from text using cloned or featured voices.</title>
      <link>https://gtmtechindex.com/changelog/heyreach</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6a9c2d876b0fb727220c5f3b</guid>
      <pubDate>Wed, 02 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>LinkedIn &amp; Social Selling</category>
      <category>Sales Engagement &amp; Outreach</category>
      <category>Data &amp; Enrichment</category>
      <description><![CDATA[<p>HeyReach introduced AI voice notes, which generate personalized audio messages from text using cloned or featured voices. A new Voice note action step in campaigns supports both static recordings and dynamic audio that pulls in personalization variables such as name and company.</p><p><strong>Why it matters:</strong> This is synthetic voice at campaign volume on a platform where a voice note reads as a personal gesture, so the disclosure question arrives with the feature rather than after it. Nothing in the announcement addresses whether the recipient is told the voice is generated, and buyers in two party consent states and under EU AI Act Article 50 should establish that before switching it on.</p><p>Impact: High. Verification: Verified. Type: Product / capability.</p><p>Evidence: <a href="https://www.heyreach.io/blog/voice-notes-are-live">Vendor announcement</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/heyreach">GTM Tech Index change log</a>. Free to reuse with a link back. <a href="https://gtmtechindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Reply.io moved its AI SDR API surface into public beta, taking 39 endpoints from documented to callable.</title>
      <link>https://gtmtechindex.com/changelog/reply-io</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6a8c47c32449972a39fd8663</guid>
      <pubDate>Tue, 11 Aug 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Sales Engagement &amp; Outreach</category>
      <category>AI SDR &amp; Outbound Agents</category>
      <category>Data &amp; Enrichment</category>
      <category>LinkedIn &amp; Social Selling</category>
      <description><![CDATA[<p>Reply.io moved its AI SDR API surface into public beta, taking 39 endpoints from documented to callable. The set covers the full AI SDR sequence lifecycle including autopilot enable, disable and force start, pending approvals with bulk send, Live Data searches, sequence preview and personalization, offer generation, the Strategist and Inbox AI drafts. Documentation was restructured into API Reference, MCP, Skills and CLI sections alongside a new command line client at v0.3.0.</p><p><strong>Why it matters:</strong> Sales operations and developer teams can now drive Reply's AI SDR from their own systems rather than the dashboard, which matters most to agencies running many client workspaces and to teams embedding outbound inside an agent stack. Approval mode and pending approvals are exposed as API objects, so the human in the loop step is scriptable and can also be scripted away.</p><p>Impact: High. Verification: Partially Verified. Type: Product / capability.</p><p>Evidence: <a href="https://community.reply.io/c/announcements">Vendor documentation</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/reply-io">GTM Tech Index change log</a>. Free to reuse with a link back. <a href="https://gtmtechindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Meet Drake introduced native CRM and Messenger capabilities to its LinkedIn automation platform.</title>
      <link>https://gtmtechindex.com/changelog/meet-drake</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6a8c47c32449972a39fd8662</guid>
      <pubDate>Tue, 11 Aug 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>LinkedIn &amp; Social Selling</category>
      <category>Sales Engagement &amp; Outreach</category>
      <description><![CDATA[<p>Meet Drake introduced native CRM and Messenger capabilities to its LinkedIn automation platform. The CRM allows users to filter contacts, update records and perform bulk actions, while the Messenger centralizes LinkedIn conversations, enabling users to manage InMails and apply message templates.</p><p><strong>Why it matters:</strong> Consolidating LinkedIn messaging and contact management into a single interface reduces the switching between the automation tool and LinkedIn itself. It also moves more of the conversation record off the platform and into the vendor, which is worth checking against the vendor's stated position on platform terms.</p><p>Impact: Medium. Verification: Verified. Type: Product / capability.</p><p>Evidence: <a href="https://intercom.help/meet-drake/en/articles/16181189-meet-drake-crm-feature">Vendor documentation</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/meet-drake">GTM Tech Index change log</a>. Free to reuse with a link back. <a href="https://gtmtechindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
  </channel>
</rss>
