Make’s October 2024 release delivered TikTok Audience management, Runway AI video generation, 23 newly verified apps, expanded BambooHR and Pipedrive modules, and a new scenario editor toolbar — giving automation builders more native integrations and smarter workflow tools without custom API workarounds.

Every month the Make community publishes a detailed changelog. October 2024 stands out as one of the most feature-packed releases of the year. From first-party TikTok audience targeting to AI-generated video and a redesigned toolbar inside the scenario editor, there is a lot to unpack.

If you’re deciding whether Make fits your stack better than Zapier, this release reinforces why Make’s integration pace matters. And if you’re still learning what the platform’s core building blocks do, the plain-English guide to Make scenarios is a good starting point before diving into new modules.

For teams already building, the additions in this release reduce the need for “Make an API Call” workarounds — the catch-all module builders use when a native connector doesn’t exist yet. The automations that used to require a developer keep getting easier.

Here’s everything that landed in October 2024, organized by category.

October 2024 Make Release: Quick Reference Table

1. TikTok Audiences — First-Party Audience Management Without Leaving Make

The TikTok Audiences integration brings first-party audience management directly into your Make scenarios. Before this, keeping TikTok Custom Audiences in sync with CRM data required manual exports or third-party tools sitting outside your automation stack.

What you can build now:

• Automatic daily sync of high-LTV customers from your CRM into TikTok Custom Audiences
• Churned-user exclusion lists that update on a schedule without manual intervention
• Reporting pulls from “Potential Audience Insights” piped into a Google Sheet dashboard

For agencies running multi-channel campaigns, this eliminates a manual sync step that previously fell through the cracks between platforms. The integration connects directly to Make’s TikTok Audiences connector.

2. Runway AI Video — Text-to-Video and Image-to-Video Automation

Runway’s Make integration opens a direct pipeline between your existing content assets and AI-generated video output. The integration covers text-to-video and image-to-video generation, meaning product images already living in Airtable or Shopify can become video ad creatives without a designer touching them.

Practical workflow:

• Pull product shots from Shopify → send to Runway → export MP4 to Google Drive
• Trigger auto-captioning on completed videos before pushing to social scheduling tools
• Auto-resize output for different social formats using downstream modules

This pairs well with the Leonardo.AI module expansion (see item 5) for teams that want both static and motion creative assets generated inside the same scenario. If you want to see how AI modules fit into real production builds, the case study on automating processes with no native module shows the same pattern applied to a different use case.

3. Anthropic Claude — “Make an API Call” Module Added

Anthropic Claude already had a presence in Make’s app library, but October 2024 added the generic “Make an API Call” module to that connector. This matters because it unlocks any Claude endpoint — including beta and preview APIs — without waiting for Make to ship a dedicated module for each one.

Why this is a bigger deal than it sounds: The existing Claude modules cover common actions like message completion. The API Call module lets builders route to specific model versions, pass custom system prompts, and use parameters that dedicated modules don’t expose. Builders who want stronger safety guardrails or specific Claude model versions now have that flexibility natively inside Make.

If you’re comparing how Claude fits into Make-based builds versus other AI tools, the Make Skills vs. ChatGPT comparison covers this distinction in depth.

4. BambooHR — Four New HR Analytics Triggers and Actions

BambooHR’s October expansion added four new triggers and actions focused on HR analytics. The standout is Watch Updated Employees, which fires a scenario any time an employee record changes — eliminating the need to poll BambooHR on a timer and then filter for changes manually.

Use cases this unlocks:

• Trigger offboarding sequences the moment a termination date is added to a record
• Push headcount changes to a live dashboard in real time
• Alert managers when direct report data changes without building a polling loop

HR teams that have started building their own automations with Make and AI will find these triggers reduce the complexity of keeping BambooHR data in sync with other tools in the stack.

5. Leonardo.AI — Generate Motion (Video) Plus Reporting

Leonardo.AI’s October additions include the Generate Motion (Video) endpoint and new reporting modules. The motion generation module takes a static image and animates it — useful for social content pipelines where a single product image needs to produce both still and animated variants.

The reporting endpoints let builders pull generation history and usage data into dashboards without leaving Make, which is useful for agencies tracking credit consumption across client accounts.

6. Pipedrive CRM — 13 New Field, Filter, and Summary Modules

Pipedrive’s October expansion is the largest single-app module addition in this release. The 13 new modules cover custom deal field manipulation, advanced filtering, and summary reporting — functions that previously required builders to use the generic “Make an API Call” workaround.

What previously required a workaround, now native:

• Read and write specific custom deal fields without parsing raw API responses
• Filter deals by multiple criteria inside a module instead of using router branches
• Pull summary stats for reporting without a custom HTTP module pointed at the Pipedrive API

For sales ops teams with complex Pipedrive configurations, this reduces scenario complexity significantly. Fewer workaround modules means fewer points of failure — a principle that applies to every automation decision worth making.

7. Greip — Fraud Prevention Scoring Inside Checkout Workflows

Greip reached verified status in October 2024, bringing fraud prevention scoring directly into Make automation workflows. The integration lets builders drop a fraud score check into any checkout or lead capture scenario — flagging suspicious transactions before they complete rather than catching them in post-purchase review.

Basic pattern: Webhook receives order data → Greip module scores the transaction → router branch sends high-risk orders to a manual review queue and clears low-risk orders to fulfillment. No custom HTTP modules, no API key management outside of Make’s connection vault.

8. TimelineAI for WhatsApp — Multi-Number Messaging at Scale

