Make.com’s December 2024 release cycle added Snapchat Campaign Management, Braze, expanded Google Ads and Workday modules, verified over 40 new integrations, launched ready-to-deploy automation templates, and shipped two platform-level improvements that change how teams handle failed executions and plan downgrades.

If you run automations on Make.com, December 2024 was a dense month. The platform expanded in four directions at once: new app integrations, new modules on existing apps, a wave of verified connectors, and infrastructure improvements that reduce friction in production workflows. What follows is a structured breakdown of every meaningful update — organized so you can quickly identify what applies to your stack.

If you’re newer to the platform and want the foundational context, the guide on what a Make scenario actually is is a good starting point. For a broader comparison of where Make sits relative to alternatives, see the Make vs. Zapier breakdown for 2026. And if you’re evaluating whether to build on Make yourself or bring in outside help, this DIY vs. partner guide covers the decision clearly.

What Landed in December 2024: A Quick Reference

New Apps: What Make Added to Its Integration Library

1. Snapchat Campaign Management

Make now connects directly to Snapchat’s advertising infrastructure. The Snapchat Campaign Management integration lets you create, update, and measure Snapchat ad campaigns from inside a Make scenario — no manual platform-switching required. For marketing teams running paid social across multiple channels, this means Snapchat data can finally live in the same automated pipeline as your other ad platforms.

Practical use: trigger scenario runs based on campaign performance thresholds, automatically update budgets when ROAS drops, or sync campaign data into a reporting sheet without touching the Snapchat dashboard.

2. Braze

Braze is a customer engagement platform built around real-time data and personalized messaging. The Make integration opens up orchestration of email journeys, push campaigns, and dynamic content flows — all driven by data that already exists in your other connected tools.

For teams that use Braze as their primary CRM communication layer, connecting it to Make removes the manual handoff between data events and campaign triggers. If you’re also dealing with HR or onboarding communication workflows, the onboarding automation case study with Sarah shows how similar trigger-based messaging cuts process time dramatically.

New Modules: Expanded Capability on Existing Apps

3. Google Ads Campaign Management — Search with Pagination

Make’s Google Ads module now supports search objects with pagination. This matters for accounts with large campaign libraries where a single API call previously truncated results. Paginated search means you can loop through every campaign, ad group, or keyword set — not just the first page returned.

4. Google Ads Campaign Management — Streaming Search

Streaming search is the more significant of the two Google Ads additions. Instead of waiting for a full dataset to return before processing, streaming lets Make begin acting on results as they arrive. For large-scale ad accounts running real-time optimization scenarios, this reduces latency and keeps scenario execution times tighter.

5. Workday Financial Management — Custom REST API Calls

Workday’s financial management module now accepts custom REST API calls. This is the flexibility unlock that many finance teams needed — rather than being limited to pre-built actions, you can now reach any endpoint Workday exposes, building precisely the data flows your finance stack requires.

6. Workday HCM — Custom REST API Calls

The same custom REST API capability applies to Workday HCM. HR teams managing headcount data, position management, or compensation workflows in Workday can now build Make scenarios that reach deeper into the HCM API without waiting for Make to add a specific pre-built module. If your HR team is building automations for the first time, this guide on non-technical HR teams using Make with AI is relevant context.

New Verified Apps: 40+ Integrations Certified in December

7. Aico — Financial Process Automation

Aico focuses on automating accounting and financial close processes. Verification on Make means the integration is tested, maintained, and officially supported. For finance teams already running Make scenarios, Aico can slot into invoice matching, reconciliation, and period-close workflows.

8. OpenPhone — VoIP, SMS, and Call Management

OpenPhone is a modern business phone system with strong team features. The verified Make integration enables automation around incoming calls, SMS triggers, and call disposition logging — useful for sales teams, support desks, and recruiting workflows where phone activity needs to flow into a CRM or tracking sheet automatically.

9. Taggun Receipt OCR

Taggun extracts structured data from receipts using OCR. Connected to Make, this means receipt images that arrive by email or upload can be automatically parsed, categorized, and pushed into expense systems — eliminating the manual data-entry step that costs operations teams hours every week. For more on the hidden cost of that kind of manual entry, see why manual data entry is a productivity killer.

10. Snappy — Personalized Gifting and Rewards

Snappy automates corporate gifting. With Make verification, you can trigger Snappy sends based on data events — a deal closing in your CRM, an employee hitting a milestone, a customer reaching a loyalty threshold — without any manual gift-ordering process.

Additional Verified Apps Worth Noting

Beyond the highlights above, December’s verification batch included Copy.ai, DeepAI, Curator, Dynosend, and over 35 other apps. The full list is available in Make’s official release notes. The practical takeaway: if you’ve been waiting on a connector to reach verified status before building production scenarios around it, December moved several candidates across that line.

New Automation Templates: What’s Ready to Deploy

11. Calendly Scheduling Link + Webhook Response

This template automatically generates a Calendly scheduling link and delivers it via webhook. The practical application: any form submission, CRM event, or inbound trigger can kick off a flow that sends a personalized booking link without a human step in between. Sales teams, recruiting teams, and client-onboarding workflows all benefit here.

12. HTML Email to Airtable Record

Incoming HTML emails get converted to plain text and logged as Airtable records. This is particularly useful for teams that receive structured data via email — order confirmations, intake forms, vendor notifications — and need that data in a database without manual copy-paste. For a look at how similar data-entry elimination plays out at scale, the David CRM data entry case study is directly relevant.

