<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>GTM Tech Index: Data &amp; Enrichment changes</title>
    <link>https://gtmtechindex.com/categories/data-and-enrichment</link>
    <atom:link href="https://gtmtechindex.com/feeds/data-and-enrichment.xml" rel="self" type="application/rss+xml" />
    <description>Material product changes at Data &amp; Enrichment 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: Data &amp; Enrichment changes</title>
      <link>https://gtmtechindex.com/categories/data-and-enrichment</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>Saleslumen published version 0.3.0 of its n8n verified community node (@saleslumen/n8n-nodes-saleslumen) on 24 Sep 2026, with 0.3.1 the…</title>
      <link>https://gtmtechindex.com/changelog/saleslumen</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6ab94d1abae534b71b03efa9</guid>
      <pubDate>Thu, 24 Sep 2026 12:00:00 GMT</pubDate>
      <category>Integration / interoperability</category>
      <category>Sales Engagement &amp; Outreach</category>
      <category>CRM &amp; Systems of Record</category>
      <category>Data &amp; Enrichment</category>
      <description><![CDATA[<p>Saleslumen published version 0.3.0 of its n8n verified community node (@saleslumen/n8n-nodes-saleslumen) on 24 Sep 2026, with 0.3.1 the same day. Compared with 0.2.0, the node adds campaign lifecycle commands (activate, pause, resume, archive, complete, delete), sender account and variable settings, and per campaign sending fields including daily delivery limit, daily new recipient limit, bounce auto pause threshold and an unsubscribe policy option, plus workflow publish, activate, deactivate, resume and cancel execution operations. It also adds OAuth2 access token and namespace authentication alongside the organization API key.</p><p><strong>Why it matters:</strong> Teams running outbound from n8n can now run full campaign and workflow lifecycles, including sending limits and unsubscribe headers, without calling the REST API directly. The node's unsubscribe policy field defaults to None, so compliance settings must be set explicitly in each automation.</p><p>Impact: Medium. Verification: Partially Verified. Type: Integration / interoperability.</p><p>Evidence: <a href="https://registry.npmjs.org/@saleslumen/n8n-nodes-saleslumen">Vendor documentation</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/saleslumen">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>Lusha moved Data Waterfall, which falls through to enabled third party providers when Lusha's own data has no email or phone match, from…</title>
      <link>https://gtmtechindex.com/changelog/lusha</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6ab94d1abae534b71b03efa5</guid>
      <pubDate>Wed, 23 Sep 2026 12:00:00 GMT</pubDate>
      <category>Pricing / packaging</category>
      <category>Data &amp; Enrichment</category>
      <category>Sales Engagement &amp; Outreach</category>
      <category>Conversation Intelligence</category>
      <description><![CDATA[<p>Lusha moved Data Waterfall, which falls through to enabled third party providers when Lusha's own data has no email or phone match, from Pro plans and above to every paid plan. The change is packaging only: there is no API change and admins still turn it on per account under Account Settings, Waterfall.</p><p><strong>Why it matters:</strong> Lower tier paid customers can now reach third party provider data for hard to match contacts without upgrading to Pro, which changes the plan math and means more records may come from sources other than Lusha's own database.</p><p>Impact: Medium. Verification: Verified. Type: Pricing / packaging.</p><p>Evidence: <a href="https://docs.lusha.com/changelog">Vendor documentation</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/lusha">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>Common Room added Natural Language Filtering, a public beta that turns a plain English description such as &quot;CEOs who have visited the…</title>
      <link>https://gtmtechindex.com/changelog/common-room</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6ab94d1abae534b71b03efa2</guid>
      <pubDate>Wed, 23 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Intent &amp; Signals</category>
      <category>Data &amp; Enrichment</category>
      <category>AI SDR &amp; Outbound Agents</category>
      <description><![CDATA[<p>Common Room added Natural Language Filtering, a public beta that turns a plain English description such as "CEOs who have visited the pricing page" into standard filter chips on Contacts, Organizations, Activity, Segments, score criteria and workflow triggers. Results always follow the visible chips, and any part of a request it cannot translate is skipped and listed in an explanation panel. It is included in all plans at no extra cost and is not yet available in Prospector.</p><p><strong>Why it matters:</strong> Reps can build target lists and score or workflow criteria without waiting on RevOps, while every AI generated condition stays visible and removable, which matters because saved score and workflow criteria run automatically.</p><p>Impact: Medium. Verification: Partially Verified. Type: Product / capability.</p><p>Evidence: <a href="https://www.commonroom.io/docs/get-started/core-concepts/natural-language-filtering/">Vendor documentation</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/common-room">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>Surfe added a Gong Engage connector that sends contacts from LinkedIn profile views, contact lists, recommendation cards and search…</title>
      <link>https://gtmtechindex.com/changelog/surfe</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6ab94d1abae534b71b03ef9f</guid>
      <pubDate>Tue, 22 Sep 2026 12:00:00 GMT</pubDate>
      <category>Integration / interoperability</category>
      <category>Data &amp; Enrichment</category>
      <category>Intent &amp; Signals</category>
      <description><![CDATA[<p>Surfe added a Gong Engage connector that sends contacts from LinkedIn profile views, contact lists, recommendation cards and search results into existing Gong Engage flows, with a choice of flow and starting step. Surfe syncs the contact to the CRM first, checks whether the contact is already in a flow, and shows flow status (for example Step 3 of 7, Bounced, Opted Out) on contact cards. It is available on the Pro plan and above, is connected once per workspace by a Gong Technical Admin, and replaces rather than sits alongside Salesloft, Outreach or Lemlist, since only one outreach tool can be active.</p><p><strong>Why it matters:</strong> Gong Engage users can now pair Surfe prospecting and enrichment with their sequencer without switching tools, which removes a reason to also buy Outreach or Salesloft seats. Buyers should note the one outreach tool limit and that flows cannot be created, edited or exited from Surfe.</p><p>Impact: Medium. Verification: Partially Verified. Type: Integration / interoperability.</p><p>Evidence: <a href="https://support.surfe.com/hc/en-gb/articles/39151763588242-How-can-I-connect-Gong-Engage-with-Surfe">Vendor documentation</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/surfe">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>Instantly released an AI Voice Agent in its September 22 Instantly Agents release that engages prospects by voice using ElevenLabs audio…</title>
      <link>https://gtmtechindex.com/changelog/instantly</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6ab94d1abae534b71b03ef9c</guid>
      <pubDate>Tue, 22 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Sales Engagement &amp; Outreach</category>
      <category>Data &amp; Enrichment</category>
      <category>AI SDR &amp; Outbound Agents</category>
      <description><![CDATA[<p>Instantly released an AI Voice Agent in its September 22 Instantly Agents release that engages prospects by voice using ElevenLabs audio models. The changelog says it can call new inbound leads within seconds, qualify prospects and capture a preferred demo time; the help center adds that it runs either as a phone agent on a workspace number for inbound or outbound calls or as an embeddable website voice widget.</p><p><strong>Why it matters:</strong> This takes an email first outreach platform into AI placed phone calls, so buyers who turn on outbound calling bring calling consent rules such as the TCPA into scope for their Instantly use.</p><p>Impact: High. Verification: Verified. Type: Product / capability.</p><p>Evidence: <a href="https://feedback.instantly.ai/changelog/the-new-instantly-agents-are-here">Vendor announcement</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/instantly">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>Autobound launched a rebuilt Reddit Signals feed that extracts B2B events from 550+ vetted business subreddits into 15 typed subtypes…</title>
      <link>https://gtmtechindex.com/changelog/autobound</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6ab94d1abae534b71b03ef99</guid>
      <pubDate>Tue, 22 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Intent &amp; Signals</category>
      <category>Sales Engagement &amp; Outreach</category>
      <category>Data &amp; Enrichment</category>
      <description><![CDATA[<p>Autobound launched a rebuilt Reddit Signals feed that extracts B2B events from 550+ vetted business subreddits into 15 typed subtypes, such as pricingChange, serviceOutage, layoffs and buyingIntent, each with verbatim quotes, a link to the source thread and a company domain from its resolver. A first pass model gates threads, a stronger model extracts the signal and an automated reviewer rechecks risky records, and every event carries an evidence stage (speculative, rumored, reported, confirmed). The feed ships weekly through the Signal API and the MCP server.</p><p><strong>Why it matters:</strong> Buyers can filter community sourced signals by evidence strength, and Autobound states it does not resolve Reddit usernames to real identities. The post claims roughly 150,000 signals a month, while the API changelog states about 13,000 to 21,667 a month through the API, so confirm volume before buying.</p><p>Impact: Medium. Verification: Verified. Type: Product / capability.</p><p>Evidence: <a href="https://www.autobound.ai/blog/reddit-signals-launch">Vendor announcement</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/autobound">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>PeopleLinx released a revenue orchestration solution for commercial real estate brokers, REITs and acquisition teams.</title>
      <link>https://gtmtechindex.com/changelog/peoplelinx</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6ab94dd5c700f29c9782cb2f</guid>
      <pubDate>Mon, 21 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Sales Engagement &amp; Outreach</category>
      <category>Data &amp; Enrichment</category>
      <category>Dialers &amp; Voice</category>
      <description><![CDATA[<p>PeopleLinx released a revenue orchestration solution for commercial real estate brokers, REITs and acquisition teams. It identifies target properties from set criteria (asset class, geography, property profile), separates owners from tenants and operators, finds the decision makers behind property LLCs, runs personalized email and video outreach, and qualifies and routes responses to the assigned broker.</p><p><strong>Why it matters:</strong> Extends PeopleLinx into a new vertical with property and ownership research that general contact databases lack, so CRE and REIT buyers can judge it against CRE specific data tools rather than generic sequencers. It is sold as a managed program, so buyers should confirm which steps run in software and which are done by PeopleLinx staff.</p><p>Impact: Medium. Verification: Verified. Type: Product / capability.</p><p>Evidence: <a href="https://peoplelinx.com/blog/industry-first-cre-origination-solution">Vendor announcement</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/peoplelinx">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>Leadsforge added local business search to its Public API under /maps-discovery, exposing Google Maps business search by location, radius…</title>
      <link>https://gtmtechindex.com/changelog/leadsforge</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6ab94d1abae534b71b03ef93</guid>
      <pubDate>Mon, 21 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Data &amp; Enrichment</category>
      <category>Intent &amp; Signals</category>
      <description><![CDATA[<p>Leadsforge added local business search to its Public API under /maps-discovery, exposing Google Maps business search by location, radius and category, owner enrichment for discovered companies, a category list endpoint, async job status and results, and completion webhooks. Before this, Maps discovery was only available inside the Leadsforge app; the endpoints (including POST /maps-discovery/search and POST /maps-discovery/enrich-owners) are live in the published API spec.</p><p><strong>Why it matters:</strong> Teams and partners selling to local and SMB businesses can now run discovery and owner enrichment from their own tools or workflows without the Leadsforge UI. The source of these records is Google Maps results, which buyers should factor into data provenance and platform terms review.</p><p>Impact: Medium. Verification: Verified. Type: Product / capability.</p><p>Evidence: <a href="https://roadmap.salesforge.ai/en/changelogs/weekly-release-update-sep-week-3-3">Vendor documentation</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/leadsforge">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>Apollo.io: Apollo added structured error_details to selected REST and MCP errors, with stable codes and recovery guidance covering search validation…</title>
      <link>https://gtmtechindex.com/changelog/apollo-io</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6aaf42546b90df6660784bff</guid>
      <pubDate>Fri, 18 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Data &amp; Enrichment</category>
      <category>Sales Engagement &amp; Outreach</category>
      <category>Dialers &amp; Voice</category>
      <description><![CDATA[<p>Apollo added structured error_details to selected REST and MCP errors, with stable codes and recovery guidance covering search validation and enrichment failures. Organization Enrichment requests with a missing or unreadable identifier now return HTTP 422 where they used to return 200 with an empty organization. The legacy top level fields on migrated errors will be removed on 16 February 2027.</p><p><strong>Why it matters:</strong> The 200 that becomes a 422 is the line to read. Any workflow that treated an empty enrichment as a quiet success will now see a failure, which is the honest answer and also a breaking one. The February 2027 removal date gives integration owners five months to update their error handling.</p><p>Impact: High. Verification: Verified. Type: Product / capability.</p><p>Evidence: <a href="https://docs.apollo.io/changelog/api-errors-now-include-structured-details">Vendor documentation</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/apollo-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>Cognism announced that its ISO 27001 and ISO 27701 certifications are now issued by British Assessment Bureau, a certification body…</title>
      <link>https://gtmtechindex.com/changelog/cognism</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6aaf42546b90df6660784c05</guid>
      <pubDate>Wed, 16 Sep 2026 12:00:00 GMT</pubDate>
      <category>Security / compliance</category>
      <category>Data &amp; Enrichment</category>
      <category>Intent &amp; Signals</category>
      <description><![CDATA[<p>Cognism announced that its ISO 27001 and ISO 27701 certifications are now issued by British Assessment Bureau, a certification body accredited by UKAS. The notice identifies certificate 273578, issued 28 August 2026 and expiring 1 September 2028. The standards themselves are unchanged.</p><p><strong>Why it matters:</strong> Who issued a certificate matters as much as the certificate. Security reviewers who check accreditation can now trace Cognism's to UKAS, and should ask for the current certificates during due diligence.</p><p>Impact: Medium. Verification: Verified. Type: Security / compliance.</p><p>Evidence: <a href="https://www.cognism.com/newsroom/ukas-accredited-iso-27001-and-27701-certification">Vendor announcement</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/cognism">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>Clay made its Plugin available to all customers, bundling its CLI and API for coding agents such as Claude Code and Codex.</title>
      <link>https://gtmtechindex.com/changelog/clay</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6aaf42546b90df6660784c03</guid>
      <pubDate>Tue, 15 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Data &amp; Enrichment</category>
      <category>AI SDR &amp; Outbound Agents</category>
      <description><![CDATA[<p>Clay made its Plugin available to all customers, bundling its CLI and API for coding agents such as Claude Code and Codex. General availability adds programmatic control of Audiences, campaign creation and analytics in Sequencer, and table queries, on top of the enrichment and workflow functions from the beta. A day later Clay opened the Plugin and its other newer products to customers on legacy Starter, Explorer and Pro plans until 31 December 2026.</p><p><strong>Why it matters:</strong> This turns Clay from a tool an operator clicks through into infrastructure a team can build on. Write access from a coding agent is the part to govern: decide which agents may create campaigns before one does. Legacy customers get a free look with a hard end, so budget for the plan change before building on it.</p><p>Impact: High. Verification: Verified. Type: Product / capability.</p><p>Evidence: <a href="https://www.clay.com/blog/build-custom-gtm-tooling-on-clay">Vendor announcement</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/clay">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>Reevo updated its macOS desktop app with local meeting transcription in more than 90 languages and Ask Reevo chat before, during and after…</title>
      <link>https://gtmtechindex.com/changelog/reevo</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6aaf42546b90df6660784c13</guid>
      <pubDate>Mon, 14 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>CRM &amp; Systems of Record</category>
      <category>Sales Engagement &amp; Outreach</category>
      <category>Data &amp; Enrichment</category>
      <category>Conversation Intelligence</category>
      <description><![CDATA[<p>Reevo updated its macOS desktop app with local meeting transcription in more than 90 languages and Ask Reevo chat before, during and after meetings. The release also adds meeting start detection, menu bar controls and a floating widget. Reevo's documentation says supported languages can vary by workspace.</p><p><strong>Why it matters:</strong> Local transcription across that many languages is the draw for multilingual sales teams. Confirm the languages you need are enabled for your workspace before relying on it.</p><p>Impact: Medium. Verification: Partially Verified. Type: Product / capability.</p><p>Evidence: <a href="https://reevo.ai/release-notes">Vendor documentation</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/reevo">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>Lusha API release 2.14.0 adds column catalogs for contact and company tables and endpoints that add up to 10 columns per call.</title>
      <link>https://gtmtechindex.com/changelog/lusha</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6aaf42546b90df6660784c0b</guid>
      <pubDate>Thu, 10 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Data &amp; Enrichment</category>
      <category>Sales Engagement &amp; Outreach</category>
      <category>Conversation Intelligence</category>
      <description><![CDATA[<p>Lusha API release 2.14.0 adds column catalogs for contact and company tables and endpoints that add up to 10 columns per call. Adding a column starts asynchronous enrichment across every row, with each result reported separately, and the operations currently consume no credits. Release 2.15.0 followed on 17 September, adding Instagram, YouTube and TikTok URLs to company enrichment on all plans.</p><p><strong>Why it matters:</strong> Teams can now define and enrich a table from code, which removes the manual setup at the start of a data workflow. The no credit pricing on these calls is described as current, so it is worth confirming before building volume on it.</p><p>Impact: Medium. Verification: Verified. Type: Product / capability.</p><p>Evidence: <a href="https://docs.lusha.com/changelog#2140---2026-09-10---tables-column-catalog--add-columns">Vendor documentation</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/lusha">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>Autobound added a podcastAppearance signal subtype to its podcast intelligence pipeline.</title>
      <link>https://gtmtechindex.com/changelog/autobound</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6a9c2d876b0fb727220c5f39</guid>
      <pubDate>Tue, 01 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Intent &amp; Signals</category>
      <category>Sales Engagement &amp; Outreach</category>
      <category>Data &amp; Enrichment</category>
      <description><![CDATA[<p>Autobound added a podcastAppearance signal subtype to its podcast intelligence pipeline. The new subtype detects and structures the case where an executive appears as a guest on a B2B podcast, which the existing podcast contact and company signals did not separate out.</p><p><strong>Why it matters:</strong> Signal vendors mostly compete on breadth, so a new subtype at this granularity is a claim about precision instead. A guest appearance gives outreach something specific and recent to reference, which is the difference between a personalized opening line and one that only looks personalized.</p><p>Impact: Medium. Verification: Verified. Type: Product / capability.</p><p>Evidence: <a href="https://www.autobound.ai/blog/whats-new-signal-api-fall-2026">Vendor announcement</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/autobound">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>Autobound shipped an update to its Signal API, headlined by the rollout of podcast intelligence signals containing over 58,000 extracted…</title>
      <link>https://gtmtechindex.com/changelog/autobound</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6a92d4a34470e92a57253207</guid>
      <pubDate>Thu, 27 Aug 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Intent &amp; Signals</category>
      <category>Sales Engagement &amp; Outreach</category>
      <category>Data &amp; Enrichment</category>
      <description><![CDATA[<p>Autobound shipped an update to its Signal API, headlined by the rollout of podcast intelligence signals containing over 58,000 extracted B2B podcast events such as appearances, claims, and sponsorships. The release also rebuilt SEO traffic signals around AI search visibility, expanded subtype filtering to all entity enrichment endpoints, and upgraded the portal sandbox into a live browsing web research agent.</p><p><strong>Why it matters:</strong> Revenue leaders can leverage the newly added podcast and AI search visibility signals to trigger highly specific, contextual outreach that competitors cannot easily match. For GTM operations teams, the new subtype filtering on enrichment endpoints provides a direct cost saving mechanism by allowing them to retrieve and pay only for the exact signal categories they need.</p><p>Impact: High. Verification: Verified. Type: Product / capability.</p><p>Evidence: <a href="https://www.autobound.ai/blog/whats-new-signal-api-august-2026">Vendor announcement</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/autobound">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>Saleshandy introduced Prospect Enrollment, allowing users to throttle the number of prospects entering the first step of an outreach…</title>
      <link>https://gtmtechindex.com/changelog/saleshandy</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6a8c47c32449972a39fd866e</guid>
      <pubDate>Mon, 24 Aug 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Sales Engagement &amp; Outreach</category>
      <category>Data &amp; Enrichment</category>
      <description><![CDATA[<p>Saleshandy introduced Prospect Enrollment, allowing users to throttle the number of prospects entering the first step of an outreach sequence on a daily, weekly, or monthly basis. The update also includes a new CSV Enrichment feature for bulk data enrichment and opens API access to Outreach Starter plan users, supported by newly rebuilt API documentation.</p><p><strong>Why it matters:</strong> Pacing entry into a sequence is a direct deliverability control: it prevents the volume spikes that trigger filtering and it protects a warming domain from a large list import. Putting the cap at the sequence level rather than the mailbox level means the limit follows the campaign rather than the sender.</p><p>Impact: Medium. Verification: Partially Verified. Type: Product / capability.</p><p>Evidence: <a href="https://headwayapp.co/saleshandy-changelog">Vendor documentation</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/saleshandy">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>Lusha released API version 2.13.0, introducing a dedicated Conversations tag for conversational intelligence.</title>
      <link>https://gtmtechindex.com/changelog/lusha</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6a8c47c32449972a39fd866d</guid>
      <pubDate>Wed, 19 Aug 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Data &amp; Enrichment</category>
      <category>Sales Engagement &amp; Outreach</category>
      <category>Conversation Intelligence</category>
      <description><![CDATA[<p>Lusha released API version 2.13.0, introducing a dedicated Conversations tag for conversational intelligence. The update adds stricter validation, where a pageSize above 100 or an invalid date format now returns a 400 error, and it unifies the response for missing or still processing transcripts under a single 404.</p><p><strong>Why it matters:</strong> Teams integrating Lusha's conversational intelligence need to update pagination and error handling, since requests that previously succeeded will now fail validation. The unified 404 also removes the ability to distinguish a transcript that does not exist from one that is still processing, so retry logic has to assume both.</p><p>Impact: High. Verification: Partially Verified. Type: Product / capability.</p><p>Evidence: <a href="https://docs.lusha.com/changelog">Vendor documentation</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/lusha">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>Lusha released API version 2.12.0, adding a maxContactsPerCompany parameter to the Prospecting Contacts endpoint and a required…</title>
      <link>https://gtmtechindex.com/changelog/lusha</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6a8c47c32449972a39fd866b</guid>
      <pubDate>Tue, 18 Aug 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Data &amp; Enrichment</category>
      <category>Sales Engagement &amp; Outreach</category>
      <category>Conversation Intelligence</category>
      <description><![CDATA[<p>Lusha released API version 2.12.0, adding a maxContactsPerCompany parameter to the Prospecting Contacts endpoint and a required maxResultsPerSignal parameter to the Signals API. The Contact Lookalikes endpoint moved to a v3 path with fully replaced request and response schemas that are not backwards compatible.</p><p><strong>Why it matters:</strong> This is a breaking change. Any integration calling Contact Lookalikes has to be rewritten against the v3 schema, and calls to the Signals API now fail without the new required parameter. The per company cap is the useful addition, giving operations teams direct control over credit consumption during prospecting.</p><p>Impact: High. Verification: Partially Verified. Type: Product / capability.</p><p>Evidence: <a href="https://docs.lusha.com/changelog">Vendor documentation</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/lusha">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>Instantly introduced Company Sources in SuperSearch, allowing users to find contacts at named target companies.</title>
      <link>https://gtmtechindex.com/changelog/instantly</link>
      <guid isPermaLink="false">gtmtechindex.com:change:6a8c47c32449972a39fd8665</guid>
      <pubDate>Wed, 12 Aug 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Sales Engagement &amp; Outreach</category>
      <category>Data &amp; Enrichment</category>
      <category>AI SDR &amp; Outbound Agents</category>
      <description><![CDATA[<p>Instantly introduced Company Sources in SuperSearch, allowing users to find contacts at named target companies. Users can upload a CSV, use saved company lists or draw on live integrations to build contact lists from tech stack data, ecommerce stores or lookalike audiences.</p><p><strong>Why it matters:</strong> Teams can run account based prospecting inside Instantly rather than assembling lists in a separate enrichment tool first. The data behind the tech stack and lookalike sources is not described, so buyers with a provenance requirement will need to ask where those signals come from.</p><p>Impact: Medium. Verification: Partially Verified. Type: Product / capability.</p><p>Evidence: <a href="https://feedback.instantly.ai/changelog">Vendor documentation</a></p><p>Source: <a href="https://gtmtechindex.com/changelog/instantly">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>
  </channel>
</rss>