TimelineAI’s verification gives Make builders a native way to run WhatsApp messaging across multiple phone numbers from a single scenario. This is the architecture that multi-location businesses and agencies need — one scenario, multiple sender identities, without routing logic built on top of workarounds.

Combined with WAMM App (see item 9), October 2024 brought two WhatsApp-native tools into Make’s verified library in the same release cycle.

9. WAMM App — Visual Campaign Scheduler for WhatsApp

WAMM App’s verified status adds a visual campaign scheduling layer for WhatsApp broadcasts. Where TimelineAI handles message delivery at scale, WAMM App handles the scheduling and campaign management layer — defining when messages go, to which segments, and on what cadence.

The two tools work at different layers of the same workflow: WAMM manages campaign logic, TimelineAI handles multi-number delivery execution.

10. Valuecase — Auto-Create Sales Rooms from CRM Triggers

Valuecase provides collaborative sales rooms — digital workspaces shared between a sales rep and a prospect. The Make integration automates the creation step: when a Pipedrive deal moves to the Proposal stage, a scenario creates the Valuecase workspace automatically, populates it with relevant deal data, and notifies the rep.

This eliminates a manual step that sales teams typically do inconsistently — some reps create the room, some skip it, and the process never fully standardizes. Automation removes the inconsistency entirely.

11. Tinify — On-the-Fly Image Compression for eCommerce

Tinify’s verification adds image compression directly into Make scenarios. For eCommerce operations, this means product images uploaded to a CMS or DAM can be automatically compressed before publishing — reducing page load times without a separate optimization step in the workflow.

Standard pattern: New image added to Shopify or a shared Drive folder → Tinify module compresses → compressed version replaces original or routes to a separate optimized folder. No manual export-compress-reimport cycle.

12. MindStudio — Orchestrate AI Workers from Make Scenarios

MindStudio reached verified status in October, giving builders a native connector to its AI “worker” platform. MindStudio lets non-developers build AI agents that perform specific tasks — think document classification, data extraction, or content generation with custom instructions.

The Make integration lets those workers become steps inside a larger automation scenario. A MindStudio worker handles the AI reasoning; Make handles the orchestration, routing, and downstream actions. This is the architecture that automation-first thinking points toward: AI handles judgment calls, automation handles everything else.

13. Enrich CRM and Foxentry — Contact Enrichment and Validation

Two contact data tools reached verified status in October: Enrich CRM and Foxentry. Both address the same problem from different angles — incoming leads and contacts often arrive with incomplete or incorrect data, and fixing that manually is slow and inconsistent.

Enrich CRM appends missing firmographic and contact data to existing records. Foxentry validates contact fields (addresses, phone numbers, emails) at the point of entry. Used together in a lead intake scenario, they clean and enrich a contact record before it ever reaches a sales rep.

For teams dealing with the downstream consequences of bad CRM data — the kind that causes the payroll errors described in the $103K labor recovery case study — upstream validation like this is the right place to intervene.

14. MightyChat and PingBell — KPI Alerts and Gamification in Slack or Teams

MightyChat and PingBell both reached verified status in October, targeting the same workflow: surfacing real-time KPI data inside communication tools like Slack or Microsoft Teams.

PingBell fires conversion alerts — a deal closes, a form submits, a threshold is crossed — and pushes a notification to the team channel. MightyChat adds a gamification layer, turning those alerts into leaderboard updates and challenge tracking. The Make integration means these notifications trigger from scenario logic, not from manual announcements.

15. Scenario Editor Toolbar — Platform-Level UX Update

Beyond the new apps and modules, October 2024 included a redesigned toolbar inside the Make scenario editor. The update reorganizes navigation controls to reduce the number of clicks needed to access common actions during scenario building.

Platform-level UX changes like this tend to compound over time — builders who spend hours per week inside the editor accumulate the time savings across every session. For teams running the kind of high-volume scenario work described in the proposal generation case study, editor efficiency matters more than it might appear.

What These Updates Mean for Your Automation Stack

The October 2024 release continues a pattern: Make’s app library is expanding fastest in the areas where builders have historically had to use generic HTTP modules or third-party middleware to fill gaps. Each verified app and new module set removes a layer of custom logic from scenarios that previously required it.

For teams evaluating whether to build on Make versus alternatives, releases like this one are part of the argument. The Make vs. N8N comparison covers the structural differences, and the Make FAQ for Zapier users addresses the most common transition questions.

If you’re running an audit of your current automation stack to identify where native connectors could replace workarounds, the OpsMap™ audit process gives you a structured way to find those gaps before building.

Additional Reading

• Make vs Zapier: A Straight Pricing and Feature Breakdown for 2026
• What Is a Make Scenario? The Plain-English Guide for Zapier Users
• 10 Automations That Are Finally Easy to Build With Make + AI — No Developer Needed
• How a Non-Technical HR Team Started Building Their Own Automations With Make + AI
• How We Used Make and Claude to Automate a Process That Had No Native Module
• 7 Questions to Ask Before You Automate Anything (The OpsMap Checklist)
• What Is Automation-First? Why You Should Automate Before You Add AI
• How One Ops Team Recovered $103K in Annual Labor Hours With Make Automation
• Make vs N8N: When Self-Hosting Stops Being Worth It
• Make.com FAQ: Everything Zapier Users Ask Before Switching
• How to Run an OpsMap Audit Before Automating Anything
• How Nick Cut 6 Manual Handoffs From Proposal Generation With One Make Workflow
• Make Skills vs. ChatGPT for Building Automation: An Honest Comparison
• 5 Automation Tasks AI Handles Well — and 5 It Still Gets Wrong
• How We Rebuilt a Client’s Zapier Stack in Make and Cut Their Automation Bill by 60%