13. Google Sheets Rows to Xero Invoices

Filter rows in Google Sheets based on specific contact criteria and automatically generate corresponding Xero invoices. For service businesses or agencies billing clients on a schedule, this removes the manual invoice-creation step that typically happens at the end of every billing cycle.

Additional Templates in the December Drop

Make also released templates covering social media posting workflows, Slack-to-Google Drive file management, ClickUp task update automations, and ChatGPT-to-Slack notification pipelines. Each template is a deployable starting point — not a finished scenario, but a structural foundation you can adapt to your specific data and trigger conditions.

If you want to understand how to evaluate a Make scenario before putting it into production, this evaluation guide applies equally to templates and custom-built scenarios.

Platform Enhancements: Two Infrastructure Changes That Matter

14. Schedule Incomplete Executions in Bulk

Before this update, resolving halted scenario runs required addressing them individually. The December release adds the ability to reschedule multiple incomplete executions in a single API call. For teams running high-volume scenarios where transient errors — rate limits, temporary API downtime, network timeouts — create batches of stalled runs, this is a significant operational improvement. Instead of working through a queue one-by-one after an incident, you clear the backlog in one operation.

15. Improved Downgrade and Cancellation Flow

Make updated the plan downgrade and cancellation experience in two ways. First, when downgrading a multi-team account, you now choose which team to retain — previously an ambiguous process. Second, before confirming a downgrade, Make now displays a side-by-side comparison of your current plan features versus the new plan, so the impact is visible before you commit. This reduces the risk of accidentally losing automation capacity you depend on.

How to Use These Updates in Practice

The December 2024 release cycle follows a pattern worth recognizing: Make is simultaneously widening its integration surface (new apps, verified connectors) and deepening capability on existing integrations (Workday custom REST, Google Ads streaming). Both directions matter depending on where your automation gaps are.

If your gaps are in coverage — apps your stack uses that Make doesn’t yet connect to — the verified app expansion is the first place to check. If your gaps are in depth — scenarios that hit the limits of what pre-built modules can do — the custom REST API additions to Workday and the streaming search on Google Ads show the direction Make is moving.

For teams thinking about automation strategy more broadly, these seven questions to ask before automating anything remain the right starting framework regardless of which new Make features are available. New integrations expand what’s possible; they don’t determine what’s worth building first.

For teams considering migrating existing workflows from another platform, the Zapier-to-Make migration guide walks through the process without disrupting live automations. And for a broader view of how Make compares to alternatives in the current environment, the complete 2026 comparison guide covers the full landscape.

Frequently Asked Questions

Are the December 2024 Make updates still relevant in 2026?

Yes. The apps, modules, and verified integrations released in December 2024 are part of Make’s current production library. The Workday custom REST modules, Google Ads streaming search, and the bulk execution rescheduling feature are all active platform capabilities. Understanding when a feature landed helps you evaluate its maturity and stability.

What does it mean for a Make app to be “verified”?

A verified app on Make has passed compatibility testing and is actively maintained by Make or the integration partner. For production scenarios, verified status means the connector is less likely to break silently when the third-party API updates. Community apps are functional but carry more maintenance risk in long-running workflows.

Can I use Make templates as-is, or do they need customization?

Templates are starting points, not finished scenarios. They establish the structural logic — triggers, module sequence, data mapping patterns — but your specific field mappings, filters, and error handling need to be configured for your actual data. Treat a template as a 60-70% complete scenario that requires your team’s context to finish.

Who benefits most from the Workday custom REST API modules?

HR and finance teams running Workday as their system of record benefit directly. Custom REST API calls let you reach any Workday endpoint — not just the actions Make has pre-built. This matters when your workflow requires data or actions that fall outside the standard module library. The tradeoff is that building HTTP modules requires understanding the Workday API documentation.

How does the bulk execution rescheduling feature work?

It’s an API-level operation that allows you to reschedule multiple incomplete (halted) scenario executions in a single call rather than addressing each one individually. This is most useful after an incident — a rate limit burst, a downstream API outage, a temporary credential failure — that creates a queue of stalled runs you need to clear and reprocess.

Additional Reading

• What Is a Make Scenario? The Plain-English Guide for Zapier Users
• Make vs Zapier: A Straight Pricing and Feature Breakdown for 2026
• Make.com FAQ: Everything Zapier Users Ask Before Switching
• How to Switch From Zapier to Make Without Breaking Your Existing Workflows
• Make vs N8N: When Self-Hosting Stops Being Worth It
• Make vs Zapier vs N8N in the Age of AI: Complete 2026 Guide
• DIY Automation vs. Hiring a Make Partner in 2026
• 7 Questions to Ask Before You Automate Anything
• How to Evaluate a Make Scenario Built by AI Before It Goes to Production
• How David Eliminated 3 Hours of Daily CRM Entry With a Single Make Scenario
• How Sarah Compressed a 45-Minute Onboarding Process to Under 4 Minutes
• How a Non-Technical HR Team Started Building Their Own Automations With Make + AI
• Manual Data Entry: The Silent Killer of Business Productivity and Profit
• 10 Automations That Are Finally Easy to Build With Make + AI
• How We Rebuilt a Client’s Zapier Stack in Make and Cut Their Automation Bill by 60%